[
https://issues.apache.org/jira/browse/TAJO-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15288117#comment-15288117
]
ASF GitHub Bot commented on TAJO-2115:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/996#issuecomment-219911267
I mean, this issue is not addressing the fundamental problem. I believe
that we need to devise a better way to map Tajo columns and HBase columns.
> 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)
