From 0daedaca36e999689ea9f5c315d763121e7b703d Mon Sep 17 00:00:00 2001 From: Daniel Voros Date: Fri, 5 Apr 2019 13:35:51 +0200 Subject: [PATCH] Extending docs Change-Id: I42519b74380567956ec447abd4d55ed2ea223302 --- src/docs/user/import.txt | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/docs/user/import.txt b/src/docs/user/import.txt index ae7c7ed6..d58e90c0 100644 --- a/src/docs/user/import.txt +++ b/src/docs/user/import.txt @@ -348,6 +348,11 @@ For example _AVRO will be converted to __AVRO. In the case of HCatalog imports, column names are converted to lower case when mapped to HCatalog columns. This may change in future. +During Avro imports the table's schema is saved in an +.avsc+ file under the +output directory (configured via +\--bindir+). The +\--class-name+ option can +be used to change the resulting file's name, which defaults to the table name +or in case of +\--query+ imports to +AutoGeneratedSchema+. + Incremental Imports ^^^^^^^^^^^^^^^^^^^ @@ -702,6 +707,9 @@ $ sqoop import --table SomeTable --jar-file mydatatypes.jar \ This command will load the +SomeTableType+ class out of +mydatatypes.jar+. +NOTE: The +\--class-name+ option also affects the +.avsc+ file's name +generated during Avro imports. + Additional Import Configuration Properties ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ There are some additional properties which can be configured by modifying