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

Erick Erickson commented on SOLR-9467:
--------------------------------------

re: lazy field loading. Does it really matter enough to care about? With no 
option to _not_ compress the stored data, and given that the stored data is 
compressed on a document basis, even loading one field is enough to cause most 
of the work to be done.

Although contrariwise, with all the "use doc values as stored" stuff I can 
argue with myself that suppressing loading the fields first a-la 3191 would 
result in measurable savings since you could arrange things so that 
fl=*&exclude=all_non_dv_fields would avoid any decompression.

BTW, the stall on 3191 is mostly that I never seem to have the time I think I 
do.....

> 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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to