[
https://issues.apache.org/jira/browse/KUDU-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15924724#comment-15924724
]
Matthew Jacobs commented on KUDU-1938:
--------------------------------------
I don't think Impala would need anything different than underlying string
storage, though arguably Kudu should store the metadata about the max length in
the column metadata. That said, Impala probably isn't ready to start expanding
support for Impala VARCHAR to Kudu or other file formats yet because it has a
number of limitations and will be improved in the future, e.g. builtins support
is not very good. IMPALA-4677 should track these sorts of issues moving forward.
[~fkader] - a separate question is why do you want VARCHAR in Kudu? In Impala
it typically comes up in the context of supporting legacy systems, but with
Kudu you presumably loading new data. Is STRING insufficient for your use case?
> Support for VARCHAR type
> ------------------------
>
> Key: KUDU-1938
> URL: https://issues.apache.org/jira/browse/KUDU-1938
> Project: Kudu
> Issue Type: Bug
> Components: client, tablet
> Reporter: Farzana Kader
>
> 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
(v6.3.15#6346)
