[
http://issues.apache.org/jira/browse/LUCENE-488?page=comments#action_12363524 ]
Daniel Naber commented on LUCENE-488:
-
writer.setMaxBufferedDocs(5); solves to OOM error, at least for binary stuff
that's 5MB. So with writer.setMaxBufferedDocs(1) you ca
On Samstag 21 Januar 2006 19:46, Chris Hostetter wrote:
> if you are flexible in the syntax you are willing to support, you can
> tell your users that they need to escape the colons that aren't ment as
> field identifiers...
>
> ID:CI\:123
Or you could use a regular expression to turn ID:
I don't want the users to have to use escape characters. I'd rather they
didn't have to use quotes.
Of course I think someone needs to go into the internals anyway... on 1.4.3
I get an index out of array bounds error (not a nice parse exception) when
it tries to parse the following (which it shoul
if you are flexible in the syntax you are willing to support, you can tell
your users that they need to escape the colons that aren't ment as field
identifiers...
ID:CI\:123
...alternately, you can tell them they have to quote colons...
ID:"CI:123"
...then you can avoid the who
Hello, I'm new here. I've actually started using dotLucene but I think I
need to make a change to the QueryParser but it's so complicated to try and
understand what it's doing I thought I'd ask if maybe one of you guys could
point me in the right direction?
In my implementation of Lucene I have th
