[
https://issues.apache.org/jira/browse/SOLR-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509768#comment-15509768
]
Gus Heck edited comment on SOLR-9467 at 9/21/16 12:31 PM:
----------------------------------------------------------
Patch vs 6_x updated to ensure that fields being hidden are hidden regardless
of renaming and that the specified field name to hide cannot reappear due to
renaming. It's worth noting (and documenting in the cwiki!) that from a
security perspective this only provides security via obscurity, since *values
of the hidden field may still be exposed by function queries involving that
field*.
was (Author: gus_heck):
Patch vs 6_x updated to ensure that fields being hidden are hidden regardless
of renaming and that the specified to hide cannot reappear due to renaming.
It's worth noting (and documenting in the cwiki!) that from a security
perspective this only provides security via obscurity, since *values of the
hidden field may still be exposed by function queries involving that field*.
> Document Transformer to Remove Fields
> -------------------------------------
>
> Key: SOLR-9467
> URL: https://issues.apache.org/jira/browse/SOLR-9467
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SearchComponents - other
> Affects Versions: 6.2
> Reporter: Gus Heck
> Attachments: SOLR-9467.patch, SOLR-9467.patch
>
>
> Given that SOLR-3191 has become bogged down and inactive, evidently stuck in
> low level details, and since I have wished several times for some way to just
> get that one big field out of my results to improve transfer times without
> making a big brittle list of all my other fields. I'd like to propose a
> DocumentTransformer that accomplishes this.
> It would look something like this:
> {code}&fl=*,[fl.rm v="title"]{code}
> Since removing one field with a known name is probably the most common case
> I'd like to start by keeping this simple, and if further features like globs
> or lists of fields are desired, subsequent Jira tickets can be opened to add
> them. Not attached to specifics here, only looking to keep things simple and
> solve the key use case. If you don't like fl.rm as a name for a transformer,
> suggest a better one (for example).
--
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
