[
https://issues.apache.org/jira/browse/SOLR-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897701#action_12897701
]
Grant Ingersoll commented on SOLR-1566:
---------------------------------------
bq. Thats basically where I was headed with SOLR-1298
Hmm, missed that, let me check it out again.
bq. means we can more easily use the values in other areas
True, but Solr doesn't really materialize the Document until the end anyway, so
all you are doing is creating the store anyway.
I've got a basic implementation already that simply adds a small storage piece
onto SolrQueryResponse. It is a <code>Map<Integer, List<DocAnnotations>><code>
where a DocAnnotation is a String name and a Object value. At RespWriting
time, it simply adds the objects as fields onto the appropriate documents. The
key to the Map is the Lucene doc id. Not sure if that is ideal, but I figure
anyone adding to a document would have that handle, but that remains to be seen.
> Allow components to add fields to outgoing documents
> ----------------------------------------------------
>
> Key: SOLR-1566
> URL: https://issues.apache.org/jira/browse/SOLR-1566
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Noble Paul
> Assignee: Grant Ingersoll
> Fix For: Next
>
> Attachments: SOLR-1566.patch, SOLR-1566.patch, SOLR-1566.patch,
> SOLR-1566.patch
>
>
> Currently it is not possible for components to add fields to outgoing
> documents which are not in the the stored fields of the document. This makes
> it cumbersome to add computed fields/metadata .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
