Re: Range queries get misinterpreted when parsed twice via the "Standard" parsers

2017-03-10 Thread Michael McCandless
Why don't we fix this in Lucene? It sounds like your fix (overriding toQueryString for the range query nodes) is contained? Could you open an issue and add a patch? I agree it's silly to produce [ts:X ts:Y] syntax. Mike McCandless http://blog.mikemccandless.com On Thu, Mar 9, 2017 at 8:59 PM,

Re: Range queries get misinterpreted when parsed twice via the "Standard" parsers

2017-03-09 Thread Michael Peterson
Everyone - thanks for the feedback. Trejkaz, I agree. The [ts:X ts:Y] range syntax seems odd at best and broken at worst. If the field name for the range has to be the same for both the lower and upper bound why put it there twice inside the braces? In addition, a user cannot type that syntax and

Re: Range queries get misinterpreted when parsed twice via the "Standard" parsers

2017-03-09 Thread Trejkaz
On Fri, 10 Mar 2017 at 01:19, Erick Erickson wrote: > There has never been a guarantee that going back and forth between a > parsed query and its string representation is idempotent. so this > isn't supported. Maybe delete the toQueryString method... There is a fundamental design problem with

Re: Range queries get misinterpreted when parsed twice via the "Standard" parsers

2017-03-09 Thread Erick Erickson
There has never been a guarantee that going back and forth between a parsed query and its string representation is idempotent. so this isn't supported. Best, Erick On Thu, Mar 9, 2017 at 5:58 AM, Michael Peterson wrote: > Hello, > > At Rocana we have a search system that builds a Lucene query on