[HDDS-1132] Ozone serialization codec for Ozone S3 secret table

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Component/s: Ozone Manager, S3
• Labels: newbie
• Target Version/s: 0.5.0
• Sprint: HDDS BadLands
• Assignee: Zsolt Venczel
• Reporter: Marton Elek
• Created: 19/Feb/19 09:36
• Updated: 01/May/19 23:42
• Resolved: 01/May/19 23:42

Description

HDDS-748/HDDS-864 introduced an option to use strongly typed metadata tables and separated the serialization/deserialization logic to separated codec implementation

HDDS-937 introduced a new S3 secret table which is not codec based.

I propose to use codecs for this table.

In OzoneMetadataManager the return value of getS3SecretTable() should be changed from Table<byte[],byte[]> to Table<S3SecretKey,S3SecretValue>.

The encoding/decoding logic of S3SecretValue should be registered in ~OzoneMetadataManagerImpl:L204

As the codecs are type based we may need a wrapper class to encode the String kerberos id with md5: class S3SecretKey(String name = kerberodId). Long term we can modify the S3SecretKey to support multiple keys for the same kerberos id.

 

 

Issue Links

• duplicates: HDDS-1482 Use strongly typed codec implementations for the S3Table