sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1395) Use random generated class name for SqoopRecord
Date Tue, 02 Sep 2014 06:49:21 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1395:

I'm concerned about randomizing the class name as that is backward incompatible change that
can break existing users especially when importing into Sequence Files where the class name
is very important. Additionally, user can override the generated class name via {{\-\-class\-name}}
parameter anyway, so I don't think that randomizing is a valid solution as it will either
break the parameter or won't solve the problem. If Kite is trying to instantiate a class based
on some Avro schema flag, I'm wondering if it would be easier to change the flag? For example
to put some prefix there or use different property alltogether?

> 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

View raw message