[
https://issues.apache.org/jira/browse/SQOOP-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498139#comment-14498139
]
Keegan Witt commented on SQOOP-2294:
------------------------------------
Is there another way we can resolve the 1395 concern? It seems wrong to me to
pollute the data with tool-specific content. Names should indicate +what+ the
data is, not +how+ the data was created. In my mind, this would be the MySQL
equivalent of naming a table _MysqlWorkbench_KeegansTable_ just because I
happened to use MySQL Workbench to create a _KeegansTable_ table.
What about prefixing the class name only in the Parquet case rather than
prefixing the Avro schema name?
> Change to Avro schema name breaks some use cases
> ------------------------------------------------
>
> Key: SQOOP-2294
> URL: https://issues.apache.org/jira/browse/SQOOP-2294
> Project: Sqoop
> Issue Type: Bug
> Reporter: Keegan Witt
> Assignee: Qian Xu
>
> SQOOP-1395 introduced a breaking change that causes issues for [some existing
> users|https://issues.apache.org/jira/browse/SQOOP-1395?focusedCommentId=14487672&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14487672].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
