[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016114#comment-13016114
]
Ryan McKinley commented on SOLR-2444:
-------------------------------------
bq. Right, but it seems like the name of the transformer should match the field
that it adds to the document by default?
Since changing from the '_' syntax to the bracket syntax, i would now expect
the brackets in the name for the return field.
{code}
?fl=id,[explain]
{code}
would return the document:
{code}
<str name="[explain]">...</str>
{code}
bq. It's magic people expect,
How do you know it is a literal and not just a missing field name? See
SOLR-2441
What about a literal that matches a field name? quotes? Didn't hoss suggest
that we should use quotes to wrap crazy field names?
is:
{code}
?fl=id,avalue:'some crazy field name',score
{code}
referring to a field or a literal? In the fl parameter, i would expect
everything to be a field name unless you explicitly say it is a literal.
> Update fl syntax to support: pseudo fields, AS, transformers, and wildcards
> ---------------------------------------------------------------------------
>
> Key: SOLR-2444
> URL: https://issues.apache.org/jira/browse/SOLR-2444
> Project: Solr
> Issue Type: New Feature
> Reporter: Ryan McKinley
> Attachments: SOLR-2444-fl-parsing.patch, SOLR-2444-fl-parsing.patch
>
>
> The ReturnFields parsing needs to be improved. It should also support
> wildcards
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
