[
https://issues.apache.org/jira/browse/SQOOP-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118309#comment-14118309
]
Joey Echeverria commented on SQOOP-1395:
----------------------------------------
I think the right fix is to change the way the entity name for the Avro schema
gets generated. It should not mach the name of the class that is generated
unless that class is generated from the Avro schema, but it sounds like we're
talking about a class generated by Sqoop.
> Use random generated class name for SqoopRecord
> -----------------------------------------------
>
> Key: SQOOP-1395
> URL: https://issues.apache.org/jira/browse/SQOOP-1395
> Project: Sqoop
> Issue Type: Sub-task
> Components: tools
> Reporter: Qian Xu
> Assignee: Qian Xu
> Priority: Minor
> Attachments: SQOOP-1395.patch
>
>
> Sqoop will generate an entity class to hold values of every database record
> for mapreduce. The class is inherited from the abstract class SqoopRecord.
> The name of the class is by default the table name.
> When export records as Parquet files, the internal logic will attempt to
> instantiate another entity class or create it on demand. Unfortunately, the
> target class has the same name of the one Sqoop generated.
> The JIRA propose to use random class name to avoid the potential problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
