Nested Facets

2019-08-29 Thread Matthias Müller
For an application that already has a Lucene Index, I would like to implement a facet search that return result aggregations in two dimensions. From the Lucene examples [1] I can see how to do a simple facet search that collects facets in one dimension but I haven't seen any examples for a two-step

Re: Best fuzzy match on multiple terms

2019-06-14 Thread Matthias Müller
e) > > i would expect the second result below to be the first result as it > is > shorter and closest hit and first result to be the second result. > > NASHUA in results: MAIN DUNSTABLE NASHUA HILLSBOROUGH NEW HAMPSHIRE > UNITED STATES in the 0 th result > NASHUA in re

Re: Best fuzzy match on multiple terms

2019-06-14 Thread Matthias Müller
String()); > > } > > == > > > > I hope it helps :D > > > > Best regards, > > Namgyu Kim > > > > P.S. For BM25, the default value in Lucene is k1 = 1.2, b = 0.75. > > > > 2019년 6월 14일 (금) 오

Best fuzzy match on multiple terms

2019-06-13 Thread Matthias Müller
I am currently matching botanic names (with possible mis-spellings) against an indexed referenced list with Lucene. After quick progress in the beginning, I am struggeling with the proper query design to achieve a ranking result I want. Here is an example: Search term: Acer campestre 'Rozi' Toke

Re: RamDirectory vs MemoryIndex vs MMapDirectory for In-Memory-Index

2018-09-25 Thread Matthias Müller
ifference > compared to MMapDirectory is typically not worth the hassle. See this > issue for more discussion. > > https://issues.apache.org/jira/browse/LUCENE-8438 > > Dawid > On Tue, Sep 25, 2018 at 10:44 AM Matthias Müller > wrote: > > > > Hi, > > &

RamDirectory vs MemoryIndex vs MMapDirectory for In-Memory-Index

2018-09-25 Thread Matthias Müller
Hi, Lucene provides different storage options for in-memory indexes. I found three structures that would qualify for the task: * RamDirectory (which I currently use for prototyping, but wonder if it is the ideal choice for my task) * MemoryIndex, which claims to have better performance and resour

Re: No varargs paraemters in LongRange?

2017-09-02 Thread Matthias Müller
... too quick typing. Of course the highlander principle is at work - there can only be one. Am Samstag, den 02.09.2017, 09:27 +0200 schrieb Matthias Müller: > (lucene 6.6.0) > > Hi, > > is there a reason why LongRange only provides array-based > constructors > and que

No varargs paraemters in LongRange?

2017-09-02 Thread Matthias Müller
(lucene 6.6.0) Hi, is there a reason why LongRange only provides array-based constructors and queries, while LongPoint features varargs? -Matthias - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional