[jira] [Updated] (TAJO-618) Catalog column length is too long.

["Jaehwa Jung (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAJO-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jaehwa Jung updated TAJO-618:
-----------------------------

    Affects Version/s:     (was: 1.0-incubating)
                           (was: 0.8-incubating)

> Catalog column length is too long.
> ----------------------------------
>
>                 Key: TAJO-618
>                 URL: https://issues.apache.org/jira/browse/TAJO-618
>             Project: Tajo
>          Issue Type: Bug
>          Components: catalog
>            Reporter: Jaehwa Jung
>            Assignee: Jaehwa Jung
>
> If users use MySQLStore, one of them can finds a bug according to their mysql configuration as follows:
> {code:xml}
>  ERROR store.MySQLStore (AbstractDBStore.java:<init>(124)) - Failed to create the base tables caused by com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytestrying to drop base table
> {code}
> It will be happened by a table called COLUMNS. It uses unique key which consists of TABLE_ID and column_name, and these two columns have 255 characters. Each column characters doesn’t matter, but it would be lack for unique key according to mysql configuration. 
> If mysql characterset is UTF8, total key length for unique key will be calculated in this way - (255 + 255) * 3 = 1,530. At the result, it will exceed max limit value such as 1000 byte. 
> We need to update these columns length. So, I wish to update these columns as follows:
> * TABLE_ID: varchar(128)
> * column_name: varchar(128)
> For reference, I borrowed from hive metastore schema. And if we update COLUMNS table, we should other tables which use TABLE_ID. I also think that DerbyStore needs to update by this issue. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)