function results' names include trailing whitespace

[Michael Sokolov <ms...@safaribooksonline.com>]

I noticed that when you include a function as a result field, the 
corresponding key in the result markup includes trailing whitespace, 
which seems like a bug.  I wonder if anyone knows if there is a ticket 
for this already?

Example:

fl="id field(units_used) archive_id"

ends up returning results like this:

|       {
         "id":"nest.epubarchive.1",
         "archive_id":"urn:isbn:97849D42C5A01",
         "field(units_used)  ":123
                           ^
       }|

A workaround is to use something like:

fl="id field(units_used)archive_id"

instead, but it seems inelegant, and not consistent with the treatment 
of other fields

-Mike

Re: function results' names include trailing whitespace

[Michael Sokolov <ms...@safaribooksonline.com>]

OK, I opened SOLR-6672; not sure how I stumbled into using white space; 
I would ordinarily use commas too, I think.

-Mike

On 10/29/14 1:23 PM, Chris Hostetter wrote:
> : fl="id field(units_used) archive_id"
>
> I didn't even realize until today that fl was documented to support space
> seperated fields.  i've only ever used commas...
>
>    fl="id,field(units_used),archive_id"
>
> Please go ahead and file a bug in Jira for this, and note in the summary
> that using commas instead of spaces is the workarround.
>
>
> -Hoss
> http://www.lucidworks.com/

Re: function results' names include trailing whitespace

[Chris Hostetter <ho...@fucit.org>]

: fl="id field(units_used) archive_id"

I didn't even realize until today that fl was documented to support space 
seperated fields.  i've only ever used commas...

  fl="id,field(units_used),archive_id"

Please go ahead and file a bug in Jira for this, and note in the summary 
that using commas instead of spaces is the workarround.


-Hoss
http://www.lucidworks.com/