lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (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 10:53:53 GMT

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

Tomás Fernández Löbbe edited comment on SOLR-3026 at 2/3/12 10:52 AM:
----------------------------------------------------------------------

I think the default should be uf=\*, otherwise it will be confusing. I think "field" search
together with "dismax" search will be one of the main reasons why people will move from other
QP to edismax, and with uf=\-\* they will not get that behavior until they explicitly change
it. I bet that if we use uf=\-\* we'll get many questions related to this in the mailing list.

About the optimization, I think its a good idea, however it should be a different Jira. The
optimization could be applied to f.who.qf as well as to qf= right?
                
      was (Author: tomasflobbe):
    I think the default should be uf=\*, otherwise it will be confusing. I think "field" search
together with "dismax" search will be one of the main reasons why people will move from other
QP to edismax, and with uf=-\* they will not get that behavior until they explicitly change
it. I bet that if we use uf=-\* we'll get many questions related to this in the mailing list.

About the optimization, I think its a good idea, however it should be a different Jira. The
optimization could be applied to f.who.qf as well as to qf= right?
                  
> 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