The length of token has to be shorter than 255, otherwise there will
be unpredictable behaviors for this tokenizer. I see 255 is set as a
private final in the src code, but there is no documentation to explicitly
address that. Can we either make that number configurable (if not an
option, I'd like
At a side note, there is a race condition in your code: what if a search on
the old reader is in progress while you call reader.close()? You need to
call reader incref (should be tryincref, as you need to consider what if
the reader is closed at the moment you call incref on it) and decref
wheneve
The standard analyzer will discard most special characters as punctuation.
What analyzer are you using?
-- Jack Krupansky
-Original Message-
From: Scott Selvia
Sent: Thursday, August 14, 2014 7:42 PM
To: java-user@lucene.apache.org
Subject: Searching with String that Represents a Sign
We have OCR a document with a signature, you can select the signature and copy
the text representation for searching in a lucene 4.7 index. We have
surrounded the search text with double quotes since it has invalid search
characters without the use of the double quotes.
Search Text: ":J!/z&”
3.6 is quite old by now ... but that behavior (100s pause on reopen)
is strange. Can you capture all Java threads during that time and
post back?
It looks like you're reopening the reader correctly, though be careful
if you have in-flight searches running in other threads; use
SearcherManager to
Have a look at this article if you have not already gone through it.
http://blog.mikemccandless.com/2011/06/lucenes-near-real-time-search-is-fast.html
On Thu, Aug 14, 2014 at 11:16 PM, Michael Jennings <
mike.c.jenni...@gmail.com> wrote:
> Hi everyone,
>
> I'm a bit of a Lucene newb, but a fairl
Hi everyone,
I'm a bit of a Lucene newb, but a fairly experienced Java developer. Hope
someone can give me some clues as to what I may be doing wrong.
In essence I've got a lucene index built off of a database table that gets
updated at a rate of about 1 row changing every 2 seconds or so. I've g
I think we should expose commit? Can you open an issue?
And fix the NPEs to be a more informative exc? E.g.
IllegalStateException w/ a reasonable message ...
You should be able to init AIS on a previously built suggester, not
.build() it every time your application starts...
Mike McCandless
h
I've been using AIS, and I see that it now has support for incremental
updates, which is great! I'm looking forward to getting suggestions from
newly-added documents without the need to rebuild the entire suggester
index. I've run into a few problems though, and I want to see if there
is a bett
I opened https://issues.apache.org/jira/browse/LUCENE-5883 to handle that.
Shai
On Thu, Aug 7, 2014 at 6:42 PM, Uwe Schindler wrote:
> This is a good idea, because sometimes it's nice to change the MergePolicy
> on the fly without reopening! One example is
> https://issues.apache.org/jira/brow
10 matches
Mail list logo
