[ 
https://issues.apache.org/jira/browse/SPARK-25143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dongjoon Hyun updated SPARK-25143:
----------------------------------
    Description: 
Currently, for better UX, Apache Spark provides data source backward 
compatibility by using the pre-defined built-in `backwardCompatibilityMap`.

 * 
[https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala#L564]

Although this mapping table is maintained carefully, but it's not flexible when 
we have multiple implementations like Avro/CSV/ORC.

This issue aims to extend Spark backward-compatibility-mapping capability by 
allowing users provide a custom mapping in a general manner as configuration. 
If a user faces some issue with the provided mapping, he/she can override it by 
configuration.

  was:
Currently, for better UX, Apache Spark provides data source backward 
compatibility by using the pre-defined built-in `backwardCompatibilityMap`.

 * 
[https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala#L564]

Although this mapping table is maintained carefully, but it's not flexible when 
we have multiple implementations like Avro/CSV/ORC. (For the detail, please see 
SPARK-24924 for the discussion.)

This issue aims to extend Spark backward-compatibility-mapping capability by 
allowing users provide a custom mapping in a general manner as configuration. 
If a user faces some issue with the provided mapping, he/she can override it by 
configuration.


> Support data source name mapping configuration
> ----------------------------------------------
>
>                 Key: SPARK-25143
>                 URL: https://issues.apache.org/jira/browse/SPARK-25143
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.4.0
>            Reporter: Dongjoon Hyun
>            Priority: Major
>
> Currently, for better UX, Apache Spark provides data source backward 
> compatibility by using the pre-defined built-in `backwardCompatibilityMap`.
>  * 
> [https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala#L564]
> Although this mapping table is maintained carefully, but it's not flexible 
> when we have multiple implementations like Avro/CSV/ORC.
> This issue aims to extend Spark backward-compatibility-mapping capability by 
> allowing users provide a custom mapping in a general manner as configuration. 
> If a user faces some issue with the provided mapping, he/she can override it 
> by configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to