Github user dongjinleekr commented on the issue:
https://github.com/apache/tajo/pull/1036
Updated! Thanks for your immediate response.
Followings are additional comments on this issue:
1. During updating the (potentially) broken test, one question arose: **is
there any list of properties that should not be unset?** If there are, it seems
like we have to implement an additional feature to make them unset-proof. (for
example, show error message when the user tries to unset some reserved
properties.) Do you have any opinion on that? Or, is it better to query about
this problem on dev mailing list?
2. I omitted implementation for HiveCatalogStore - as you remember, it is a
deprecated feature. (TAJO-1775)
---
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.
---
