Mahesh Reddy has posted comments on this change. ( 
http://gerrit.cloudera.org:8080/17769 )

Change subject: KUDU-2671 key encoding for custom hash bucket schemas
......................................................................


Patch Set 6:

(2 comments)

http://gerrit.cloudera.org:8080/#/c/17769/6/src/kudu/client/client.cc
File src/kudu/client/client.cc:

http://gerrit.cloudera.org:8080/#/c/17769/6/src/kudu/client/client.cc@1016
PS6, Line 1016: if (range->hash_bucket_schemas_.empty()) {
              :         schemas_pb->mutable_hash_schemas()->CopyFrom(
              :             data_->partition_schema_.hash_bucket_schemas())
> Nope, there is no need to require user to manually add a hash dimension for
To be clear, I was referring to when the table-wide hash schema would be phased 
out. Then, the user would have to manually add hash dimensions for each range 
right?


http://gerrit.cloudera.org:8080/#/c/17769/6/src/kudu/common/partition.cc
File src/kudu/common/partition.cc:

http://gerrit.cloudera.org:8080/#/c/17769/6/src/kudu/common/partition.cc@1559
PS6, Line 1559: if (!upper.empty() && upper <= range_key) {
              :       has_custom_range = false;
              :     }
> The return value should be the appropriate hash schema corresponding to the
Right, but what will be returned in the case of a non-covered range once the 
table-wide hash schema is phased out?



--
To view, visit http://gerrit.cloudera.org:8080/17769
To unsubscribe, visit http://gerrit.cloudera.org:8080/settings

Gerrit-Project: kudu
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I81aa1c10998d88a1bd5314fc3132037b1c8bbe4b
Gerrit-Change-Number: 17769
Gerrit-PatchSet: 6
Gerrit-Owner: Alexey Serbin <[email protected]>
Gerrit-Reviewer: Alexey Serbin <[email protected]>
Gerrit-Reviewer: Andrew Wong <[email protected]>
Gerrit-Reviewer: Kudu Jenkins (120)
Gerrit-Reviewer: Mahesh Reddy <[email protected]>
Gerrit-Comment-Date: Wed, 18 Aug 2021 20:54:16 +0000
Gerrit-HasComments: Yes

Reply via email to