You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/10/13 02:25:05 UTC

[jira] [Commented] (SQOOP-2612) Allow rules-based column mapping

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

Jarek Jarcec Cecho commented on SQOOP-2612:
-------------------------------------------

Thank you for your contribution [~proftodd]! Would you mind uploading your patch to the [review board|https://reviews.apache.org/dashboard/] since it's so huge?

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