[
https://issues.apache.org/jira/browse/TAJO-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944589#comment-14944589
]
ASF GitHub Bot commented on TAJO-1907:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/800#issuecomment-145759418
With out this patch, users will face an error message like ```Specified key
was too long; max key length is 767.``` when starting up the tajo master. This
patch must be included in the 0.11.0 release, I think.
> 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)
