Hi Lucene users,
I am in the beginning of implementing a Lucene application which would
supposedly search through some log files.
One of the requirements is to return results between a time range. Let's
say these are two lines in a series of log files:
2015-02-08 00:02:06.852Z INFO...
...
2015-02
Hi,
I am trying out pagination in lucene. I did it in two ways. The first
one by mentioning the offset position in topdocs(). This is a piece of code
I am trying out to achieve the same scenario using searchAfter().This works
fine but since I have a web appication, how will I do deep paging to
On Sun, Feb 8, 2015 at 9:04 PM, Uwe Schindler wrote:
> Hi,
>
> Lucene does not use algebraic / boolean logic! Maybe review this blog
> post: https://lucidworks.com/blog/why-not-and-or-and-not/
This article is an old classic.
The "plus, minus, nothing" operators aren't without their issues
either
Hi,
Lucene does not use algebraic / boolean logic! Maybe review this blog post:
https://lucidworks.com/blog/why-not-and-or-and-not/
As you see in your examples and how the wqueries are parsed, AND, OR, and NOT
are mapped to something else: Lucene only knows if a term MUST be in results,
or SHO
The G1C1 issue reference by Robert Muir on the Wiki page is at a
Lucene level. Lucene, of course, is critically important to Solr so
from that perspective it is about Solr too.
https://wiki.apache.org/lucene-java/JavaBugs
And, I assume, it also applies to your custom app.
FWIW,
Erick
On Fri, Fe
Hello.
My question was general. As in this thread G1 garbage collector was
discussed.
So lucene wiki says to not use it. But on the other side solr wiki says
that it is ok.
But solr is using lucene.
So the wuestion was who is right?
Regards
On 6 Feb 2015 18:12, "McKinley, James T" wrote:
> Just
Hello,
I am trying to understand whether I am using the NOT operator correctly. I have
the following scenario:
Query 1 = body:(a OR NOT b)
This is parsed as: (body:a) -(body:b) and finds 96,620 hits
Query 2 = body:(a OR (*:* AND NOT b))
This is parsed as: (body:a) (+*:* -(body:b)) and finds 1
So I dug into this a bit further, and find it happens with the stock
Lucene query as well, in 4.10.2. I looked at the code on trunk, and I
don't think the situation is different there. Basically if you delete a
parent document, orphaning some child document(s) and then merge, the
TPBJQuery fa
Hi,
Sorry for my ignorance, how do I obtain AtomicReader from a IndexReader?
I figured above code but it gives me a list of atomic readers.
for (AtomicReaderContext context : reader.leaves()) {
NumericDocValues docValues = context.reader().getNormValues(field);
if (docValues != null)
normValu
