[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015554#comment-13015554
]
Yonik Seeley commented on SOLR-2444:
------------------------------------
bq. 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.
Well sure, more development wherever it is. I meant more that it's different
issue as far as features go.
Being able to return function values finally completes basic geosearch.
bq. if you have fl=id,foo(c)&fl.pseudo.foo(c)=field_name we never actually
parse foo(c) as a function
That seems like more complexity than it's worth, and would really only work
with parameter-less functions (if implemented as a hashmap lookup) since
different arguments to the function would cause the match to fail.
"transformer syntax" also seems like an somewhat orthoginal issue. Has anyone
commented on the proposed syntax (what is the full proposed syntax anyway? I
need to see some examples with more than one parameter). Is it important to
allow these transformer parameters inline in "fl"? etc.
> 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
