[
https://issues.apache.org/jira/browse/KYLIN-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
PENG Zhengshuai updated KYLIN-4030:
-----------------------------------
Description:
In ResourceStore, the interface *deleteResourceImpl(String resPath, long
timestamp)* maybe failed to delete the resource because the resource timestamp
may lose the precision.
For example, if we use *$KYLIN_HOME/bin/metastore.sh* to backup from metastore
to Local OS filesystem, and restore from local filesystem to metastore. The
resource timestamp will lose precision in Millis Second.
An example here:
original timestamp: 1559564381
after precision lost: 1559564000
The fix design is to tolerate [0-999] ms difference when comparing the timestamp
was:
In ResourceStore, the interface *deleteResourceImpl(String resPath, long
timestamp)* maybe failed to delete the resource because the resource timestamp
may lose the precision.
For example, if we use *$KYLIN_HOME/bin/metastore.sh* to backup from metastore
to Local OS filesystem, and restore from local filesystem to metastore. The
resource timestamp will lose precision in Millis Second.
An example here:
original timestamp: 1559564381
after precision lost: 1559564000
> ResourceStore deleteResource by comparing timestamp may be failed to delete
> caused by time precision loose
> ----------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-4030
> URL: https://issues.apache.org/jira/browse/KYLIN-4030
> Project: Kylin
> Issue Type: Bug
> Reporter: PENG Zhengshuai
> Assignee: PENG Zhengshuai
> Priority: Minor
>
> In ResourceStore, the interface *deleteResourceImpl(String resPath, long
> timestamp)* maybe failed to delete the resource because the resource
> timestamp may lose the precision.
> For example, if we use *$KYLIN_HOME/bin/metastore.sh* to backup from
> metastore to Local OS filesystem, and restore from local filesystem to
> metastore. The resource timestamp will lose precision in Millis Second.
> An example here:
> original timestamp: 1559564381
> after precision lost: 1559564000
> The fix design is to tolerate [0-999] ms difference when comparing the
> timestamp
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
