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.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
