[
https://issues.apache.org/jira/browse/SQOOP-2294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496559#comment-14496559
]
Keegan Witt commented on SQOOP-2294:
------------------------------------
OK. I'd object if it were in the data file itself, but keeping it in separate
metadata doesn't make it too cumbersome if the user had a need to change the
schema name later. I am curious though, how high are the chances of a class
name collision? If not that high, why was the schema name route chosen over
{{\--class-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)
