You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "PENG Zhengshuai (JIRA)" <ji...@apache.org> on 2019/06/03 12:28:00 UTC

[jira] [Updated] (KYLIN-4030) ResourceStore deleteResource by comparing timestamp may 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 ]

PENG Zhengshuai updated KYLIN-4030:
-----------------------------------
    Summary: ResourceStore deleteResource by comparing timestamp may failed to delete caused by time precision loose  (was: Resource deleteResource by comparing timestamp may failed to delete caused by time precision loose)

> ResourceStore deleteResource by comparing timestamp may 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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)