On Mon, Jan 27, 2014 at 3:48 AM, Andreas Brandl wrote:
> Is there some limitation on the length of fields? How do I get around this?
[cut]
> My overall goal is to index (arbitrary sized) text files and run a regular
> expression search using lucene's RegexpQuery. I suspect the
> KeywordAnalyzer to
Thanks. I wound up writing my own performance test tool, since, among other
things, I want to be sure that the index is big enough to not fit in memory
(either in a Lucene cache or the OS disk cache). I will take your
recommendation about nightly tests, though. It's hard to have too many unit
(Note: cross posted, please keep any replies to general@lucene)
Quick reminder that the CFP for ApacheCon (Denver) ends on Saturday...
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
Ladies and Gentlemen, start writing your proposals. The Call For Papers
for Apac
OpenGrok uses Lucene to index large source code repositories:
https://github.com/OpenGrok/OpenGrok
On Jan 27, 2014, at 9:59 AM, henrik sorensen
wrote:
> I have just started looking at Lucene but I wanted to ask if Lucene can be
> used to index large source code repository.
>
> Looking at the
I have just started looking at Lucene but I wanted to ask if Lucene can be
used to index large source code repository.
Looking at the documentation
http://lucene.apache.org/core/4_6_0/core/org/apache/lucene/analysis/package-summary.html#package_description
it seems like I can add specific languag
Thanks, I've put some time checks on the different parts of my search, it
seems like the directory opening part is taking most of the response time.
I'm using MMapDirectory, but it doesn't seem to speed up my directory
opening process.
I've split my indexes during creation into different folders, a
