[
https://issues.apache.org/jira/browse/IMPALA-7291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554599#comment-16554599
]
ASF subversion and git services commented on IMPALA-7291:
---------------------------------------------------------
Commit f9e7d938546b5bad607075d4e852e21558d4d67c in impala's branch
refs/heads/master from [~arodoni_cloudera]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=f9e7d93 ]
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 <impala-public-jenk...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@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
>
> 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-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
