You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Dinesh Chitlangia (JIRA)" <ji...@apache.org> on 2018/09/26 20:56:00 UTC

[jira] [Created] (HDDS-558) When creating keys, the creationTime and modificationTime should ideally be the same

Dinesh Chitlangia created HDDS-558:
--------------------------------------

             Summary: When creating keys, the creationTime and modificationTime should ideally be the same
                 Key: HDDS-558
                 URL: https://issues.apache.org/jira/browse/HDDS-558
             Project: Hadoop Distributed Data Store
          Issue Type: Bug
          Components: Ozone Client, Ozone Manager
            Reporter: Dinesh Chitlangia


Steps to replicate:
 # Start ozone
 # Create Volume and Bucket or use existing ones
 # Create Key
 # List Keys for that bucket or just get key info

We will see that the creationTime and ModificationTime has a minor difference.

 

Potential fix area : KeyManagerImpl#commitKey
{code:java}
keyInfo = new OmKeyInfo.Builder()
    .setVolumeName(args.getVolumeName())
    .setBucketName(args.getBucketName())
    .setKeyName(args.getKeyName())
    .setOmKeyLocationInfos(Collections.singletonList(
        new OmKeyLocationInfoGroup(0, locations)))
    .setCreationTime(Time.now())
    .setModificationTime(Time.now())
    .setDataSize(size)
    .setReplicationType(type)
    .setReplicationFactor(factor)
    .build();
{code}
For setting, both these values, we are getting current time and thus the minor difference.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org