[
https://issues.apache.org/jira/browse/SOLR-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13192238#comment-13192238
]
Jan Høydahl commented on SOLR-3026:
-----------------------------------
I think this is a good enough first step for user fields and aliasing feature.
Then if we want to take it further such as recursive aliasing from inside qf
params, we'll open new issues.
Not sure I got full test coverage for all combinations of fields, default
boosts etc.
Anyone wants to review it? There's bound to be some bugs with such string
manipulations...
> 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
>
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
