[jira] [Updated] (HADOOP-17643) WASB : Make metadata checks case insensitive
[ https://issues.apache.org/jira/browse/HADOOP-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shilun Fan updated HADOOP-17643: Component/s: fs/azure Hadoop Flags: Reviewed Target Version/s: 3.3.2, 3.2.3, 3.4.0 > WASB : Make metadata checks case insensitive > > > Key: HADOOP-17643 > URL: https://issues.apache.org/jira/browse/HADOOP-17643 > Project: Hadoop Common > Issue Type: Improvement > Components: fs/azure >Affects Versions: 2.7.0 >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.2.3, 3.3.2 > > Time Spent: 3h 50m > Remaining Estimate: 0h > > WASB driver uses meta data on blobs to denote permission, whether its a place > holder 0 sized blob for dir etc. > For storage migration users uses Azcopy, it copies the blobs but will cause > the metadata keys to get changed to camel case. As per discussion with MSFT > Azcopy team, this is a known issue and technical limitation. This is what > Azcopy team explained > "For context, blob metadata is implemented with HTTP headers. They are case > insensitive but case preserving. > There is a known issue with the Go language. The HTTP client that it provides > does this case modification to the response headers before we can read the > raw values, so the destination metadata keys have a different casing than the > source. We’ve reached out to the Go Team in the past but weren’t successful > in convincing them to change the behaviour. We don’t have a short term > solution right now" > So propose to change the metadata key checks to do case insensitive checks. > May be make case insensitive check configurable with defaults to false for > compatibility. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17643) WASB : Make metadata checks case insensitive
[ https://issues.apache.org/jira/browse/HADOOP-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated HADOOP-17643: -- Fix Version/s: 3.2.3 (was: 3.2.4) > WASB : Make metadata checks case insensitive > > > Key: HADOOP-17643 > URL: https://issues.apache.org/jira/browse/HADOOP-17643 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 2.7.0 >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.2.3, 3.3.2 > > Time Spent: 3h 50m > Remaining Estimate: 0h > > WASB driver uses meta data on blobs to denote permission, whether its a place > holder 0 sized blob for dir etc. > For storage migration users uses Azcopy, it copies the blobs but will cause > the metadata keys to get changed to camel case. As per discussion with MSFT > Azcopy team, this is a known issue and technical limitation. This is what > Azcopy team explained > "For context, blob metadata is implemented with HTTP headers. They are case > insensitive but case preserving. > There is a known issue with the Go language. The HTTP client that it provides > does this case modification to the response headers before we can read the > raw values, so the destination metadata keys have a different casing than the > source. We’ve reached out to the Go Team in the past but weren’t successful > in convincing them to change the behaviour. We don’t have a short term > solution right now" > So propose to change the metadata key checks to do case insensitive checks. > May be make case insensitive check configurable with defaults to false for > compatibility. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17643) WASB : Make metadata checks case insensitive
[ https://issues.apache.org/jira/browse/HADOOP-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masatake Iwasaki updated HADOOP-17643: -- Fix Version/s: 3.2.4 (was: 3.2.3) > WASB : Make metadata checks case insensitive > > > Key: HADOOP-17643 > URL: https://issues.apache.org/jira/browse/HADOOP-17643 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 2.7.0 >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.3.2, 3.2.4 > > Time Spent: 3h 50m > Remaining Estimate: 0h > > WASB driver uses meta data on blobs to denote permission, whether its a place > holder 0 sized blob for dir etc. > For storage migration users uses Azcopy, it copies the blobs but will cause > the metadata keys to get changed to camel case. As per discussion with MSFT > Azcopy team, this is a known issue and technical limitation. This is what > Azcopy team explained > "For context, blob metadata is implemented with HTTP headers. They are case > insensitive but case preserving. > There is a known issue with the Go language. The HTTP client that it provides > does this case modification to the response headers before we can read the > raw values, so the destination metadata keys have a different casing than the > source. We’ve reached out to the Go Team in the past but weren’t successful > in convincing them to change the behaviour. We don’t have a short term > solution right now" > So propose to change the metadata key checks to do case insensitive checks. > May be make case insensitive check configurable with defaults to false for > compatibility. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17643) WASB : Make metadata checks case insensitive
[ https://issues.apache.org/jira/browse/HADOOP-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surendra Singh Lilhore updated HADOOP-17643: Fix Version/s: 3.2.3 > WASB : Make metadata checks case insensitive > > > Key: HADOOP-17643 > URL: https://issues.apache.org/jira/browse/HADOOP-17643 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 2.7.0 >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0, 3.2.3 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > WASB driver uses meta data on blobs to denote permission, whether its a place > holder 0 sized blob for dir etc. > For storage migration users uses Azcopy, it copies the blobs but will cause > the metadata keys to get changed to camel case. As per discussion with MSFT > Azcopy team, this is a known issue and technical limitation. This is what > Azcopy team explained > "For context, blob metadata is implemented with HTTP headers. They are case > insensitive but case preserving. > There is a known issue with the Go language. The HTTP client that it provides > does this case modification to the response headers before we can read the > raw values, so the destination metadata keys have a different casing than the > source. We’ve reached out to the Go Team in the past but weren’t successful > in convincing them to change the behaviour. We don’t have a short term > solution right now" > So propose to change the metadata key checks to do case insensitive checks. > May be make case insensitive check configurable with defaults to false for > compatibility. -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17643) WASB : Make metadata checks case insensitive
[ https://issues.apache.org/jira/browse/HADOOP-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Surendra Singh Lilhore updated HADOOP-17643: Fix Version/s: 3.4.0 > WASB : Make metadata checks case insensitive > > > Key: HADOOP-17643 > URL: https://issues.apache.org/jira/browse/HADOOP-17643 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 2.7.0 >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > Labels: pull-request-available > Fix For: 3.4.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > WASB driver uses meta data on blobs to denote permission, whether its a place > holder 0 sized blob for dir etc. > For storage migration users uses Azcopy, it copies the blobs but will cause > the metadata keys to get changed to camel case. As per discussion with MSFT > Azcopy team, this is a known issue and technical limitation. This is what > Azcopy team explained > "For context, blob metadata is implemented with HTTP headers. They are case > insensitive but case preserving. > There is a known issue with the Go language. The HTTP client that it provides > does this case modification to the response headers before we can read the > raw values, so the destination metadata keys have a different casing than the > source. We’ve reached out to the Go Team in the past but weren’t successful > in convincing them to change the behaviour. We don’t have a short term > solution right now" > So propose to change the metadata key checks to do case insensitive checks. > May be make case insensitive check configurable with defaults to false for > compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17643) WASB : Make metadata checks case insensitive
[ https://issues.apache.org/jira/browse/HADOOP-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HADOOP-17643: Labels: pull-request-available (was: ) > WASB : Make metadata checks case insensitive > > > Key: HADOOP-17643 > URL: https://issues.apache.org/jira/browse/HADOOP-17643 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 2.7.0 >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > WASB driver uses meta data on blobs to denote permission, whether its a place > holder 0 sized blob for dir etc. > For storage migration users uses Azcopy, it copies the blobs but will cause > the metadata keys to get changed to camel case. As per discussion with MSFT > Azcopy team, this is a known issue and technical limitation. This is what > Azcopy team explained > "For context, blob metadata is implemented with HTTP headers. They are case > insensitive but case preserving. > There is a known issue with the Go language. The HTTP client that it provides > does this case modification to the response headers before we can read the > raw values, so the destination metadata keys have a different casing than the > source. We’ve reached out to the Go Team in the past but weren’t successful > in convincing them to change the behaviour. We don’t have a short term > solution right now" > So propose to change the metadata key checks to do case insensitive checks. > May be make case insensitive check configurable with defaults to false for > compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-17643) WASB : Make metadata checks case insensitive
[ https://issues.apache.org/jira/browse/HADOOP-17643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HADOOP-17643: Affects Version/s: 2.7.0 > WASB : Make metadata checks case insensitive > > > Key: HADOOP-17643 > URL: https://issues.apache.org/jira/browse/HADOOP-17643 > Project: Hadoop Common > Issue Type: Improvement >Affects Versions: 2.7.0 >Reporter: Anoop Sam John >Assignee: Anoop Sam John >Priority: Major > > WASB driver uses meta data on blobs to denote permission, whether its a place > holder 0 sized blob for dir etc. > For storage migration users uses Azcopy, it copies the blobs but will cause > the metadata keys to get changed to camel case. As per discussion with MSFT > Azcopy team, this is a known issue and technical limitation. This is what > Azcopy team explained > "For context, blob metadata is implemented with HTTP headers. They are case > insensitive but case preserving. > There is a known issue with the Go language. The HTTP client that it provides > does this case modification to the response headers before we can read the > raw values, so the destination metadata keys have a different casing than the > source. We’ve reached out to the Go Team in the past but weren’t successful > in convincing them to change the behaviour. We don’t have a short term > solution right now" > So propose to change the metadata key checks to do case insensitive checks. > May be make case insensitive check configurable with defaults to false for > compatibility. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
