[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015515#comment-13015515
]
Yonik Seeley commented on SOLR-2444:
------------------------------------
>From the high level user perspective, a field and a function of fields both
>yield values.
I like that simplicity - it's the same type of simplicity we have in
programming languages.
I can call foo(a,b), but instead of a variable(think fieldname) I can simply
substitute another function:
foo(a,bar(c,d))
I think this best matches people's expectations - directly specify what they
want returned in "fl", as they do today. It's also less syntax to remember.
It's also consistent with how we enable sort-by-function... anywhere a
fieldname can be, a function can be substituted. It's also cleaner by default
since a name is not required and the label that will be used is the function
itself.
bq. i vote for the colon
+1, I think that's the best option.
I think this is an independent issue from setting up transparent user
selectable aliases/pseudofields such that when a user puts "foo" in the field,
they get the value but have no idea it came from a source other than stored
fields.
> 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
