Hi,
I am looking for an experienced and skilled Solr & Lucene developer/consultant
to work on a software project incorporating natural language processing and
machine learning algorithms. As part of a larger NLP/AI project that is under
way, we need someone to install, refine and optimize Solr
Actually, there are no results in the range [l220-2 TO l220-10]
This is basically a string comparison, and l220-2 > l220-10 so
this range would never match.
Best
Erick
On Tue, May 17, 2011 at 1:51 PM, G.Long wrote:
> I set the field article to NOT_ANALYZED and I didn't quoted the article
> valu
I set the field article to NOT_ANALYZED and I didn't quoted the article
values in the range part of the query and it looks like it works better now.
However, some results are still missing. For exemple, sometimes a range
like [l220-2 TO l220-10] will not return any results (although i'm sure
t
Could it be as simple as a missing colon after article in +code:CCOM
+article[l123-12 TO l123-14]?
If not, double check analyzers, see what Luke shows as indexed terms
for that field, work through the FAQ info posted earlier. And play
with quotes - sometimes you show your article values quoted, s
I added a standard analyzer and a Query Parser to parse each boolean
clause of my query and i got some results :)
But now there are some strange behaviors.
the following queries :
+code:CCOM +article:"l123-12"
+code:CCOM +article:"l123-13"
+code:CCOM +article:"l123-14"
return one result.
Howe
It's likely to have something to do with analyzers. That is the
usually the first thing to come to mind if queries hold upper or mixed
case terms. Maybe Luke is using an analyzer that matches the one you
used when you indexed your documents.
You can use Luke to see what is being stored in the in
Hi Uwe :)
Thank you for your answer ! Now I have another problem. Here is the code
I use to query the index :
ScoreDoc[] hits = null;
TopFieldCollector collector = TopFieldCollector.create(new
Sort(SortField.FIELD_DOC), 20, true, false, false, false);
Directory directory =
Hi,
Let's say we have an index having few documents indexed using
StopAnalyzer.ENGLISH_STOP_WORDS_SET. The user issues two queries:
1) foo:bar
2) baz:"there is"
Let's assume that the first query yields some results because there
are documents matching that query.
The second query contains two st
Hi, I know it is too late to answer a question (sorry Chris) but I thought
it could be useful to share things (even late).
I was just going through the mails and I found that we've done it a few
months back.
*Objective: To add a new field to existing index without re-writing the
whole index.*
We
Hi,
Query q = new TermRangeQuery(...)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: G.Long [mailto:jde...@gmail.com]
> Sent: Tuesday, May 17, 2011 1:53 PM
> To: java-user@lucene.apache.org
> Subj
Hi there :)
I would like to perform a range query on a lucene index. I'm using
lucene 3.1 api.
I looked at the javadoc and found a rangeQueryNode but i'm not sure how
to use it.
I've got a field "article" in my index which is indexed this way :
entry.add(new Field("article", article, Field.S
Anyone else able to reply to this?
Thanks
Greg
-Original Message-
From: Gregory Tarr
Sent: 13 May 2011 15:46
To: 'java-user@lucene.apache.org'
Subject: RE: SpanNearQuery - inOrder parameter
Chris, and others
Thanks for your reply. In effect what you are saying is that
SpanNearQuery wo
12 matches
Mail list logo
