[ 
https://issues.apache.org/jira/browse/HDDS-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dinesh Chitlangia updated HDDS-558:
-----------------------------------
    Description: 
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.

 
{noformat}
hadoop@fdaf56d9e9d8:~$ ./bin/ozone sh key put /rvol/rbucket/rkey sample.orc
hadoop@fdaf56d9e9d8:~$ ./bin/ozone sh key list /rvol/rbucket
[ {
"version" : 0,
"md5hash" : null,
"createdOn" : "Wed, 26 Sep 2018 20:29:10 GMT",
"modifiedOn" : "Wed, 26 Sep 2018 20:29:12 GMT",
"size" : 2262690,
"keyName" : "rkey"
} ]{noformat}
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.

  was:
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.


> 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
>            Priority: Major
>              Labels: newbie
>
> 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.
>  
> {noformat}
> hadoop@fdaf56d9e9d8:~$ ./bin/ozone sh key put /rvol/rbucket/rkey sample.orc
> hadoop@fdaf56d9e9d8:~$ ./bin/ozone sh key list /rvol/rbucket
> [ {
> "version" : 0,
> "md5hash" : null,
> "createdOn" : "Wed, 26 Sep 2018 20:29:10 GMT",
> "modifiedOn" : "Wed, 26 Sep 2018 20:29:12 GMT",
> "size" : 2262690,
> "keyName" : "rkey"
> } ]{noformat}
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to