You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2014/09/01 10:30:21 UTC

[jira] [Commented] (SQOOP-1395) Use random generated class name for SqoopRecord

    [ https://issues.apache.org/jira/browse/SQOOP-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117183#comment-14117183 ] 

Jarek Jarcec Cecho commented on SQOOP-1395:
-------------------------------------------

I'm wondering how it can happen that Sqoop generates the same class names as Parquet uses when those classes should be in different packages?

> 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
>
> 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)