Hi Christoph,
Apologize for the delayed response, I'm on a holiday vacation. I will take
a look at your issues as soon as I can.
Shai
On Fri, Apr 11, 2014 at 12:02 PM, Christoph Kaser
wrote:
> Hello Shai and Mike,
>
> thank you for your answers!
>
> I created LUCENE-5597 for this feature. Unfo
On 16/04/14 10:42, Neil Bacon wrote:
Once this is sorted out I've got a modified AnalyzingInfixSuggester to
try that should handle a field with multiple values
(AnalyzingInfixSuggester only uses the first of multiple values).
correction: modification is to DocumentDictionary which I'm using
No, the index remains, you can reopen using OpenMode.Append (an enum
somewhere) if there is any exception like power loss you must delete the
lock file(which lock the index stream for other index process), i solved
some issues on performance using a multithread task since the IndexWriter
is thread
Hello Jose,
Thank you for your insight.
It sounds to me that, before method commit is called, then if there is any
error happened, example, power failure or human error, then the index will
be lost?
> (like at each X docs you commit the index and close it)
iwc.setMaxBufferedDocs(10);
the index
Hi,
Not sure if this is user error or a bug. AnalyzingInfixSuggester.build()
appears to be deleting the stored fields in my index.
Please see the attached unit test.
test1: creates an index
test2: debug logs stored fields, searches it
test3: does AnalyzingInfixSuggester.build() and looks up so
Given that he is already using Java, simply building a object-tree based
on the text file may be also possible. Although a 300MB file may turn
out to be fairly large in memory consumption (possibly caused by quite a
bit of object-overhead).
If that turns out to consume too much memory there ar
Hello,
I have followed instructions to build lucen 4.7.1 using maven build, in
order to get osgfied version of lucene, but I cannot use some bundles
like misc because of packages export conflicts
This is a quite similar issue to the one described here, this bug
https://issues.apache.org/jir
Hello!
To me, Lucene doesn't sound as good solution to this problem.
It seems to me that you need classic relational database. Storing tree
structure in relational DBs isn't simple thing but this presentation will
help you:
http://www.slideshare.net/billkarwin/sql-antipatterns-strike-back (slides
Hello,
We're using the Lucene 4.4 embedded in eXist-db (exist-db.org), and as the
subject indicates we want to ignore stop word gaps in queries - without the
user having to indicate where such gaps might occur at query time.
Since Lucene 4.4 the FilteringTokenFilter.setEnablePositionIncrements(
Thanks Doug
i have gone through SIREN DB Unfortunately i couldn't find enough examples
which i could match to my requirement could you point me to any examples
involving tree structure represented in text files
regards,
Girish Durgasi
--
View this message in context:
http://lucene.472066.
April 2014, Apache Lucene™ 4.7.2 available
The Lucene PMC is pleased to announce the release of Apache Lucene 4.7.2
Apache Lucene is a high-performance, full-featured text search engine
library written entirely in Java. It is a technology suitable for
nearly any application that requires full-tex
11 matches
Mail list logo