lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gus Heck (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-9467) Document Transformer to Remove Fields
Date Tue, 20 Sep 2016 23:53:20 GMT

    [ https://issues.apache.org/jira/browse/SOLR-9467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15508176#comment-15508176
] 

Gus Heck commented on SOLR-9467:
--------------------------------

Ok reading [~hossman]'s cases again

# Yes that's nonsense, a quick test locally shows that my code already ignores it, I'll just
add a unit test to document this. 
# Good point, my code doesn't handle this case. I think this should be supported. 
# Although I wasn't planning on using it for security type stuff, I can quickly imagine that
this feature might be used that way. I wouldn't want info to become exposed because it got
aliased. Quick testing in the admin ui for my local install shows that the current code already
achieves this and it should be tested and documented.

So if that sounds good  I'll work on providing another patch sometime in the near future.





> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message