You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Attila Szabo (JIRA)" <ji...@apache.org> on 2016/12/23 14:44:58 UTC
[jira] [Created] (SQOOP-3093) Make --as-parquetfile option
available for ExportTool
Attila Szabo created SQOOP-3093:
-----------------------------------
Summary: Make --as-parquetfile option available for ExportTool
Key: SQOOP-3093
URL: https://issues.apache.org/jira/browse/SQOOP-3093
Project: Sqoop
Issue Type: Improvement
Reporter: Attila Szabo
Currently --as-parquetfile option is only parsed in case of ImportTool.
This option is checked in CodeGentTool as well, to ensure Sqoop class generation is not clashing with the Parquet lib AvroIndexedRecordConverter class mechanism. With the help of this option the class name is altered with a "codegen_" prefix.
However in case of ExportTool this small fix is not applied, thus if the user directly tries to export a directory containing Parquet files to the very same table from it was imported, then it will cause a Parquet error, which is only avoidable when the user uses explicitly the --class-name option, and resolves the name clashing. As the exception thrown in Parquet is very much not straightforward (it's a ClassCastException) it would be better to make the option available to ExportTool thus users would know that the usage of this option is very much suggested (also the documentation could be improved in a parallel JIRA).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)