codesearch

(Sorry, this is mildly off-topic.) Not sure if this fits your usecase, but you should check out codesearch if you haven't already: https://github.com/google/codesearch (Russ Cox's excellent writeup is here: https://swtch.com/~rsc/regexp/regexp4.html)

Unfortunately, this doesn't support regular expressions, which is a very useful feature for a code search engine. See https://github.com/google/codesearch for one implementation of this.

I have written about it all here (I maintain searchcode.com ) http://www.boyter.org/category/searchcode/ specifically http://www.boyter.org/2013/02/why-code-search-is-difficult/ is of note. If you want to see implementations I suggest looking at https://github.com/OpenGrok/OpenGrok https://github.com/ggreer/the_silver_searcher https://github.com/google/codesearch and my own https://github.com/boyter/searchcode-server

I've recently ran into debian code search again, https://codesearch.debian.net/. Built on top of Russ Cox's Code search (https://github.com/google/codesearch), and quite well documented. Can't say I've used it much, but it gives a few pointers into how you could build a better one yourself.

It's like codesearch [1]. [1] https://github.com/google/codesearch

Google code search used mmap and go back in the day: Regular Expression Matching with a Trigram Index or How Google Code Search Worked https://swtch.com/~rsc/regexp/regexp4.html https://github.com/google/codesearch/tree/master/index I used mmap in a go project that had large (GByte) hash tables. Sidesteps any GC pauses and makes for very fast file loading.

Yes, and they've open sourced part of that here (at least, I think it is related, and is also called "Code Search"): https://github.com/google/codesearch But, their public code search was not the same as the internal thing, as far as I know. The internal beast sounds kind of awesome. Here's his talk about it from a few years ago: https://www.youtube.com/watch?v=KTJs-0EInW8 I think the really useful thing (beyond a mere search engine that has indexed a lot of source code) is the comprehension of the "guzzintas" and "guzzouttas" of the code, more than merely a naive word search; i.e. knowing how pieces interact, so you can search for functions that work with a particular kind of object, for example, or objects that have the same properties, or code that interacts with the same API you're working with, whatever.

They open sourced a tool for code search: https://github.com/google/codesearch I don't know if it's the same, as I just heard of it from a YAPC talk a few days ago and haven't tried it, but it's called "Code Search" so it seems likely.

Part of the way down the post links to Russ Cox's excellent writeup of how Google used this general sort of technique (turn a regexp into a bunch of conditions involving three-symbol sequences, search an index for them, work from there) to do regexp searching scalably for Code Search: https://swtch.com/~rsc/regexp/regexp4.html You can peruse his open-source (re)implementation of the approach at https://github.com/google/codesearch .

If you're seeking to stay within the Atlassian ecosystem, the product that you're looking for is actually FishEye[0]. (Yes, yes, paying money, etc., but if you're a large organization, you're already used to buying stuff off the shelf to solve problems like this.) On the other hand, if you don't feel like drinking the Atlassian sugary beverage with an odd taste, there's LXR[1] (and LXRng[2]), OpenGrok[3] (remember OpenGrok?), and Etsy's Hound[4], not to mention Russ Cox's standalone Go implementation of Google's code search tool[5]. 0: https://www.atlassian.com/software/fisheye 1: http://lxr.sourceforge.net/ 2: Ironically enough, search Github. lxr.linux.no went down some time ago. 3: http://opengrok.github.io/OpenGrok/ 4: https://github.com/etsy/Hound 5: https://github.com/google/codesearch