Return-Path: X-Original-To: apmail-sqoop-dev-archive@www.apache.org Delivered-To: apmail-sqoop-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B246D11CA6 for ; Mon, 1 Sep 2014 02:15:21 +0000 (UTC) Received: (qmail 50372 invoked by uid 500); 1 Sep 2014 02:15:21 -0000 Delivered-To: apmail-sqoop-dev-archive@sqoop.apache.org Received: (qmail 50338 invoked by uid 500); 1 Sep 2014 02:15:21 -0000 Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sqoop.apache.org Delivered-To: mailing list dev@sqoop.apache.org Received: (qmail 50327 invoked by uid 99); 1 Sep 2014 02:15:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Sep 2014 02:15:21 +0000 Date: Mon, 1 Sep 2014 02:15:21 +0000 (UTC) From: "Qian Xu (JIRA)" To: dev@sqoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SQOOP-1395) Use random generated class name for SqoopRecord MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)