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

Qian Xu updated SQOOP-1395:
---------------------------
    Description: 
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.

  was:
We would consider to use Kite SDK to do the real conversion of the data. The following are the major areas for this:
* Implement ParquetExportMapper
* Hook up ParquetInputFormat and ParquetExportMapper in the export job.

       Priority: Minor  (was: Major)
       Assignee: Qian Xu
        Summary: Use random generated class name for SqoopRecord  (was: Convert Parquet format to Sqoop format via MapReduce)

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