You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "nichunen (JIRA)" <ji...@apache.org> on 2019/07/05 14:00:00 UTC
[jira] [Closed] (KYLIN-4030) ResourceStore deleteResource by
comparing timestamp may be failed to delete caused by time precision loose
[ https://issues.apache.org/jira/browse/KYLIN-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nichunen closed KYLIN-4030.
---------------------------
> 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
> Fix For: v2.6.3
>
>
> 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)