[
https://issues.apache.org/jira/browse/SOLR-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003064#comment-15003064
]
Yonik Seeley commented on SOLR-3191:
------------------------------------
I think new features should be free to ignore funky field name... no back
compat requirements.
Changing existing APIs... I don't know. I guess it depends on how many cases
there are out there of funky names, how many of them will upgrade, and what the
cost is to us to support.
bq. That's a good question about field aliases - a number literal, for example,
wouldn't be a valid Solr field name by these rules. So I think field aliases
are fair game to be funky.
My guess is that Scott was referring to just the alias name... as in
<alias_name> : <alias_value>, where alias_value can be a function query,
literal, or transformer, as well as another field.
> field exclusion from fl
> -----------------------
>
> Key: SOLR-3191
> URL: https://issues.apache.org/jira/browse/SOLR-3191
> Project: Solr
> Issue Type: Improvement
> Reporter: Luca Cavanna
> Priority: Minor
> Attachments: SOLR-3191.patch, SOLR-3191.patch, SOLR-3191.patch,
> SOLR-3191.patch
>
>
> I think it would be useful to add a way to exclude field from the Solr
> response. If I have for example 100 stored fields and I want to return all of
> them but one, it would be handy to list just the field I want to exclude
> instead of the 99 fields for inclusion through fl.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
