Project

General

Profile

Bug #48716

aws-s3 incompatibility related metadata

Added by Ilsoo Byun 4 months ago. Updated 14 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When using metadata containing _, the behavior is different from aws-s3.

s3cmd put ~/1m s3://mytest --add-header 'x-amz-meta-key_1: value_1'
s3cmd get --debug s3://mytest/1m

rgw result:

{'headers': {
             ...
             'x-amz-meta-key6-1': 'value_1',
             ...

aws-s3 result:

{'headers': {
             ...
             'x-amz-meta-key6_1': 'value_1',
             ...

The second case is

s3cmd put ~/1m s3://mytest --add-header 'x_amz_meta_key_1: value_1'
s3cmd get --debug s3://mytest/1m

rgw result:

{'headers': {
             ...
             'x-amz-meta-key6-1': 'value_1',
             ...

aws-s3 result:

{'headers': {
             ...

History

#2 Updated by J. Eric Ivancich 14 days ago

  • Pull request ID set to 38737

#3 Updated by J. Eric Ivancich 14 days ago

  • Status changed from New to Resolved
  • Assignee set to Ilsoo Byun
  • Target version set to v17.0.0

This looks to me like something that should be backported to nautilus (near end-of-life), octopus, and pacific. Any objection?

Also available in: Atom PDF