Sqoop

最新推荐文章于 2023-05-24 20:14:23 发布

满床清梦覆星河

最新推荐文章于 2023-05-24 20:14:23 发布

阅读量201

点赞数

分类专栏： Resume 文章标签：大数据 sqoop

本文链接：https://blog.csdn.net/qq_40640228/article/details/128264152

版权

Resume 专栏收录该内容

19 篇文章 1 订阅

订阅专栏

1 Sqoop参数

/opt/module/sqoop/bin/sqoop import \
--connect \
--username \
--password \
--target-dir \
--delete-target-dir \
--num-mappers \
--fields-terminated-by   \
--query   "$2" ' and $CONDITIONS;'

2 Sqoop导入导出Null导致存储一致性问题

Hive中的Null在底层是以“\N”来存储，而MySQL中的Null在底层就是Null，为了保证数据两端的一致性。在导出数据时采用–input-null-string和–input-null-non-string两个参数。导入数据时采用–null-string和–null-non-string。

3 Sqoop数据导出一致性问题

Sqoop在导出到Mysql时，使用4个Map任务，过程中有2个任务失败，那此时MySQL中存储了另外两个Map任务导入的数据，此时业务正好看到了这个报表数据。而开发工程师发现任务失败后，会调试问题并最终将全部数据正确的导入MySQL，那后面业务再次看报表数据，发现本次看到的数据与之前的不一致，这在生产环境是不允许的。

Since Sqoop breaks down export process into multiple transactions, it is possible that a failed export job may result in partial data being committed to the database. This can further lead to subsequent jobs failing due to insert collisions in some cases, or lead to duplicated data in others. You can overcome this problem by specifying a staging table via the --staging-table option which acts as an auxiliary table that is used to stage exported data. The staged data is finally moved to the destination table in a single transaction.官方链接

–staging-table方式

sqoop export 
	--connect jdbc:mysql://192.168.137.10:3306/user_behavior 
	--username root 
	--password 123456 
	--table app_cource_study_report 
	--columns watch_video_cnt,complete_video_cnt,dt 
	--fields-terminated-by "\t" 
	--export-dir "/user/hive/warehouse/tmp.db/app_cource_study_analysis_${day}" 
	--staging-table app_cource_study_report_tmp 
	--clear-staging-table 
	--input-null-string '\N'