[
https://issues.apache.org/jira/browse/TAJO-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363795#comment-15363795
]
ASF GitHub Bot commented on TAJO-2165:
--------------------------------------
Github user jihoonson commented on the issue:
https://github.com/apache/tajo/pull/1036
Thank you for the quick update. Here are my answers.
1. Basically, table properties are used for optional settings per table.
So, every table property is optional, and tajo should be able to work with
default property values if they are absent.
However, among table properties, timezone is recently changed as a
mandatory property of a table. So, currently I think it is the only one which
should not be removed.
The best solution seems to store the timezone value in the TableMeta or
TableDesc instead of in the optional KeyValue set. But this would be better to
be done in a separate ticket, and it would be enough to force timezone as
unsettable here.
2. The deprecated one is HCatalogStore, and HiveCatalogStore should be
implemented. But, as you see, many functions of HiveCatalogStore are not
implemented yet. I think it also would be better to do in a separate ticket.
> Add 'ALTER TABLE UNSET PROPERTY' statement to Tajo DDL
> ------------------------------------------------------
>
> Key: TAJO-2165
> URL: https://issues.apache.org/jira/browse/TAJO-2165
> Project: Tajo
> Issue Type: New Feature
> Reporter: Lee Dongjin
> Assignee: Lee Dongjin
>
> For version 0.11.x now, there is only set statement for table property. When
> the user makes a typo with DDL statement, this mistake cannot be removed. We
> also need the way to remove already set properties.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
