[
https://issues.apache.org/jira/browse/SQOOP-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13741451#comment-13741451
]
Kostiantyn Kudriavtsev commented on SQOOP-1171:
-----------------------------------------------
Hi Jarek,
thank you for your time
So, I see what you mean, Let me explain my code changes: I faced into problem,
when I was need to pass data from HDFS to fact table through staging table.
However, in the current code staging table must be equals to resulting (fact)
table. In my code changes, I aims provide possibility to use different columns.
As you can see from my changes, I provide accurate list of columns to be
inserted in fact table: INSERT INTO %s (%s) (SELECT %s FROM %s)
So, this give you possibility to have autoincrement or trigger-filed columns in
fact (resulting) table, and don't have them in staging table
> Add possibility to specify columns list to export in required table.
> --------------------------------------------------------------------
>
> Key: SQOOP-1171
> URL: https://issues.apache.org/jira/browse/SQOOP-1171
> Project: Sqoop
> Issue Type: Bug
> Reporter: Kostiantyn Kudriavtsev
> Labels: patch
> Attachments: columns_to_export.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Add possibility to specify columns list to export in required table.
> For example, your target table contains the following fields: id, message,
> country, dtx. 'id' is autoincrement field and 'dtx' set by trigger. So, you
> have only two columns on HDFS (message and country). Now you can set them w/
> option '--columns message, country' during export
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
