[
https://issues.apache.org/jira/browse/TAJO-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231633#comment-15231633
]
ASF GitHub Bot commented on TAJO-2115:
--------------------------------------
GitHub user blrunner opened a pull request:
https://github.com/apache/tajo/pull/996
TAJO-2115: Change the size of the VALUE_ column in OPTIONS table
This patch just updates the ``VALUE_`` column size of ``OPTIONS`` table.
Existing codes of catalog module have remained static. Here are corrections as
following:
DBMS | Existing Type | Updated Type
-------------------|----------------------|--------------------------
Derby | VARCHAR(4000) | LONG VARCHAR
MySQL | VARCHAR(4000) | TEXT
MariaDB | VARCHAR(4000) | TEXT
PostgreSQL | VARCHAR(4000) | TEXT
Oracle | VARCHAR2(4000) | LONG
I referenced following sites.
* https://db.apache.org/derby/docs/10.1/ref/rrefsqlj15147.html
* https://docs.oracle.com/cd/B19306_01/java.102/b14188/datamap.htm
* https://en.wikibooks.org/wiki/Converting_MySQL_to_PostgreSQL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/blrunner/tajo TAJO-2115
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/996.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #996
----
commit 865da9634d56b768ffff7a4a2d1d7986a6db112c
Author: JaeHwa Jung <[email protected]>
Date: 2016-04-08T03:38:18Z
TAJO-2115: Change the size of the VALUE_ column in OPTIONS table
commit 184750b1647f2e24e9fd7a20e94565c8b14151c9
Author: JaeHwa Jung <[email protected]>
Date: 2016-04-08T03:39:05Z
Update the base version of Catalog
----
> Change the size of the VALUE_ column in OPTIONS table
> -----------------------------------------------------
>
> Key: TAJO-2115
> URL: https://issues.apache.org/jira/browse/TAJO-2115
> Project: Tajo
> Issue Type: Improvement
> Components: Catalog
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Fix For: 0.12.0
>
>
> There is no limit on number of column families in HBase, in theory. Actually,
> many users of HBase create from several dozen of column families to a single
> HBase table. But when create external table to Tajo with HBase and 120 column
> families, the DDL failed as following:
> {code:xml}
> 2016-04-04 15:21:05,809 ERROR org.apache.tajo.catalog.CatalogServer:
> Stack Trace:
> org.apache.tajo.exception.TajoInternalError: internal error: Data truncation:
> Data too long for column 'VALUE_' at row 1
> at
> org.apache.tajo.catalog.store.AbstractDBStore.createTable(AbstractDBStore.java:962)
> at
> org.apache.tajo.catalog.CatalogServer$CatalogProtocolHandler.createTable(CatalogServer.java:693)
> at
> org.apache.tajo.catalog.AbstractCatalogClient.createTable(AbstractCatalogClient.java:542)
> at
> org.apache.tajo.master.exec.CreateTableExecutor.create(CreateTableExecutor.java:113)
> at
> org.apache.tajo.master.exec.CreateTableExecutor.create(CreateTableExecutor.java:69)
> at
> org.apache.tajo.master.exec.DDLExecutor.execute(DDLExecutor.java:106)
> {code}
> Above error made by the column size of OPTIONS table on catalog. We need to
> update its size.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
