Yonik Seeley wrote:
From the user's point of view I think it will make sense to
build a phrase query only when the quotes are found in the search string.
You make an interesting point Sergiu. Your proposal would increase
the expressive power of the QueryParser by allowing the constructio
Chris Hostetter wrote:
: Exactly this is my question, why the QueryParser creates a Phrase query
: when he gets several tokens from analyzer
: and not a BooleanQuery?
Because if it did that, there would be no way to write phrase queries :)
I'm not very sure about this ...
QueryParser only
Chris Hostetter wrote:
: I built a wrong query string "word1,word2,word3" instead of "word1
: word2 word3"
: therefore I got a wrong query: field:"word1 word2 word3" instead of
: field:word1 field:word2 field:word3.
:
: Is this an espected behaviour?
: I used Standard analyzer, probably the
Hi all,
I built a wrong query string "word1,word2,word3" instead of "word1
word2 word3"
therefore I got a wrong query: field:"word1 word2 word3" instead of
field:word1 field:word2 field:word3.
Is this an espected behaviour?
I used Standard analyzer, probably therefore, the comas were repl
Hi Christian,
That syntax is not entirely correct.
Search in the mailing list for "*term" or suffix queries
a few months ago I submitted the correct grammar that enables
suffix queries.
Best,
Sergiu
BOUDOT Christian wrote:
I have found in the QueryParser.jj those lines of comments:
// OG:
Ciau,
Ce mai faci?
Cred ca te-am mai intrebat ce lucrezi, dar am uitat.
In viitorul apropiat s-ar putea sa lucrez si eu putin in directia text
mining
si bineinteles ca am sa refolosesc ce e implementat in lucene.
S-ar putea ca munca noastra sa aiba ceva puncte comune .. te
intereseaza sa
ma
Kevin Burton wrote:
I have an index with a date field. I want to quickly find the minimum
and maximum values in the index.
Is there a quick way to do this? I looked at using TermInfos and
finding the first one but how to I find the last?
I also tried the new sort API and the performance
I think that the solution is to sort the results and to get the first
result.
See:
*org.apache.lucene.search.Sort
*
Best,
Sergiu
Kevin Burton wrote:
Andrew Boyd wrote:
How about using range query?
private Term begin, end;
begin = new Term("dateField",
DateTools.dateToString(Date.
Tansley, Robert wrote:
Hi all,
The DSpace (www.dspace.org) currently uses Lucene to index metadata
(Dublin Core standard) and extracted full-text content of documents
stored in it. Now the system is being used globally, it needs to
support multi-language indexing.
I've looked through the mail
eries:
// http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12137
// Change from:
// |
// (<_TERM_CHAR> | ( [ "*", "?" ] ))* >
// To:
//
// | | ( [ "*", "?" ] ))* >
//
//SG: or better, this definition
//| (<_TERM_CHAR> | ( [
"*"
Chris Lamprecht wrote:
It's a nice idea, and makes sense. I think that it can be broken if
boosting is used and the search is performed on multiple fileds, especially
unstored ones. In this case the distance between very similar documents
might be increased.
I think that also the duplications sho
Karthik N S wrote:
Hi Guys
Is there a way around for which the query parser would have something like
this
(+digital +camera +optics) -(All other Default variables)
But a run time Once cannot determine the default values.
I am stuck in between for this cause :(D
You can ask the u
Karthik N S wrote:
**
*Hi Guys*
*Apologies...*
*I have Indexed documents sucessfully and they would be
**Document 1 contains = ELECTRONICS DIGITAL CAMERA
***Document 2 contains = ELECTRONICS DIGITAL CAMERA BATTERY
ACCESSORIES*
*Document 3 contains* = ELECTRONICS DIGITAL CAME
Erik Hatcher wrote:
On Mar 8, 2005, at 5:17 PM, Chris Hostetter wrote:
Earlier in this thread...
: >>> +a -> a
: >>
: >> Hmmm this is a debatable one. It's returning a TermQuery in
this
: >> case for "a". Is that appropriate? Or should it return a
: >> BooleanQuery
: >> with a single TermQu
Chris Hostetter wrote:
Earlier in this thread...
: >>> +a -> a
: >>
: >> Hmmm this is a debatable one. It's returning a TermQuery in this
: >> case for "a". Is that appropriate? Or should it return a
: >> BooleanQuery
: >> with a single TermQuery as required?
: > Ok.
: > The question how to
Doug Cutting wrote:
sergiu gordea wrote:
So .. here is an example of how I parse a simple query string
provided by a user ...
the user checks a few flags and writes "test ko AND NOT bo"
and the resulting query.toString() is saved in the database:
+(+(subject:test descri
Erik Hatcher wrote:
On Mar 8, 2005, at 4:11 AM, sergiu gordea wrote:
In our project I save search strings, generated with query.toString
in the database and I reconstruct the Query at runtime.
I would appreciate if the new QueryParser will pass the following
assert:
Query query
es when after long debug sessions I discovered
silent exception drop ...
One of them was just yesterday ...
In an application, I handled this by dropping the query and notifying
the
user, that some part of the query could not be handled and was ignored.
How did your application notice that part
18 matches
Mail list logo
