You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Vitalii Diravka (JIRA)" <ji...@apache.org> on 2018/07/01 20:58:00 UTC
[jira] [Updated] (DRILL-6564) Storage plugins versioning and
separate storage plugins handler service
[ https://issues.apache.org/jira/browse/DRILL-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vitalii Diravka updated DRILL-6564:
-----------------------------------
Description:
Storage plugin handler can be improved with:
* Incremental update of storage plugins configs. For example in case of Hive, oldPluginConfig may have a key ("hive.metastore.sasl.enabled") with value true in configProps whereas newPluginConfig doesn't have this key at all. In that case if Incremental Update is enabled the old value for the property should remain.
* Versioning can be implemented by introducing timestamp:long in the DataChangeVersion.
Zookeper ZNode stats has timestamp values. So timestamp when storage-plugins.conf file was created can be used in the process of updating plugin. When timestamp of file and plugin config from PersistentStore is the same - nothing need to do
* The approach of updating plugins configs without restarting drillbit could be implemented.
* It can be extracted to the separate service, like Installer Agent, which can generate _storage-plugins.conf_ files depends on the environment and system env properties.
was:
Storage plugin handler can be improved with:
* Versioning can be implemented by introducing timestamp:long in the DataChangeVersion.
Zookeper ZNode stats has timestamp values. So timestamp when storage-plugins.conf file was created can be used in the process of updating plugin. When timestamp of file and plugin config from PersistentStore is the same - nothing need to do
* The approach of updating plugins configs without restarting drillbit could be implemented.
* It can be extracted to the separate service, like Installer Agent, which can generate _storage-plugins.conf_ files depends on the environment and system env properties.
> Storage plugins versioning and separate storage plugins handler service
> -----------------------------------------------------------------------
>
> Key: DRILL-6564
> URL: https://issues.apache.org/jira/browse/DRILL-6564
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.13.0
> Reporter: Vitalii Diravka
> Priority: Minor
> Fix For: Future
>
>
> Storage plugin handler can be improved with:
> * Incremental update of storage plugins configs. For example in case of Hive, oldPluginConfig may have a key ("hive.metastore.sasl.enabled") with value true in configProps whereas newPluginConfig doesn't have this key at all. In that case if Incremental Update is enabled the old value for the property should remain.
> * Versioning can be implemented by introducing timestamp:long in the DataChangeVersion.
> Zookeper ZNode stats has timestamp values. So timestamp when storage-plugins.conf file was created can be used in the process of updating plugin. When timestamp of file and plugin config from PersistentStore is the same - nothing need to do
> * The approach of updating plugins configs without restarting drillbit could be implemented.
> * It can be extracted to the separate service, like Installer Agent, which can generate _storage-plugins.conf_ files depends on the environment and system env properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)