[
https://issues.apache.org/jira/browse/KUDU-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16995819#comment-16995819
]
ASF subversion and git services commented on KUDU-1938:
-------------------------------------------------------
Commit 4327b6e17e6d673fa6800a2a7ff2843508a4da68 in kudu's branch
refs/heads/master from Attila Bukor
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=4327b6e ]
KUDU-1938 Fix length check in SchemaBuilder
Length check in schema builder didn't account for the possibility that
length is unset.
Change-Id: If3d14c3c791b9de016cd346e73e629fdc03448d2
Reviewed-on: http://gerrit.cloudera.org:8080/14893
Tested-by: Kudu Jenkins
Reviewed-by: Alexey Serbin <aser...@cloudera.com>
> Support for VARCHAR type
> ------------------------
>
> Key: KUDU-1938
> URL: https://issues.apache.org/jira/browse/KUDU-1938
> Project: Kudu
> Issue Type: New Feature
> Components: client, tablet
> Reporter: Farzana Kader
> Assignee: Attila Bukor
> Priority: Major
> Labels: limitations, roadmap-candidate
>
> VARCHAR is currently not supported by Kudu. This is functionality that
> currently exists in Impala. Some client applications convert STRING to 32K
> bytes which causes performance issues so they need the VARCHAR support in
> order to integrate well with Kudu.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
