tajo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAJO-1907) Reduce the size of the INDEXES table's COLUMN_NAMES field
Date Mon, 05 Oct 2015 06:59:27 GMT

    [ https://issues.apache.org/jira/browse/TAJO-1907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942988#comment-14942988

ASF GitHub Bot commented on TAJO-1907:

GitHub user jihoonson opened a pull request:


    TAJO-1907: Reduce the size of the INDEXES table's COLUMN_NAMES field


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jihoonson/tajo-2 TAJO-1907

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #800
commit d082433c96fea83b6be3b7bd4d73ca7d353766af
Author: Jihoon Son <jihoonson@apache.org>
Date:   2015-10-05T06:58:59Z



> 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

This message was sent by Atlassian JIRA

View raw message