[
https://issues.apache.org/jira/browse/TAJO-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726797#comment-14726797
]
Hudson commented on TAJO-1808:
------------------------------
ABORTED: Integrated in Tajo-0.11.0-build #3 (See
[https://builds.apache.org/job/Tajo-0.11.0-build/3/])
TAJO-1808: Wrong table type problem in catalog. (jihoonson: rev
b4c2c98903433a6f6b8298372c1dca6863e2c3d3)
*
tajo-catalog/tajo-catalog-server/src/main/resources/schemas/mariadb/mariadb.xml
* tajo-catalog/tajo-catalog-server/src/main/resources/schemas/derby/derby.xml
* tajo-catalog/tajo-catalog-server/src/main/resources/schemas/mysql/mysql.xml
* CHANGES
* tajo-catalog/tajo-catalog-server/src/main/resources/schemas/oracle/oracle.xml
*
tajo-catalog/tajo-catalog-server/src/main/resources/schemas/postgresql/postgresql.xml
> Wrong table type problem in catalog
> -----------------------------------
>
> Key: TAJO-1808
> URL: https://issues.apache.org/jira/browse/TAJO-1808
> Project: Tajo
> Issue Type: Bug
> Components: Catalog
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Fix For: 0.11.0
>
> Attachments: TAJO-1808.patch
>
>
> At TAJO-1802, wrong table type of 'base' is fixed to 'managed'. This makes
> the existing catalog emit exception. One easy solution is to bump up our
> catalog version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
