You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "wupj (JIRA)" <ji...@apache.org> on 2019/04/26 09:23:00 UTC

[jira] [Created] (SQOOP-3437) when the PartitionColumn is Types.CHAR or Types.VARCHAR or Types.LONGVARCHAR the partition will be wrong

wupj created SQOOP-3437:
---------------------------

             Summary: when the  PartitionColumn is    Types.CHAR or Types.VARCHAR or Types.LONGVARCHAR the   partition will be wrong
                 Key: SQOOP-3437
                 URL: https://issues.apache.org/jira/browse/SQOOP-3437
             Project: Sqoop
          Issue Type: Bug
          Components: connectors, connectors/generic
    Affects Versions: 1.99.7
         Environment: sqoop1.99.7

 
            Reporter: wupj
         Attachments: image-2019-04-26-17-17-58-119.png

Now I found some problem with PartitionColumn . 

when my partition column is type of char or varchar or LONGVARCHAR, It'will be wrong will the partition .

eg:

The PartitionColumn is MONTH with varchar ,the value is  "01" to "12".

Then I can see the  result is 

!image-2019-04-26-17-17-58-119.png!

what happen?

The unknow char is unicode such  as \u0001 and so on. It happen on textToBigDecimal().

 It's wrong with the algorithm or I wrong

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)