Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 2 Feb 2012 21:28:54 +0000 (UTC)
From: =?utf-8?Q?Jan_H=C3=B8ydahl_=28Commented=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1101811486.4806.1328218134869.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1855485731.27884.1326240759951.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-3026) eDismax: Locking down which fields
 can be explicitly queried (user fields aka uf)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Jan H=C3=B8ydahl commented on SOLR-3026:
-----------------------------------

Super duper. I tested it and it works great! Strange, I could not get alias=
ing 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=3D 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=3D*}} or=
 {{uf=3D-*}}. If we aim to let edismax replace dismax, people may want it t=
o behave like dismax out of the box. But if it won't replace dismax it's be=
tter to stick with the current defaults which people already are used to. N=
ote that since eDismax is still @lucene.experimental we should not be afrai=
d to change defaults.
               =20
> 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=C3=B8ydahl
>            Assignee: Jan H=C3=B8ydahl
>             Fix For: 3.6, 4.0
>
>         Attachments: SOLR-3026.patch, SOLR-3026.patch, SOLR-3026.patch, S=
OLR-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 e=
nd user as fielded search.
> In the original SOLR-1553, there's a patch implementing "user fields", bu=
t 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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
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