Hi,
Is someone able to explain the purpose of both these properties. By reading
the documentation I don't understand the benefit of setting the
termIndexInterval on the IndexWriter.
Thanks
Anuj
r wrote:
> You have everything you need to implement this. This is much easier to
> change the syntax.
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > F
/lucene-java-user/200910.mbox/%3cblu%0a140-w22f12e1c9ac650580e9852d0...@phx.gbl%3E>
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From:
Is there a query syntax for specifying a numeric range for a field indexed
as a NumericField.
I've tried
numericfield:[0 TO 10]
>
But it is parsed as a TermRangeQuery and not a NumericRangeQuery.
Many thanks
Anuj
On this issue, I ended up writing a simple interface and delegating proxy to
use for calls to IndexWriter methods.
It would be nice if future versions had an interface architecture around key
components to promote unit testing.
On 26 January 2011 17:27, Anuj Shah wrote:
> Thanks Uwe, t
ocks for new,
> test-driven & well-designed code."
>
> Does any of this apply to Lucene? It's open source, so you can look into
> source code and even change it!
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thet
wrote:
> ... and also the full exception?
>
> Mike
>
> On Tue, Jan 25, 2011 at 11:52 AM, Uwe Schindler wrote:
> > Can you post your code?
> >
> > -
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> &
Hi,
I've upgraded from 3.00 to 3.0.3 and am now hitting assertion errors from
IndexWriter.ReaderPool.commit, at this line:
// We invoke deleter.checkpoint below, so we must be
> // sync'd on IW:
> assert Thread.holdsLock(IndexWriter.this);
>
Has anyone encountered this before?
Apologies Erick, missed your question.
I'm on version 3.0
On Thu, Aug 5, 2010 at 11:52 AM, Anuj Shah wrote:
> Having delved a bit more into the code it looks like every MultiTermQuery
> descendant fails to implement the extractTerms method. This does make sense,
> as it is not po
e help
> Erick
>
> On Tue, Aug 3, 2010 at 5:02 AM, Anuj Shah wrote:
>
> > Thanks, that does seem good in theory. I can get the field from each of
> the
> > terms and add them to a Set to de-dupe.
> >
> > However, in practice queries of the following nature se
'll work for you.
> Note that the query must be rewritten, and that the set of terms will
> have duplicate fields. i.e. if you search field1:Erick +field1:James
> I expect you'll have two terms in the set that are on field1.
>
> Best
> Erick
>
> On Mon, Aug 2, 2010 a
2:21 AM, Erick Erickson wrote:
> Could you explain more about what you're trying to do? You're writing the
> query
> after all, so you probably already know what went into it.
>
> Which shows that I don't understand what you want to do at all.
>
> Best
> Eri
Hi,
Is there a way to get all the fields involved in a query?
Thanks
Anuj
13 matches
Mail list logo