I'm back to looking at how we can cleanly add more fields to outgoing
documents...

When I poke around the code, now, I see that TextRespnseWriter now has
some fields that look like they should solve SOLR-1566:

writeSolrDocument(String name, SolrDocument doc, Set<String>
returnFields, Map pseudoFields)
writeDocList(String name, DocList ids, Set<String> fields, Map otherFields)
writeSolrDocumentList(String name, SolrDocumentList docs, Set<String>
fields, Map otherFields)

What are Map pseudoFields and Map otherFields?  How are they used?
IIUC, this would just solve SOLR-1566 for things that use
TextResponseWriter, but not BinaryResponseWriters.

Anyone have any insite on this?

thanks
ryan

---------------------------------------------------------------------

The 'location' field type is a compound type. Having a field
translator somewhere would be awesome; as of awhile back you got the
internally generated fields with a 'fl=*'. Is this the right tool or
even layer for that problem?

Also, having function results return as fields would help.

On Sun, Feb 27, 2011 at 2:42 PM, Ryan McKinley <[EMAIL PROTECTED]> wrote:
> I'm back to looking at how we can cleanly add more fields to outgoing
> documents...
>
> When I poke around the code, now, I see that TextRespnseWriter now has
> some fields that look like they should solve SOLR-1566:
>
> writeSolrDocument(String name, SolrDocument doc, Set<String>
> returnFields, Map pseudoFields)
> writeDocList(String name, DocList ids, Set<String> fields, Map otherFields)
> writeSolrDocumentList(String name, SolrDocumentList docs, Set<String>
> fields, Map otherFields)
>
> What are Map pseudoFields and Map otherFields?  How are they used?
> IIUC, this would just solve SOLR-1566 for things that use
> TextResponseWriter, but not BinaryResponseWriters.
>
> Anyone have any insite on this?
>
> thanks
> ryan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

--
Lance Norskog
[EMAIL PROTECTED]

---------------------------------------------------------------------

On Sun, Feb 27, 2011 at 7:23 PM, Lance Norskog <[EMAIL PROTECTED]> wrote:
> The 'location' field type is a compound type. Having a field
> translator somewhere would be awesome; as of awhile back you got the
> internally generated fields with a 'fl=*'.

That's because the sub-fields were marked as stored, which isn't
necessary for the LatLon field type.

-Yonik
http://lucidimagination.com

---------------------------------------------------------------------