[
https://issues.apache.org/jira/browse/TAJO-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946381#comment-14946381
]
ASF GitHub Bot commented on TAJO-1907:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/800#issuecomment-146096918
Yes, I think it will be ok. Users don't have to backup and restore their
catalog unless they have indexes on some columns where the length of the
composite string of those column names is 256 bytes.
> Reduce the size of the INDEXES table's COLUMN_NAMES field
> ---------------------------------------------------------
>
> Key: TAJO-1907
> URL: https://issues.apache.org/jira/browse/TAJO-1907
> Project: Tajo
> Issue Type: Task
> Components: Catalog
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Priority: Critical
> Fix For: 0.11.0
>
>
> MySQL InnoDB allows the size of a single column for an index key up to 767
> bytes by default. For a TEXT or VARCHAR column, a UTF-8 character set and the
> maximum of 3 bytes for each character are assumed. So, the current length of
> COLUMN_NAMES (256) causes an error while starting up occasionally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
