[ https://issues.apache.org/jira/browse/SOLR-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15480136#comment-15480136 ]
Gus Heck commented on SOLR-9467: -------------------------------- Been on vacation (still am)... will think about the cases [~hossman] mentioned. [~arafalov], The intent here is to solve only the transport cost issue initially, deeper better savings (or more expressive versions, using regexes, globs etc) can be had via future enhancements or SOLR-3191. > 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 > > > 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