[
https://issues.apache.org/jira/browse/IMPALA-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093999#comment-17093999
]
ASF subversion and git services commented on IMPALA-9640:
---------------------------------------------------------
Commit b9e84738b68710e00afb7efb3cf0c25c0582f7f8 in impala's branch
refs/heads/master from Kris Hahn
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=b9e8473 ]
IMPALA-9640: [DOCS] Document Impala support for Kudu VARCHAR type
Removed VARCHAR from unsupported types in "Kudu considerations".
Change-Id: I61ad6982c35a009b15a2a082692f118a0fbcee65
Reviewed-on: http://gerrit.cloudera.org:8080/15703
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Tamas Mate <[email protected]>
Reviewed-by: Joe McDonnell <[email protected]>
> [DOC]: Document Impala support for Kudu VARCHAR type
> ----------------------------------------------------
>
> Key: IMPALA-9640
> URL: https://issues.apache.org/jira/browse/IMPALA-9640
> Project: IMPALA
> Issue Type: Documentation
> Components: Docs
> Affects Versions: Not Applicable
> Reporter: Kris Hahn
> Assignee: Kris Hahn
> Priority: Major
> Labels: docs
> Fix For: Not Applicable
>
>
> See Impala-5092. The length of a Kudu varchar is applied as a character
> length as opposed to a byte length which Impala currently uses. Kudu tuples
> containing VARCHAR columns use characters instead of bytes to limit the
> length. In the case of ASCII values there is no difference. However, if
> multi-byte characters are written to Kudu the length could be longer than
> allowed.
> Impala checks the actual length and truncates the length of the value if
> necessary.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
