[
https://issues.apache.org/jira/browse/IMPALA-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840389#comment-16840389
]
Mike Casey commented on IMPALA-3451:
------------------------------------
Hi,
Re "surprised more people aren't noticing" as per 02/May/16 23:37.
I guess most don't tend to have comments that long.
FWIW, on upgrading from older versions that didn't have this bug, some places
did hit this issue, multiple times... and still do.
But if they need Impala they work around it by shortening comments to under
256, presumably with some loss of useful information if there was a real need
for the comment to be that long in the first place.
Regards,
Mike
> Long comments should not break queries
> --------------------------------------
>
> Key: IMPALA-3451
> URL: https://issues.apache.org/jira/browse/IMPALA-3451
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.3.0
> Reporter: Marcell Szabo
> Priority: Minor
> Labels: ramp-up, usability
>
> 1) The type of column "COMMENT" in HMS DB table "COLUMNS_V2" is varchar(256),
> which makes Impala thinks the max length of comment is just 256 characters
> 2) A table defined with an avro schema file can have a comment that is longer
> than 256 characters.
> Querying from such table causes:
> ERROR: AnalysisException: Failed to load metadata for table: 'database.table'
> CAUSED BY: TableLoadingException: Failed to load metadata for table:
> database.table
> CAUSED BY: AnalysisException: Comment of column 'columnname' exceeds maximum
> length of 256 characters:
> <comment>. has 267 characters.
> Impala should ignore / truncate the comment and execute the query normally.
--
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
