[
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012582#comment-13012582
]
Hoss Man commented on SOLR-2444:
--------------------------------
bq. I think it makes sense because it is the place you select what goes in the
output.
part of the complexity here is that in a lot of cases you want the client to
specy the "target" of the transformation, w/o knowing the source.
in your previous example: clients may e in a situation where they know they
want the "xxx" and "score" fields w/o knowing that "xxx" is the result of a
transformation from the concrete "id" field.
In an ideal world, a solr admin named Bob should be able to tell his client
Carl that the "price" field is the one Carl wants to use. Carl could then
query solr with "...&fl=price" or "...&sort=price desc" w/o ever necessarily
knowing that price is really the result of a function query that takes into
account the current exchange rate (or some other factors driven by a
transformer configured in solrconfig.xml for hte handler Carl is querying)
Carl is selecting what data goes in the output, but that doesn't mean carl
should (have to) know where that data comes from
> support wildcards in fl parameter, improve DocTransformer parsing
> -----------------------------------------------------------------
>
> 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
