Martin,
Note that the documents within each index segment (leaf context) are zero
indexed. Meaning that each segment in your index will contain a different
document with a segment-relative docId of 0.
When working inleaf context, you can calculate a document's absolute docId
with something like:
Dear all,
I'm experiencing troubles with SpanTermQuery.getSpans(AtomicReaderContext
context, Bits acceptDocs, Map termContexts) method in
version 4.6. I want to use it to retrieve payloads of matched spans.
First, I search the index with IndexSearcher.search(query, limit) and I get
TopDocs. In th
I've "remember now" name is /liblevenshtein works with Node.js if i am not
wrong.
"Lucene suggest" works on same algorithm. Which in practice is enough for
words with same "character sequence".
On Tue, Apr 1, 2014 at 1:30 PM, Jose Carlos Canova <
jose.carlos.can...@gmail.com> wrote:
> Hi,
>
>
Hi,
I haven't reach this point but it seems that Lucene has a "suggester"
project that works over "Lucene's Index" it self which simplifies terms
(for query suggestion) collecting. I saw something on GitHub to be used
with javascript but i cant remember now the name of the project.
att.
On Tue
Hi all,
I'm looking a solution for a multi-word suggester.
Reading Changing Bits, Mike McCandless's Blog, I saw some solutions that seem
working for a restricted number of input. I'm searching a suggester that works
as DirectSpellckecker o SpellChecker but with multi-word.
Any ideas?
thanks,
