lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Issue Comment Edited) (JIRA) <j...@apache.org>
Subject [jira] [Issue Comment Edited] (SOLR-3026) eDismax: Locking down which fields can be explicitly queried (user fields aka uf)
Date Fri, 03 Feb 2012 00:24:53 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199240#comment-13199240
] 

Jan Høydahl edited comment on SOLR-3026 at 2/3/12 12:24 AM:
------------------------------------------------------------

Super duper. I tested it and it works great! Strange, I could not get aliasing for qf fields
to work before now. Now it works like a charm.

A possible optimization would be to detect if the f.who.qf= contains just a single field,
and create a simple TermQuery(?) instead of a DisMaxQuery in that case. But it might not be
important for performance..

Another thing to re-consider is whether the default should be {{uf=\*}} or {{uf=-\*}}. If
we aim to let edismax replace dismax, people may want it to behave like dismax out of the
box. But if it won't replace dismax it's better to stick with the current defaults which people
already are used to. Note that since eDismax is still @lucene.experimental we should not be
afraid to change defaults.
                
      was (Author: janhoy):
    Super duper. I tested it and it works great! Strange, I could not get aliasing for qf
fields to work before now. Now it works like a charm.

A possible optimization would be to detect if the f.who.qf= contains just a single field,
and create a simple TermQuery(?) instead of a DisMaxQuery in that case. But it might not be
important for performance..

Another thing to re-consider is whether the default should be {{uf=*}} or {{uf=-*}}. If we
aim to let edismax replace dismax, people may want it to behave like dismax out of the box.
But if it won't replace dismax it's better to stick with the current defaults which people
already are used to. Note that since eDismax is still @lucene.experimental we should not be
afraid to change defaults.
                  
> eDismax: Locking down which fields can be explicitly queried (user fields aka uf)
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-3026
>                 URL: https://issues.apache.org/jira/browse/SOLR-3026
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>    Affects Versions: 3.1, 3.2, 3.3, 3.4, 3.5
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>             Fix For: 3.6, 4.0
>
>         Attachments: SOLR-3026.patch, SOLR-3026.patch, SOLR-3026.patch, SOLR-3026.patch,
SOLR-3026.patch, SOLR-3026.patch, SOLR-3026.patch
>
>
> We need a way to specify exactly what fields should be available to the end user as fielded
search.
> In the original SOLR-1553, there's a patch implementing "user fields", but it was never
committed even if that issue was closed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message