[
https://issues.apache.org/jira/browse/DRILL-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vitalii Diravka updated DRILL-6564:
-----------------------------------
Description:
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
was:
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.
Also the approach of updating plugins configs without restarting drillbit could
be considered for implementing.
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
> --------------------------
>
> 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
>
>
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
