You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "pengdou1990 (Jira)" <ji...@apache.org> on 2021/07/13 04:42:00 UTC
[jira] [Updated] (IMPALA-10785) when union kudu table and hdfs
table, union passthrough does not take effect
[ https://issues.apache.org/jira/browse/IMPALA-10785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
pengdou1990 updated IMPALA-10785:
---------------------------------
Description:
IMPALA-3586 already supports union passthrough, and brings great performance improvements in union， but there is still some problems when union between hdfs table and kudu table ，several points cause the problem:
# in kudu scanner node output TupleDescriptor, string slot is 16B,while in hdfs scanner node output TupleDescriptor, string slot is 12B,cause tuple memory layout mismatch
# in kudu scanner node output TupleDescriptor, string slot is 16B, while in Union output TupleDescriptor, string slot is 12B,cause tuple memory layout mismatch
# in Kudu Scannode, row key slot is not null, while in hdfs node, not null slot can't get from the metadata, cause tuple memory layout mismatch
I hive resolved the 1st and 2nd points, how should I do with the 3rd point?
was:
[IMPALA-3586|https://issues.apache.org/jira/browse/IMPALA-3586] already supports union passthrough, and brings great performance improvements in union， but there is still some problems when union between hdfs table and kudu table ，several points cause the problem:
# in kudu scanner node output TupleDescriptor, string slot is 16B,while in hdfs scanner node output TupleDescriptor, string slot is 12B,cause tuple memory layout mismatch
# in kudu scanner node output TupleDescriptor, string slot is 16B, while in Union output TupleDescriptor, string slot is 12B,cause tuple memory layout mismatch
# in Kudu Scannode, row key slot is not null, while in hdfs node, not null slot can't get from the metadata, cause tuple memory layout mismatch
I hive resolved the 1st and 2nd points, how should I do with the 3rd point?
> when union kudu table and hdfs table, union passthrough does not take effect
> ----------------------------------------------------------------------------
>
> Key: IMPALA-10785
> URL: https://issues.apache.org/jira/browse/IMPALA-10785
> Project: IMPALA
> Issue Type: Improvement
> Reporter: pengdou1990
> Priority: Major
>
> IMPALA-3586 already supports union passthrough, and brings great performance improvements in union， but there is still some problems when union between hdfs table and kudu table ，several points cause the problem:
> # in kudu scanner node output TupleDescriptor, string slot is 16B,while in hdfs scanner node output TupleDescriptor, string slot is 12B,cause tuple memory layout mismatch
> # in kudu scanner node output TupleDescriptor, string slot is 16B, while in Union output TupleDescriptor, string slot is 12B,cause tuple memory layout mismatch
> # in Kudu Scannode, row key slot is not null, while in hdfs node, not null slot can't get from the metadata, cause tuple memory layout mismatch
> I hive resolved the 1st and 2nd points, how should I do with the 3rd point?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org