[ 
https://issues.apache.org/jira/browse/SOLR-2444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13016107#comment-13016107
 ] 

Yonik Seeley commented on SOLR-2444:
------------------------------------

bq. no need for the '_' with transformers – i would hope that the brackets tell 
you that it is a tranformer.

Right, but it seems like the name of the transformer should match the field 
that it adds to the document by default?  That's just a convention of course... 
for example, fl=_docid_ adds the _docid_ field to the documents.  It seems 
natural to refer to the transformer that does that as the _docid_ transformer?

bq. I still don't get this. How do you know that the literal is not referring 
to a field (or invalid field)? How do you know it is an int vs float vs double 
vs string? Seems like too much magic to me.

It's magic people expect, and easy to understand, because most of their 
programming languages work that way. It's unlikely that float vs double would 
matter for returning a constant anyway - and things like JSON don't even 
distinguish.  A string would be quoted, and an int would lack characteristics 
of a float/doube.

We could even add float() int() double() long() functions in the future if we 
really need them.

 

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to