[
https://issues.apache.org/jira/browse/SOLR-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16796466#comment-16796466
]
Noble Paul commented on SOLR-13312:
-----------------------------------
bq. By Transformer, you mean DocumentTransformer (e.g. fl=id,name,score,[shard]
to add the shard info)?
Well, the problem is that we have the DocTransformers working on a concrete
class called {{SolrDocument}} . We should be able to make transformers work on
an interface. So , any DocTransformer which implements the new interface can
possibly work. The most common ones that we ship today can cut over to the
interface.
bq. 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.
No. the output format remains same. There will be zero changes. So, even an
older client should have no problem in communicating with a new Solr
bq. but I it seems that javabin is shipping a serialized SolrDocument...
Javabin is a serialization/deserialization format. it is very well possible to
construct that format without creating an Object.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
