You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Cassandra Targett (JIRA)" <ji...@apache.org> on 2018/01/12 19:58:00 UTC
[jira] [Updated] (SOLR-6785) polyfields are encapsulated and
escaped in csv
[ https://issues.apache.org/jira/browse/SOLR-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cassandra Targett updated SOLR-6785:
------------------------------------
Component/s: update
> polyfields are encapsulated and escaped in csv
> ----------------------------------------------
>
> Key: SOLR-6785
> URL: https://issues.apache.org/jira/browse/SOLR-6785
> Project: Solr
> Issue Type: Bug
> Components: update
> Reporter: Michael Lawrence
>
> The wiki for UpdateCSV (which also presumably applies to the CSV response writer) states: "If an escape is specified, the encapsulator is not used unless also explicitly specified since most formats use either encapsulation or escaping, not both." That makes a lot of sense. However, the fix for SOLR-3959 makes it so that polyfields are always escaped, even when enscapsulation is enabled. Are we sure that SOLR-3959 was even a bug in the first place? Why should commas in the output of polyfields be treated any differently than commas elsewhere? One possible enhancement to the interface would be to use "\" as the separator by default when encapsulation is disabled, but I propose starting by reverting the "fix" for SOLR-3959.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org