Re: LUCENE-6766 index sorting and custom SortField

2016-08-15 Thread Michael McCandless
Hmm I see. Yeah, it seems like the only way forward is to explore SortField (and its subclasses) handling their own serialization, maybe via SPI (what we use for codecs), though that sounds somewhat heavy. Maybe open an issue for discussion? Mike McCandless http://blog.mikemccandless.com On Mo

Re: LUCENE-6766 index sorting and custom SortField

2016-08-15 Thread Andres de la Peña
Hi, We are using a custom SortField to sort Cassandra primary keys. The sort criteria is based on the marshalled values of each of the columns in the primary key

Re: Synchronous Lucene index update tests occasionally fail

2016-08-15 Thread Michael McCandless
OK, thanks for bringing closure! Mike McCandless http://blog.mikemccandless.com On Mon, Aug 15, 2016 at 7:19 AM, Daniq wrote: > I've simplified the test and it works OK. Possibly it was very deep > simplification) but likely the initial problem is in code from our side. > > > Daniq wrote > > O

Re: Combination of BooleanQuery and PhraseQuery

2016-08-15 Thread Erik Hatcher
Try combining into multiple clauses… (with q.op=OR) “some phrase”~ OR (some phrase) That would boost docs with with proximity, but still allow matches for docs that don’t contain all terms. Erik > On Aug 15, 2016, at 4:02 AM, Erel Uziel wrote: > > Hi, > Is there any query

Combination of BooleanQuery and PhraseQuery

2016-08-15 Thread Erel Uziel
Hi, Is there any query similar to BooleanQuery with SHOULD semantics that prefer documents where the terms are close to each other? I currently use a PhraseQuery with large slop for this. However this only works if all the terms are in the document. Best regards, Erel Uziel

Re: Synchronous Lucene index update tests occasionally fail

2016-08-15 Thread Daniq
I've simplified the test and it works OK. Possibly it was very deep simplification) but likely the initial problem is in code from our side. Daniq wrote > Ok, I'll try it a bit later. > Thank you. > Michael McCandless-2 wrote >> No, casing issues would not be random; it was just what I noticed in