I wonder if QueryParser.setAutoGeneratePhraseQueries() is exposed through
API.
From Lucene 3.1, the default value of AutoGeneratePhraseQueries becomes
"false" for some reason. It breaks CJK queries. To make CJK queries to work,
we need to call QueryParser.setAutoGeneratePhraseQueries(true).
Hi,
I wonder if QueryParser.setAutoGeneratePhraseQueries() is exposed through
API.
From Lucene 3.1, the default value of AutoGeneratePhraseQueries becomes
"false" for some reason. It breaks CJK queries. To make CJK queries to work,
we need to call QueryParser.setAutoGeneratePhraseQueries(true).
If it's not possible, can I open a ticket for it?
"break" might not be right word. It is "break" for us, though.
It doesn't return the same result as previous version and we need
QueryParser to behave the same as 3.0.
Hi,
I wonder if QueryParser.setAutoGeneratePhraseQueries() is exposed through
API.
From Lucene 3.1, the default value of AutoGeneratePhraseQueries becomes
"false" for some reason. It breaks CJK queries. To make CJK queries to
work,
we need to call QueryParser.setAutoGeneratePhraseQueries(true).
If it's not possible, can I open a ticket for it?
Yea, this field is not exposed in ES, open an issue, easy to expose.
On Tuesday, May 24, 2011 at 2:36 PM, Iori wrote:
Hi,
"break" might not be right word. It is "break" for us, though.
It doesn't return the same result as previous version and we need QueryParser to behave the same as 3.0.
Hi,
I wonder if QueryParser.setAutoGeneratePhraseQueries() is exposed through
API.
From Lucene 3.1, the default value of AutoGeneratePhraseQueries becomes
"false" for some reason. It breaks CJK queries. To make CJK queries to work,
we need to call QueryParser.setAutoGeneratePhraseQueries(true).
If it's not possible, can I open a ticket for it?
Hi,
"break" might not be right word. It is "break" for us, though.
It doesn't return the same result as previous version and we need
QueryParser to behave the same as 3.0.
Anyway, I will create a ticket.
Hi,
I wonder if QueryParser.setAutoGeneratePhraseQueries() is exposed
through
API.
From Lucene 3.1, the default value of AutoGeneratePhraseQueries becomes
"false" for some reason. It breaks CJK queries. To make CJK queries to
work,
we need to call QueryParser.setAutoGeneratePhraseQueries(true).
If it's not possible, can I open a ticket for it?
Yes, actually I ended up re-setting org.elasticsearch.common.lucene.Lucene.QUERYPARSER_VERSION using reflection.
But it looks I don't need it any more since this is already implemented
Iori
On Tuesday, May 24, 2011 at 14:33 , Michael McCandless wrote:
Ahh, OK, makes sense.
You (or ES) could also pass Version.LUCENE_30 as the "matchVersion"
param to QueryParser.
Hi,
"break" might not be right word. It is "break" for us, though.
It doesn't return the same result as previous version and we need
QueryParser to behave the same as 3.0.
Anyway, I will create a ticket.
Hi,
I wonder if QueryParser.setAutoGeneratePhraseQueries() is exposed
through
API.
From Lucene 3.1, the default value of AutoGeneratePhraseQueries becomes
"false" for some reason. It breaks CJK queries. To make CJK queries to
work,
we need to call QueryParser.setAutoGeneratePhraseQueries(true).
If it's not possible, can I open a ticket for it?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.