RE: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-10-04 Thread Chris Hostetter
even if/when the schema is edited. : : Thanks! : Markus : : : : -Original message- : > From:Markus Jelsma : > Sent: Tuesday 3rd October 2017 15:18 : > To: solr-user@lucene.apache.org; Solr-user : > Subject: RE: Moving to Point, trouble with IntPoint.newRangeQuery() :

RE: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-10-03 Thread Markus Jelsma
solr-user@lucene.apache.org; Solr-user > Subject: RE: Moving to Point, trouble with IntPoint.newRangeQuery() > > Ok, i have stripped down the QParser to demonstrate the problem. This is the > basic test with only one document in the index: > > public void testPointRange() throws Exc

RE: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-10-03 Thread Markus Jelsma
lder.build(); } I might be overlooking things but i really don't so the problem with the second parse() impl. What am i doing wrong? Many thanks, Markus -Original message- > From:Chris Hostetter > Sent: Tuesday 26th September 2017 18:52 > To: Solr-user > S

RE: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-09-26 Thread Markus Jelsma
Thanks! I'll try it and get back later! -Original message- > From:Chris Hostetter > Sent: Tuesday 26th September 2017 18:52 > To: Solr-user > Subject: Re: Moving to Point, trouble with IntPoint.newRangeQuery() > > > : I have a QParser impl. that trans

Re: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-09-26 Thread Chris Hostetter
: I have a QParser impl. that transforms text input to one or more : integers, it makes a BooleanQuery one a field with all integers in : OR-more. It used to work by transforming the integer using : LegacyNumericUtils.intToPrefixCoded, getting a BytesRef. : : I have now moved it to use IntPoin

RE: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-09-26 Thread Markus Jelsma
- > From:Alan Woodward > Sent: Tuesday 26th September 2017 13:48 > To: solr-user@lucene.apache.org > Subject: Re: Moving to Point, trouble with IntPoint.newRangeQuery() > > The Points queries use a completely different data structure to the previous > range queries, so yo

Re: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-09-26 Thread Alan Woodward
The Points queries use a completely different data structure to the previous range queries, so you can’t just use them interchangeably, you have to reindex your data. I’m guessing your ‘d1’ field here is a TrieIntField or similar? Alan Woodward www.flax.co.uk > On 26 Sep 2017, at 12:22, Marku

Re: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-09-26 Thread Michael Kuhlmann
Arrgh, forget my question. I just see that newExactQuery() simply triggers newRangeQuery() like you already do. -Michael Am 26.09.2017 um 13:29 schrieb Michael Kuhlmann: > Hi Markus, > > I don't know why there aren't any results. But just out of curiosity, > why don't you use the better choice I

Re: Moving to Point, trouble with IntPoint.newRangeQuery()

2017-09-26 Thread Michael Kuhlmann
Hi Markus, I don't know why there aren't any results. But just out of curiosity, why don't you use the better choice IntPoint.newExectQuery(String,int)? What happens if you use that? -Michael Am 26.09.2017 um 13:22 schrieb Markus Jelsma: > Hello, > > I have a QParser impl. that transforms text

Moving to Point, trouble with IntPoint.newRangeQuery()

2017-09-26 Thread Markus Jelsma
Hello, I have a QParser impl. that transforms text input to one or more integers, it makes a BooleanQuery one a field with all integers in OR-more. It used to work by transforming the integer using LegacyNumericUtils.intToPrefixCoded, getting a BytesRef. I have now moved it to use IntPoint.new