On 06/03/2015 15:07, Michael McCandless wrote:
On Thu, Mar 5, 2015 at 4:27 PM, Paul Taylor wrote:
On 05/03/2015 19:01, Michael McCandless wrote:
On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor
wrote:
On 05/03/2015 15:53, Paul Taylor wrote:
On 05/03/2015 14:43, Michael McCandless wrote:
It loo
On 06/03/2015 17:34, Michael McCandless wrote:
On Fri, Mar 6, 2015 at 11:03 AM, Paul Taylor wrote:
Right, did you see my last post the query parser does trap the exception if
you enable assertions. I thought this was what you were saying was fixed in
a later version, but assume you actually me
On Fri, Mar 6, 2015 at 11:03 AM, Paul Taylor wrote:
> Right, did you see my last post the query parser does trap the exception if
> you enable assertions. I thought this was what you were saying was fixed in
> a later version, but assume you actually mean search is fixed not parser
Well it's bot
On 06/03/2015 15:07, Michael McCandless wrote:
On Thu, Mar 5, 2015 at 4:27 PM, Paul Taylor wrote:
On 05/03/2015 19:01, Michael McCandless wrote:
On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor
wrote:
On 05/03/2015 15:53, Paul Taylor wrote:
On 05/03/2015 14:43, Michael McCandless wrote:
It loo
On Thu, Mar 5, 2015 at 4:27 PM, Paul Taylor wrote:
> On 05/03/2015 19:01, Michael McCandless wrote:
>>
>> On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor
>> wrote:
>>>
>>> On 05/03/2015 15:53, Paul Taylor wrote:
On 05/03/2015 14:43, Michael McCandless wrote:
>
> It looks like field
On 05/03/2015 21:27, Paul Taylor wrote:
FWIW if I do enable assertions then parse does throw an assertion before
actually trying to do the search.
java.lang.AssertionError
at
org.apache.lucene.search.MultiTermQuery.(MultiTermQuery.java:252)
at
org.apache.lucene.search.AutomatonQuery.(
On 05/03/2015 19:01, Michael McCandless wrote:
On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor wrote:
On 05/03/2015 15:53, Paul Taylor wrote:
On 05/03/2015 14:43, Michael McCandless wrote:
It looks like field was null?
Back in 4.1.0 we just assert field != null, but in newer releases it's
a rea
On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor wrote:
> On 05/03/2015 15:53, Paul Taylor wrote:
>>
>> On 05/03/2015 14:43, Michael McCandless wrote:
>>>
>>> It looks like field was null?
>>>
>>> Back in 4.1.0 we just assert field != null, but in newer releases it's
>>> a real check.
>>>
>>> Mike McC
On 05/03/2015 15:53, Paul Taylor wrote:
On 05/03/2015 14:43, Michael McCandless wrote:
It looks like field was null?
Back in 4.1.0 we just assert field != null, but in newer releases it's
a real check.
Mike McCandless
Hi, thankyou Il try and get the query logged for when it next happens
Okay
On 05/03/2015 14:43, Michael McCandless wrote:
It looks like field was null?
Back in 4.1.0 we just assert field != null, but in newer releases it's
a real check.
Mike McCandless
Hi, thankyou Il try and get the query logged for when it next happens
Paul
---
It looks like field was null?
Back in 4.1.0 we just assert field != null, but in newer releases it's
a real check.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Mar 5, 2015 at 8:25 AM, Paul Taylor wrote:
> Hi
>
> Is this a Lucene (4.1.0) (known) bug or application code error, (I don'
11 matches
Mail list logo
