[ 
https://issues.apache.org/jira/browse/HDDS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16651926#comment-16651926
 ] 

Hadoop QA commented on HDDS-657:
--------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  6s{color} 
| {color:red} HDDS-657 does not apply to ozone-0.3. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDDS-657 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12944162/HDDS-657-ozone-0.3.003.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-HDDS-Build/1420/console |
| Powered by | Apache Yetus 0.8.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> Remove {volume} path segments from all the remaining rest endpoints
> -------------------------------------------------------------------
>
>                 Key: HDDS-657
>                 URL: https://issues.apache.org/jira/browse/HDDS-657
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>         Attachments: HDDS-657-ozone-0.3.001.patch, 
> HDDS-657-ozone-0.3.002.patch, HDDS-657-ozone-0.3.003.patch
>
>
> In the recent jiras (HDDS-577 and HDDS-522 and HDDS-606 ) we moved to a model 
> where the ozone volume name is calculated based on a naming convention (s3 + 
> username). With this approach we don't need to add the volume to the path. We 
> can remove it from everywhere.
>  



--
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