On Fri, Feb 17, 2017 at 11:14 AM, Erick Erickson
wrote:
> Lucene query logic is not strict Boolean logic, the article above explains
> why.
tl;dr it mostly comes down to scoring and syntax.
The scoring argument will depend on how much you care. (My care for
scoring is pretty close to zero, as I
take a look at this blog by Hossman:
https://lucidworks.com/2011/12/28/why-not-and-or-and-not/
Lucene query logic is not strict Boolean logic, the article above explains why.
Best,
Erick
On Thu, Feb 16, 2017 at 2:08 PM, Trejkaz wrote:
> On Fri, Feb 17, 2017 at 5:42 AM, Michael Peterson wrote:
I am using org.apache.lucene.queryparser.classic.QueryParser to generate my
queries in Lucene 6.4.1 and the class level docs indicate there is a "new"
QueryParser in contrib. I am wondering if the documentation in the class
is accurate and if so, where is this "new" QueryParser implementation.
I'v
On Fri, Feb 17, 2017 at 5:42 AM, Michael Peterson wrote:
> I have a question about the meaning and behavior of grouping behavior with
> Lucene queries.
For this query:
host:host_1 AND (NOT location:location_5)
The right hand side is:
NOT location:location_5
Which matches nothing, as i
I have a question about the meaning and behavior of grouping behavior with
Lucene queries.
In particular, here is the scenario I am testing. I have indexed 1,000
documents.
|---+---+---|
| # | Query String | Result (
Hi,
Remove the setReader()? Tokenizers do not need a Reader when they are
constructed (as they are for reuse). Once created the same instance is used
over and over, so it is initialized with a Reader before each use. This was
never different in the past, the was just the additional hurdle to ha
Ah... right I misunderstood your question, thought you were asking for
the list f feature differences between 5x and 6x.
There is never much development work done that far back, this was a
special case. There will almost certainly never be features developed
on the old major version this far into
Hi all,
I'm porting few classes from 4.8.1 to the newer version of Lucene. I can't
understand how to convert this code, I hope you can help me:
public Analyzer creaAnalyzer() {
return new Analyzer() {
@Override
protected TokenStreamComponents createComponents(String fieldName, Reader
arg1
Adrien, that is what I was looking for...I am using 6.4.1 but was curious
about the different branches. Thanks again.
J.D. Corbin
Senior Research Engineer
Advanced Computing & Data Science Lab
3075 W. Ray Road
Suite 200
Chandler, AZ 85226-2495
USA
M: (303) 912-0958
E: jd.cor...@pearson.com
Lucene 6.x is the stable branch while Lucene 5.x is the old stable branch.
We would advise you to use 6.x if possible as it has more frequent releases
and contains improvements that 5.x does not have.
Le jeu. 16 févr. 2017 à 17:18, Corbin, J.D. a
écrit :
> Hi,
>
> I am aware of the changes docum
Hi,
I am aware of the changes documented, I was just curious why there are two
baselines for Lucene, e.g., 5.x and 6.x. I would have assumed that 5.x was
a precursor to 6.x, but obviously lucene has separate tracks for 5.x and
6.x.
I'll look again at the changes and see if it details what is the
Please read the CHANGES.txt in both the lucene and solr directories
for all the changes between versions. The "New Features" section is
probably the best overview, while the detailed bug changes are also
listed. Both of the above are defined for each release.
Best,
Erick
On Thu, Feb 16, 2017 at 7
Today I noticed there is a new release of Lucene v5.5.4. What is the major
difference(s) between the 5.x and 6.x lines of Lucene.
Thanks,
J.D. Corbin
13 matches
Mail list logo
