[ https://issues.apache.org/jira/browse/SQOOP-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Voros reassigned SQOOP-3276: ----------------------------------- Assignee: Daniel Voros Hi [~elkarel]! Thanks for reporting this! We've just discussed the need for such an option in SQOOP-3267. We've agreed on adding a new option (--hbase-null-string) for this not to overload the existing two (--null-string and --null-non-string). However, nothing's set in stone, please let me know if you have any concerns with this approach! > Enable import of null columns to HBase > -------------------------------------- > > Key: SQOOP-3276 > URL: https://issues.apache.org/jira/browse/SQOOP-3276 > Project: Sqoop > Issue Type: Improvement > Components: hbase-integration > Reporter: Karel > Assignee: Daniel Voros > Priority: Major > Labels: hbase, null-values, sqoop > > It would be very useful to to have these options for hbase import: > --null-string '' > --null-non-string '0' > The workaround is using coalesce in the query, but that's hard if you import > many tables with many columns. -- This message was sent by Atlassian JIRA (v7.6.3#76005)