You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/06/25 15:46:01 UTC
[jira] [Commented] (IMPALA-7291) [DOCS] Document recommendation to
use VARCHAR or STRING instead of CHAR(N)
[ https://issues.apache.org/jira/browse/IMPALA-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16872456#comment-16872456 ]
ASF subversion and git services commented on IMPALA-7291:
---------------------------------------------------------
Commit 3d6a8959f8077a53194dd5a7b9e339b09046fa49 in impala's branch refs/heads/2.x from Alex Rodoni
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=3d6a895 ]
IMPALA-7291: [DOCS] Note about no codegen support for CHAR
Also, cleaned up confusing examples.
Change-Id: Id89dcf44e31f1bc56d888527585b3ec90229981a
Reviewed-on: http://gerrit.cloudera.org:8080/11022
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> [DOCS] Document recommendation to use VARCHAR or STRING instead of CHAR(N)
> --------------------------------------------------------------------------
>
> Key: IMPALA-7291
> URL: https://issues.apache.org/jira/browse/IMPALA-7291
> Project: IMPALA
> Issue Type: Improvement
> Components: Docs
> Affects Versions: Impala 2.12.0
> Reporter: Balazs Jeszenszky
> Assignee: Alex Rodoni
> Priority: Major
> Fix For: Impala 3.1.0
>
>
> CHAR(N) currently does not have codegen support. For that reason, we should recommend customers to use VARCHAR or STRING instead - the gain of codegen outweighs the benefits of fixed width CHARs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org