[
https://issues.apache.org/jira/browse/SOLR-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897704#action_12897704
]
Chris Male commented on SOLR-1566:
----------------------------------
bq. 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.
Sounds reasonable to me. Except I still fear that by creating the
DocAnnotation idea we are now adding another construct to Documents. Sure, as
you say, Solr doesn't materialize Documents till it needs to write them out,
but still a Document consists only of Fields. Now they consist of Fields and
DocAnnotations. Its not a big issue I suppose, just wondering whether its
needed. Perhaps a simple renaming to MetadataField or AnnotatedField or
something would suffice.
> 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]
