[
https://issues.apache.org/jira/browse/SQOOP-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003068#comment-15003068
]
Jarek Jarcec Cecho commented on SQOOP-2612:
-------------------------------------------
When you look how the parameter {{\-\-map\-column\-java}} is actually used,
then you'll see that it's being applied in {{ClassWriter}}'s
{{[toJavaType|https://github.com/apache/sqoop/blob/trunk/src/java/org/apache/sqoop/orm/ClassWriter.java#L289]}}
method rather then in {{ConnManager}}.
Since adding support for mapping entire type and not just column is very
similar functionality, I would expect it to be implemented in the same place
the same way.
> Allow rules-based column mapping
> --------------------------------
>
> Key: SQOOP-2612
> URL: https://issues.apache.org/jira/browse/SQOOP-2612
> Project: Sqoop
> Issue Type: New Feature
> Components: codegen, connectors, test, tools
> Affects Versions: 1.4.6
> Reporter: John Todd
> Priority: Minor
> Attachments: SQOOP-2612.patch
>
>
> Allow users to map source columns to Java and Avro types based on rules
> rather than a list.
> About half the data types on my current project are NUMERIC, and many of
> those have a SCALE of 0. It would be helpful to be able to process those as
> Integers or Longs. The map-column-java feature is helpful, but it requires
> continuous surveillance of the source tables and maintenance of lists of
> columns and what type they should be mapped to.
> It would be helpful to be able to create a rules-based interpretation of the
> type inference provided by Sqoop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
