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 "Alexey Serbin (Jira)" <ji...@apache.org> on 2021/01/28 03:37:00 UTC
[jira] [Updated] (IMPALA-10457) Add a note that 'hash x range' and
'range x hash' partition for Kudu tables produce the same result
[ https://issues.apache.org/jira/browse/IMPALA-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Serbin updated IMPALA-10457:
-----------------------------------
Description:
I stumbled upon on a fact that in Impala prior to version 4 the syntax for {{CREATE TABLE}} doesn't allow specifying {{range x hash}} partition, the only acceptable syntax is {{hash x range}}, as reflected in [IMPALA-7686|https://issues.apache.org/jira/browse/IMPALA-7686].
With knowledge on Kudu partitioning its self-obvious that 'hash x range' and 'range x hash' should result in the same layout of data across Kudu tablets, but it's would be great to explicitly document that (probably, with the reference to this page https://kudu.apache.org/docs/schema_design.html#hash-range-partitioning-example ?).
Probably, the best place to add the note is: https://impala.apache.org/docs/build/html/topics/impala_kudu.html#ariaid-title17
was:
I stumbled upon on a fact that in Impala prior to version 4 the syntax for {{CREATE TABLE}} doesn't allow specifying {{range x hash}} partition, the only acceptable syntax is {{hash x range}}, as reflected in [IMPALA-7686|https://issues.apache.org/jira/browse/IMPALA-7686].
With knowledge on Kudu partitioning its self-obvious that 'hash x range' and 'range x hash' should result in the same result, but it's would be great to explicitly document that (probably, with the reference to this page https://kudu.apache.org/docs/schema_design.html#hash-range-partitioning-example ?).
Probably, the best place to add the note is: https://impala.apache.org/docs/build/html/topics/impala_kudu.html#ariaid-title17
> Add a note that 'hash x range' and 'range x hash' partition for Kudu tables produce the same result
> ---------------------------------------------------------------------------------------------------
>
> Key: IMPALA-10457
> URL: https://issues.apache.org/jira/browse/IMPALA-10457
> Project: IMPALA
> Issue Type: Documentation
> Components: Docs
> Reporter: Alexey Serbin
> Priority: Minor
>
> I stumbled upon on a fact that in Impala prior to version 4 the syntax for {{CREATE TABLE}} doesn't allow specifying {{range x hash}} partition, the only acceptable syntax is {{hash x range}}, as reflected in [IMPALA-7686|https://issues.apache.org/jira/browse/IMPALA-7686].
> With knowledge on Kudu partitioning its self-obvious that 'hash x range' and 'range x hash' should result in the same layout of data across Kudu tablets, but it's would be great to explicitly document that (probably, with the reference to this page https://kudu.apache.org/docs/schema_design.html#hash-range-partitioning-example ?).
> Probably, the best place to add the note is: https://impala.apache.org/docs/build/html/topics/impala_kudu.html#ariaid-title17
--
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