[
https://issues.apache.org/jira/browse/KUDU-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15652797#comment-15652797
]
Jean-Daniel Cryans commented on KUDU-1744:
------------------------------------------
Fixed two months ago but missed 1.0.1 unfortunately:
https://github.com/apache/kudu/commit/21a01cff6e0eddc82a519b80a0da3ec7a7ab57ea
> Java client does not return the set value for the desired block size column
> option
> ----------------------------------------------------------------------------------
>
> Key: KUDU-1744
> URL: https://issues.apache.org/jira/browse/KUDU-1744
> Project: Kudu
> Issue Type: Bug
> Components: api
> Affects Versions: 1.1.0
> Reporter: Dimitris Tsirogiannis
>
> Impala uses the Java client during the execution of CREATE TABLE statements
> to create and set the schema of Kudu tables; the Java client is also used
> during metadata loading. As part of IMPALA-3726, more column options are
> added in the CREATE TABLE statement, including BLOCK_SIZE (desired block size
> for columns). Setting the block size doesn't seem to have any effect and when
> the schema of Kudu tables is loaded from Kudu, the desired block size is
> always 0 (as returned by ColumnSchema.getDesiredBlockSize()).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
