Hi,
Use FieldValueFilter for that:
http://lucene.apache.org/core/4_10_2/core/org/apache/lucene/search/FieldValueFilter.html
If you need a query instead of a Filter, wrap it with ConstantScoreQuery.
This is also much faster than a RangeQuery like suggested by Ahmed.
Uwe
-
Uwe Schindler
H.-H
Yes that all looks reasonable. Maybe there is a mismatch in the
analysis chain? I'm just throwing out wild guesses because I don't
really see any problems in what you shared. Also - if the problem
really has something to do with ControlledRealTimeReopenThread, I'm not
going to have the answe
Hi Sascha,
Generally RangeQuery is used for that, e.g. fieldName:[* TO *]
Ahmet
On Monday, December 1, 2014 9:44 PM, Sascha Janz wrote:
Hi,
is there a chance to add a additional clause to a query for a field that
should not be null ?
greetings
sascha
-
Thanks for your reply!
I try to delete documents using a term that matches a Document TextField:
private static final String NAME = "name";
private void store(String n, ... other fields ...) {
Document d = new Document();
d.add(new TextField(NAME, n, Field.Store.YES));
... add ot
It's impossible to tell since you didn't include the code for it, but my
advice would be to look at how the documents are being marked for
deletion. What are the terms being used to delete them? Are you trying
to use lucene docids?
-Mike
On 12/1/2014 4:22 PM, Badano Andrea wrote:
Hello,
M
Hello,
My apologies for a longish question.
I am having some problems with a class that tries to ensure that a lucene index
is
always kept up-to-date with the contents of a mysql master database. Users add,
modify, and delete items in the master database, and all changes to the master
database
Hi,
is there a chance to add a additional clause to a query for a field that
should not be null ?
greetings
sascha