lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3026) eDismax: Locking down which fields can be explicitly queried (user fields aka uf)
Date Fri, 03 Feb 2012 21:34:54 GMT

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

Hoss Man commented on SOLR-3026:
--------------------------------

bq. If we aim to let edismax replace dismax, people may want it to behave like dismax out
of the box

I don't think that should be the goal.  plenty of people are using "edismax" already because
they like the fact that it is a super set of the dismax & lucene features, and the defaults
for "edismax" should embrace that.  

if/when EDisMaxQParser reaches the point that it can be configured to work exactly the same
as DisMaxQParser, then it may be worth considering defaulting "dismax" => an EDisMaxQParser
instance configured that way, but that doesn't mean "edismax" shouldn't expose all of it's
bells and whistles by default.

uf=* as a default should be fine -- the only reason to question it would be if it was hard
to disable, but the "-*" syntax is so easy it's not worth worrying about it.
                
> 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