Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The current implementation of HCatalog related export works out of the box with RDBMS systems (e.g. Oracle) if the column names match case sensitive, although in several cases the column names are received as an UPPER_CASE list from the RDBMS, and thus the export fails, within the ClassWriter.
Although the users have the possibility to define the name of the columns explicit with the --columns option, in case of 100+ columns it's not practical.
It would be great to have an option which could do the matching in lower and UPPER case as well. The start point for this implementation should start from SqoopHCatUtilities#configureHCat method with respect to ensure HCatalog api is able to handle the different cased column names.
Attachments
Issue Links
- relates to
-
SQOOP-3030 Export to Oracle using (--direct + --hcatalog + --columns) with columns having the wrong case sensitivity fails with NPE
- Open
-
SQOOP-3025 Oracle Direct export from HCatalog parquet table gives NPE in kerberized cluster
- Resolved