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

Gus Heck commented on SOLR-13312:
---------------------------------

By Transformer, you mean DocumentTransformer (e.g. fl=id,name,score,[shard] to 
add the shard info)? So most vanilla query use cases don't use those, including 
those underpinning streaming expression searches? When you say "write it out" 
do you mean directly generating JSON/XML/javabin? I think javabin would requrie 
creating a SolrDocument If not, the client side changes too... (though perhaps 
shipping the SolrDocument creation load to the solrj client will be of benefit)

I'm not an expert on the codec having never had cause to work with it directly, 
but I it seems that javabin is shipping a serialized SolrDocument 
(org.apache.solr.common.util.JavaBinCodec#readSolrDocument). If the binary wire 
format changes you probably are proposing javabin2? (or lucenebin?) in that 
case it becomes slightly confusing since adding ,[shard] could require the wt 
param to change. 

Perhaps I'm entirely misinterpreting what you said. A patch would probably 
clarify. I'm not for or against this yet, but the description seems short.

> write out responses without creating SolrDocument objects
> ---------------------------------------------------------
>
>                 Key: SOLR-13312
>                 URL: https://issues.apache.org/jira/browse/SOLR-13312
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Noble Paul
>            Priority: Major
>
> Once we get a document from lucene there is no need to create a SolrDocument 
> object to write out the response, if there are no transformers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to