[
https://issues.apache.org/jira/browse/SOLR-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13833084#comment-13833084
]
Yonik Seeley commented on SOLR-3191:
------------------------------------
bq. I agree with you regarding the abstract class: ReturnFields should be an
interface;
Heh - I see my use of "interface" was ambiguous. I actually meant the higher
level text (http, etc) interface to Solr is important, not the java level.
It's that interface that really counts... being able to pass fl=foo,
*_important, -bar, -*_big
So I was questioning why there were even two classes, rather than just a single
one. If a super-expert user wants to make their own customized version, they
can copy-n-paste the code, but it's so far into the outliers we shouldn't be
designing around it.
> field exclusion from fl
> -----------------------
>
> Key: SOLR-3191
> URL: https://issues.apache.org/jira/browse/SOLR-3191
> Project: Solr
> Issue Type: Improvement
> Reporter: Luca Cavanna
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Attachments: 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.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
