Hi,
I've been going nuts trying to use LuceneParser parse query
strings using the default operator AND correctly:
String queryString = getQueryString();
QueryParser parser = new QueryParser(text, new StandardAnalyzer());
parser.setDefaultOperator(QueryParser.AND_OPERATOR);
try {
Query q =
i`m in Beijing,reading Hadoop/Lucene/Nutch source code every day.
On 10/9/07, qi wu [EMAIL PROTECTED] wrote:
Hi,
I find some people from China also are in Lucene related mail list. Do any
one have interest to meet together for exprience sharing or just for known
each other.
If you were
xing , wo ye canjia .
ok , I am enrolled.
tian chunfeng
On 10/9/07, KenWu [EMAIL PROTECTED] wrote:
i`m in Beijing,reading Hadoop/Lucene/Nutch source code every day.
On 10/9/07, qi wu [EMAIL PROTECTED] wrote:
Hi,
I find some people from China also are in Lucene related mail list. Do
I certainly applaud your effort to dig in and find out what's going on!
However, I suspect you'll get farther faster by trying one of several
tactics:
1 post the indexing code and the searching code in snippet form. This
kind of issue is usually a problem with analyzers. That is, perhaps
Uttam,
To unsubscribe you need to send an email to
[EMAIL PROTECTED]
--
Joe Attardi
[EMAIL PROTECTED]
http://thinksincode.blogspot.com/
On 10/9/07, Barik, Uttam [EMAIL PROTECTED] wrote:
Regards,
Uttam Kumar Barik
IT Services
Fidelity Business Services India Pvt. Limited
I'm currently using rangeFilter's and queryWrapperFilter's to get around
the max boolean clause limit.
A couple of questions concerning this:
1) Is it good design practice to substitue every term containing a
wildcard with a queryWrapperFilter, and a rangeQuery with a RangeFilter
and
I think you shouldn't worry about it until you can demonstrate that
you actually have a space problem. Worrying about storing
an extra 3M is almost certainly a waste of time.
What evidence do you have that this is any kind of problem
at all?
Best
Erick
On 10/9/07, Narendra yadala [EMAIL
Note that as of Lucene 2.1 QueryParser was changed to use RangeFilters in place
of RangeQuerys by default.
You can simply subclass QueryParser to override construction of wildcardQuerys
etc. These methods are over-ridable to provide a hook for you to return a Query
object of your choosing
WooHoo! That's good news.
Now I seee the ConstantScoreRangeQuery in QueryParser.getRangeQuery.
So all I have to do is over-ride QueryParser.getWildcardQuery.
-Original Message-
From: mark harwood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 09, 2007 10:57 AM
To:
Peter - LIA2 is in progress! :) LIA2IP?
Otis (hi Erik! ;))
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Simpy -- http://www.simpy.com/ - Tag - Search - Share
- Original Message
From: Peter W. [EMAIL PROTECTED]
To: java-user@lucene.apache.org
Sent: Tuesday,
On Tuesday 09 October 2007 09:55, Martin Dietze wrote:
I've been going nuts trying to use LuceneParser parse query
strings using the default operator AND correctly:
The operator precedence is known to be buggy. You need to use parenthesis,
e.g. (aa AND bb) OR (cc AND dd)
regards
Daniel
--
Hi-
We are a startup in the web indexing space. We are looking for an
experienced search engine developer for our team. We are using Solr and
Lucene, but search is search and solid experience with any large search
engine is welcome.
At this point we do not wish to disclose our name. We have
Cool!
The quality of first LIA really shined even for
those familiar with Java but new to assertions
and unit tests. Can't wait to buy LIA2...
Please accept the request to include FieldSelector,
QueryWrapperFilter, Lucli, MemoryIndex, MoreLikeThis,
Payload, ScoreDoc, TermDocs, ValueSourceQuery,
Hi everyone,
I have a question that I can't quite seem to find the answer to by
googling or searching the archives of this mailing list. The problem
is I would like to weight some fields more than others. Assume that I
have three fields: title, author, and default where title and author
contain
14 matches
Mail list logo
