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

Erick Erickson edited comment on SOLR-7208 at 3/9/15 2:05 PM:
--------------------------------------------------------------

Offhand, I don't see a good reason to support this, why do you think this is 
important? Why can't the client just deal with a single instance of the field?

I suspect you'll find this is a pretty invasive change. Unless a good case can 
be made for supporting this has a common use-case I doubt it'll get much 
support.

Feel free to argue the point, but I'd get some consensus that this would be 
accepted before putting in the work.




was (Author: erickerickson):
Offhand, I don't see a good reason to support this, why do you think this is 
important? Why can't the client just deal with a single representation of the 
list?

I suspect you'll find this is a pretty invasive change. Unless a good case can 
be made for supporting this has a common use-case I doubt it'll get much 
support.

Feel free to argue the point, but I'd get some consensus that this would be 
accepted before putting in the work.



> Duplicate column in search not supported
> ----------------------------------------
>
>                 Key: SOLR-7208
>                 URL: https://issues.apache.org/jira/browse/SOLR-7208
>             Project: Solr
>          Issue Type: Task
>    Affects Versions: 4.10.2
>         Environment: Open Suse 14
>            Reporter: Nagabhushan
>            Priority: Trivial
>
> Hi tried to get CSV response with duplicate field in select.
> Ex : fl = name,age,no,name
> It will return only name,age,no in CSV. Duplicate column name is missing in 
> response.
> Need help to fix this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to