[jira] [Updated] (HDDS-4102) Normalize Keypath for lookupKey

2020-09-28 Thread Marton Elek (Jira)


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

Marton Elek updated HDDS-4102:
--
Target Version/s: 1.1.0
  Resolution: Fixed
  Status: Resolved  (was: Patch Available)

> Normalize Keypath for lookupKey
> ---
>
> Key: HDDS-4102
> URL: https://issues.apache.org/jira/browse/HDDS-4102
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Major
>  Labels: pull-request-available
>
> When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the 
> Keyname.
> Now when user tries to read the file from S3 using the keyName which user has 
> used to create the Key, it will return error KEY_NOT_FOUND
> The issue is, lookupKey need to normalize path, when 
> ozone.om.enable.filesystem.paths is enabled. This is common API used by 
> S3/FS. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-4102) Normalize Keypath for lookupKey

2020-08-13 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated HDDS-4102:
-
Labels: pull-request-available  (was: )

> Normalize Keypath for lookupKey
> ---
>
> Key: HDDS-4102
> URL: https://issues.apache.org/jira/browse/HDDS-4102
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Major
>  Labels: pull-request-available
>
> When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the 
> Keyname.
> Now when user tries to read the file from S3 using the keyName which user has 
> used to create the Key, it will return error KEY_NOT_FOUND
> The issue is, lookupKey need to normalize path, when 
> ozone.om.enable.filesystem.paths is enabled. This is common API used by 
> S3/FS. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-4102) Normalize Keypath for lookupKey

2020-08-11 Thread Bharat Viswanadham (Jira)


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

Bharat Viswanadham updated HDDS-4102:
-
Status: Patch Available  (was: Open)

> Normalize Keypath for lookupKey
> ---
>
> Key: HDDS-4102
> URL: https://issues.apache.org/jira/browse/HDDS-4102
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Major
>
> When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the 
> Keyname.
> Now when user tries to read the file from S3 using the keyName which user has 
> used to create the Key, it will return error KEY_NOT_FOUND
> The issue is, lookupKey need to normalize path, when 
> ozone.om.enable.filesystem.paths is enabled. This is common API used by 
> S3/FS. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-4102) Normalize Keypath for lookupKey

2020-08-11 Thread Bharat Viswanadham (Jira)


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

Bharat Viswanadham updated HDDS-4102:
-
Parent: HDDS-4097
Issue Type: Sub-task  (was: Bug)

> Normalize Keypath for lookupKey
> ---
>
> Key: HDDS-4102
> URL: https://issues.apache.org/jira/browse/HDDS-4102
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Major
>
> When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the 
> Keyname.
> Now when user tries to read the file from S3 using the keyName which user has 
> used to create the Key, it will return error KEY_NOT_FOUND
> The issue is, lookupKey need to normalize path, when 
> ozone.om.enable.filesystem.paths is enabled. This is common API used by 
> S3/FS. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org