[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015551#comment-13015551
]
Ryan McKinley commented on SOLR-2444:
-------------------------------------
bq, For user directly asking for functions, we'll support (as we already do
today)
bq. fl=a,b,foo(c),d]
bq. And if the user wants to change the name, they can use "mykey:foo(c)"
With the addition of the inline transformer syntax
fl=a,b,[explain]
fl=a,b,price:[value:10]
I don't think we can treat the pseudo fields as a totally different issue since
the field list parsing depends on the pseudo fields. That is, if you have
fl=id,foo(c)&fl.pseudo.foo(c)=field_name we never actually parse foo(c) as a
function -- it needs to get mapped to the field 'field_name'
I think the fl parser needs a few passes:
1. split fl into tokens (or whatever we call them)
2. each token may get replaced with the value from fl.pseudo.token
3. check if the token is a function, transformer, or wildcard
but yes, it is a conceptually different issue.
> 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
