I have my own versioning system and I use it to keep index in sync with
other parts of the system. Just wanted to know if there is a shortcut to
keep it in the Lucene index and be able to read it by using something
similar to getCurrentVersion.
I guess I will have to store it somewhere outside of t
Arisem is a French ISV delivering best-of-breed text analytics software. We
are using Lucene in our products since 2001 and are in search of a Lucene
expert to complement our R&D team.
Required skills:
- Master degree in computer science
- 2+ years of experience in working with Lucene
- Stro
Would IndexReader:
/**
* Reads version number from segments files. The version number is
* initialized with a timestamp and then increased by one for each
change of
* the index.
*
* @param directory where the index resides.
* @return version number.
* @throws CorruptIndexEx
WildcardQuery won't be slower than TermQuery if there are no wildcard
characters. Beyond what QueryParser does, WildcardQuery itself
reverts to a TermQuery:
public Query rewrite(IndexReader reader) throws IOException {
if (this.termContainsWildcard) {
return super.rewrite(r
I'm not using the QueryParser at all. I need to do a little more with
the terms, so i'm explicitly creating a Query from a single term. What I
was hoping was to avoid something like this:
...
if(term.contains("*") || terms.contains("?") {
return new WildcardQuery(...
}
else {
return new T
Are you using the out of the box Lucene QueryParser? It will automatically
detect wildcard queries by the presence of * or ? chars.
If the user input does not contain these characters a plain TermQuery is used.
BooleanQuery.setMaxClauseCount can be used to control the upper limit on terms
produ
Hi,
I'm working my way through the Lucene In Action book, and there is one
thing I need explained that I didn't find there;
While wildcard queries are potentially slower than ordinary term
queries, are they slower even if theyt don't contain a wildcard?
Significantly slower?
The reason I a
