> Is anyone else out there creating a tutorial. I would be willing to
> compile and coordinate all the different parts for the people who want
> to contribute.
I wrote something up a few months ago, and posted it to the list.
I've been meaning to get back to it, edit it again, spiff it up
Lucene does not implement a standalone "NOT" query. (Probably BooleanQuery
should throw an exception if all clauses are prohibited clauses.) Negation
is only implemented with respect to other non-negated clauses.
So you cannot directly model your query tree as a Lucene query tree. NOT
nodes mu
Are brackets, [ and ], legal in a query?
If so, do they have some special meaning?
If not, are there other "illegal" characters as well?
Parsing the query syntax, "[]", causes the following error:
Lexical error at line 1, column 3. Encountered: after : "[]"
org.apache.lucene.queryParser.Toke
I had the same problem and have started to write down all my own notes
and experiences. I was hoping this could be put into a manual/tutorial
in the future.
I was going to wait until it was a bit more robust, but let's see if we
can create some coordination.
Is anyone else out there creating a
Hello,
I have some trouble understanding the semantics of the BooleanQuery with
regards to prohibited clause.
the method I am using is this:
public final void add(Query query, boolean required, boolean prohibited)
in the class BooleanQuery.
I am not using the QueryParser, but instead I buil
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Haven't seen any really simple tutorials since I've been using it. The best
place to start though is the FAQ at
http://www.lucene.com/cgi-bin/faq/faqmanager.cgi . I read completely through
it several times and was finally a
Hi,
I am new user, I would truly appreciate if someone
could tell me where I can find a Tutorial or
Documentation for Lucene which will guide me through
how to get started and do a simple search test.
Thank You,
DV
__
Do You Yahoo!?
Make a great co
This should work. You should be able to find an un-tokenized field
containing spaces with a TermQuery. Nothing should ever tokenize the
string.
Can you please supply a simple, self-contained example showing that this
does not work?
Thanks,
Doug
> -Original Message-
> From: Winton Dav
Hi,
(Apologies if this shows up twice).
If I do a search such as "field1:jim OR field2:bob" is there any way to
determine for each document that was a hit, which field caused the hit?
Or rather, since they both might, is there any easy way to find out
which fields definitely didn't cause a hit
Hi,
I have a field which I need to match exactly -- Ideally it shouldn't
even be tokenized, but I can't find a way to do that -- adding a
field that is indexed but not tokenized, doesn't seem to work -- or
at least a Term Query doesn't work.
eg the field is "x y z" -- and I do a phrase qu
Its a problem with the query parser, but this is not the correct fix.
I think this fix just masks the problem.
> I think it's the bug of QueryParser.jj file because there the term is
> definied as character string that begins with any English character.
>
> Modify a line in the QueryParser.jj:
>
11 matches
Mail list logo