[
https://issues.apache.org/jira/browse/SOLR-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12892330#action_12892330
]
Michael McCandless commented on SOLR-2015:
------------------------------------------
bq. The problem is not that we have an incorrect solution, but an incomplete
solution.
True, but... I think you're splitting hairs ;)
>From the user's standpoint, auto-phrase is flakey -- in some cases it
works, in others it doesn't.
{quote}
Let's assume we had a QP that didn't split on whitespace (or whatever our
optimal solution is).
IMO, I would still want tokens joined by a dash to form a phrase query, just
like tokens surrounded by quotes.
It's important information and shouldn't be discarded.
{quote}
I agree we shouldn't discard a user's dashes -- they are important.
Google also treats wizard-of-oz as a phrase query (Uwe seems
particularly fond of this!).
Hmm though I just tried wizard-of-oz, wizard of oz, and "wizard of
oz", and got 3 different sets of results, from Google... hmmm.
bq. We can have different text field types in a single schema - it's just a
matter of adding another one that's good for non-whitespace delimited languages?
OK this seems like a good solution for now, until we fix QP/Analyzer
to do this "privately".
> add a config hook for autoGeneratePhraseQueries
> -----------------------------------------------
>
> Key: SOLR-2015
> URL: https://issues.apache.org/jira/browse/SOLR-2015
> Project: Solr
> Issue Type: New Feature
> Affects Versions: 3.1, 4.0
> Reporter: Koji Sekiguchi
> Assignee: Yonik Seeley
> Priority: Blocker
> Fix For: 3.1, 4.0
>
> Attachments: SOLR-2015.patch, SOLR-2015.patch, SOLR-2015.patch
>
>
> After committed LUCENE-2458, a hook for autoGeneratePhraseQueries will be
> convenient for some situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
