[
https://issues.apache.org/jira/browse/SOLR-5008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713239#comment-13713239
]
Erik Hatcher commented on SOLR-5008:
------------------------------------
With SOLR-5037 about to be committed, there won't be a need to have fields
defined for columns in a CSV.
I can understand the desire to be able to configure "composite" fields all from
request parameters in order to not have to configure an update processor to
ingest arbitrary CSV in this "lat" and "lon" => "lat,lon" kind of scenario. I
can see this being an optional bell/whistle for the CSV loader only. If you're
ingesting SolrXML or SolrJSON you're obviously generating that from somewhere
else so you could do the combining in that generation process, but that's not
always the case with the ideal CSV ingestion pipeline. I also understand (and
tend to agree with it being a nice other option to have) the update processor
idea here, but that can be a separate ticket and shouldn't block a useful and
optional feature from making it to the CSV loader only.
> Add Support for composite CSV fields
> ------------------------------------
>
> Key: SOLR-5008
> URL: https://issues.apache.org/jira/browse/SOLR-5008
> Project: Solr
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Priority: Minor
> Fix For: 5.0, 4.4
>
>
> It is often useful to be able to create a single field from more than one CSV
> column. For instance, I may want to take a latitude and longitude column in
> my CSV and map that to a single field name
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
