Thanks Mark!
I have to mention Benoit Mercier here who worked with me so we could
understand how to expand a term and use TOKEN_MGR_DECLS.
Patrick
On 10/13/06, Mark Miller <[EMAIL PROTECTED]> wrote:
Great work Patrick. I was unfamiliar with the use of TOKEN_MGR_DECLS.
Looks
like a powerfull f
Submitted to Jira with key LUCENE-682
Patrick
Grant Ingersoll wrote:
Hi Patrick,
Thanks for the work. Create a bug in JIRA and upload a patch (see svn
diff). See the Wiki for information on how to contribute.
Thanks,
Grant
-
Great work Patrick. I was unfamiliar with the use of TOKEN_MGR_DECLS. Looks
like a powerfull feature for dynamic token selection. Thanks a lot,
- Mark
On 10/13/06, Patrick Turcotte <[EMAIL PROTECTED]> wrote:
Mark Miller wrote:
> Could you say in a few words what you did to accomplish this? I k
Mark Miller wrote:
Could you say in a few words what you did to accomplish this? I know that
you mentioned you used a resource bundle, but what part of the code reads
this resource bundle? What method did you use to get by the JavaCC
issues?
Basically:
* I used TOKEN_MGR_DECLS to decla
Had this page open for somebody else:
http://wiki.apache.org/jakarta-lucene/HowToContribute
Otis
- Original Message
From: Patrick Turcotte <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Friday, October 13, 2006 10:40:27 AM
Subject: QueryParser syntax French Operator
Could you say in a few words what you did to accomplish this? I know that
you mentioned you used a resource bundle, but what part of the code reads
this resource bundle? What method did you use to get by the JavaCC issues?
thanks,
-Mark
On 10/13/06, Patrick Turcotte <[EMAIL PROTECTED]> wrote:
Hi Patrick,
Thanks for the work. Create a bug in JIRA and upload a patch (see
svn diff). See the Wiki for information on how to contribute.
Thanks,
Grant
On Oct 13, 2006, at 10:40 AM, Patrick Turcotte wrote:
Hello!
This may not be the best place for this message, sorry if this is
the
Hello!
This may not be the best place for this message, sorry if this is the
case, but since this is the result of a question I asked here, I decided
to post it here. If I'm in error, please refer me to the best procedure.
Thanks!
I've completed the desired "patch". I now have a version of t
runtime using the
ResourceBundle paradigm. I'll keep you posted.
Patrick
> -Message d'origine-
> De : karl wettin [mailto:[EMAIL PROTECTED]
> Envoyé : 8 octobre, 2006 10:14
> À : java-user@lucene.apache.org
> Objet : Re: QueryParser syntax French Operator
>
>
On 10/8/06, Otis Gospodnetic <[EMAIL PROTECTED]> wrote:
Hi Patrick,
If I were trying to do this, I'd modify QueryParser.jj to construct the grammar
for boolean operators based on something like Locale (or LANG env. variable?).
I'd try adding code a la:
en_AND = AND
en_OR = OR
en_NOT = NOT
fr_
if (locale is 'fr')
// construct the grammar with fr_*
...
Something like that.
Otis
- Original Message
From: Patrick Turcotte <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Tuesday, October 3, 2006 11:15:56 AM
Subject: QueryParser syntax French Operator
I've started to look into this (and the whole javacc syntax) I'll keep
you posted on my results.
Patrick
Erik Hatcher wrote:
Currently AND/OR/NOT are hardcoded into the .jj file. A patch to make
this configurable would be welcome!
Erik
On Oct 3, 2006, at 11:15 AM, Patrick Turcotte w
On Oct 4, 2006, at 2:18 AM, Ronnie Kolehmainen wrote:
Wouldn't the easiest fix be to just alter the users query string
before passing
it to queryparser (moving the semantics of your search app outside
of lucene)?
Something like:
str.replaceAll(" ET ", " AND ").replaceAll(" OU ", " OR
").
Wouldn't the easiest fix be to just alter the users query string before passing
it to queryparser (moving the semantics of your search app outside of lucene)?
Something like:
str.replaceAll(" ET ", " AND ").replaceAll(" OU ", " OR ").replaceAll(" SAUF ",
" NOT ")
Citerar Mark Miller <[EMAIL PROT
Oh wouldn't we all. I want this too. Unfortunately, it's an elusive
beast at best. As I am sure you know, JavaCC generates code based on the
grammar and so it is very hard to alter the grammar after JavaCC'ing it.
If you relax the 'add' part then you might be able to do something with
QueryPars
Currently AND/OR/NOT are hardcoded into the .jj file. A patch to
make this configurable would be welcome!
Erik
On Oct 3, 2006, at 11:15 AM, Patrick Turcotte wrote:
Hi,
Is there a way to add / replace the text for the boolean operators
used
by the query parser?
We would like to
Hi,
Is there a way to add / replace the text for the boolean operators used
by the query parser?
We would like to replace (or even better, add), "AND", "OR" and "NOT" by
"ET", "OU" and "SAUF".
Is there a way to configure the QueryParser to do it?
We know we could always modify QueryParser.jj to
17 matches
Mail list logo
