prashantpogde commented on issue #783: HDDS-2976. Recon throws error while
trying to get snapshot over https
URL: https://github.com/apache/hadoop-ozone/pull/783#issuecomment-612322340
Done
This is an automated message from
bharatviswa504 commented on a change in pull request #806: HDDS-3374.
OMVolumeSetOwnerRequest doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806#discussion_r406973632
##
File path:
[
https://issues.apache.org/jira/browse/HDDS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3368:
-
Fix Version/s: 0.6.0
Resolution: Fixed
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/HDDS-3291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham reopened HDDS-3291:
--
This has been reverted, as this is causing an issue for Hadoop applications.
> Write
[
https://issues.apache.org/jira/browse/HDDS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang updated HDDS-3377:
--
Description:
I missed this during HDDS-3000
guava-26.0-android is not used but if it's in the
vivekratnavel commented on issue #783: HDDS-2976. Recon throws error while
trying to get snapshot over https
URL: https://github.com/apache/hadoop-ozone/pull/783#issuecomment-612170412
@prashantpogde Can you rebase this branch with the current master, so we can
get a clean CI run? Thanks!
[
https://issues.apache.org/jira/browse/HDDS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17080857#comment-17080857
]
Wei-Chiu Chuang commented on HDDS-3377:
---
Looking at git history, this guava was added in HDDS-1382.
[
https://issues.apache.org/jira/browse/HDDS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3377:
-
Labels: pull-request-available (was: )
> Remove guava 26.0-android jar
>
jojochuang opened a new pull request #808: HDDS-3377. Remove guava 26.0-android
jar.
URL: https://github.com/apache/hadoop-ozone/pull/808
## What changes were proposed in this pull request?
Do not explicitly copy guava 26.0-jre to the lib/ directory, because we
already depend on
[
https://issues.apache.org/jira/browse/HDDS-3377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang reassigned HDDS-3377:
-
Assignee: Wei-Chiu Chuang
> Remove guava 26.0-android jar
>
Wei-Chiu Chuang created HDDS-3377:
-
Summary: Remove guava 26.0-android jar
Key: HDDS-3377
URL: https://issues.apache.org/jira/browse/HDDS-3377
Project: Hadoop Distributed Data Store
Issue
bharatviswa504 merged pull request #804: HDDS-3368. Ozone filesystem jar should
not include webapps folder
URL: https://github.com/apache/hadoop-ozone/pull/804
This is an automated message from the Apache Git Service.
To
bharatviswa504 commented on issue #804: HDDS-3368. Ozone filesystem jar should
not include webapps folder
URL: https://github.com/apache/hadoop-ozone/pull/804#issuecomment-612164785
Thank You @vivekratnavel for the contribution.
smengcl commented on a change in pull request #806: HDDS-3374.
OMVolumeSetOwnerRequest doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806#discussion_r406888217
##
File path:
smengcl commented on a change in pull request #806: HDDS-3374.
OMVolumeSetOwnerRequest doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806#discussion_r406888013
##
File path:
smengcl commented on a change in pull request #806: HDDS-3374.
OMVolumeSetOwnerRequest doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806#discussion_r406887127
##
File path:
Vivek Ratnavel Subramanian created HDDS-3376:
Summary: Exclude unwanted jars from Ozone Filesystem jar
Key: HDDS-3376
URL: https://issues.apache.org/jira/browse/HDDS-3376
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDDS-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3375:
-
Status: Patch Available (was: Open)
> S3A failing complete multipart upload with Ozone
[
https://issues.apache.org/jira/browse/HDDS-3093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dinesh Chitlangia updated HDDS-3093:
Fix Version/s: 0.6.0
Resolution: Fixed
Status: Resolved (was: Patch
dineshchitlangia merged pull request #800: HDDS-3093. Allow forced overwrite of
local file
URL: https://github.com/apache/hadoop-ozone/pull/800
This is an automated message from the Apache Git Service.
To respond to the
bharatviswa504 commented on a change in pull request #806: HDDS-3374.
OMVolumeSetOwnerRequest doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806#discussion_r406866823
##
File path:
bharatviswa504 commented on a change in pull request #806: HDDS-3374.
OMVolumeSetOwnerRequest doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806#discussion_r406867227
##
File path:
dineshchitlangia commented on a change in pull request #806: HDDS-3374.
OMVolumeSetOwnerRequest doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806#discussion_r406866343
##
File path:
dineshchitlangia commented on a change in pull request #806: HDDS-3374.
OMVolumeSetOwnerRequest doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806#discussion_r406865345
##
File path:
[
https://issues.apache.org/jira/browse/HDDS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham resolved HDDS-3372.
--
Fix Version/s: 0.6.0
Resolution: Fixed
> Delete HISTORY.txt
> --
bharatviswa504 merged pull request #805: HDDS-3372. Delete HISTORY.txt
URL: https://github.com/apache/hadoop-ozone/pull/805
This is an automated message from the Apache Git Service.
To respond to the message, please log on
bharatviswa504 commented on issue #805: HDDS-3372. Delete HISTORY.txt
URL: https://github.com/apache/hadoop-ozone/pull/805#issuecomment-612132851
Thank You @dineshchitlangia for the contribution
This is an automated message
bharatviswa504 opened a new pull request #807: HDDS-3375. S3A failing complete
multipart upload with Ozone S3.
URL: https://github.com/apache/hadoop-ozone/pull/807
## What changes were proposed in this pull request?
S3A failing complete multipart upload request due to namespace
[
https://issues.apache.org/jira/browse/HDDS-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3375:
-
Labels: pull-request-available (was: )
> S3A failing complete multipart upload with Ozone S3
>
Bharat Viswanadham created HDDS-3375:
Summary: S3A failing complete multipart upload with Ozone S3
Key: HDDS-3375
URL: https://issues.apache.org/jira/browse/HDDS-3375
Project: Hadoop Distributed
smengcl commented on issue #696: HDDS-3056. Allow users to list volumes they
have access to, and optionally allow all users to list all volumes
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-612020402
I just posted https://github.com/apache/hadoop-ozone/pull/806, might
[
https://issues.apache.org/jira/browse/HDDS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-3374:
-
Description:
OMVolumeSetOwnerRequest doesn't seem to check if the user is already the owner.
If the user
[
https://issues.apache.org/jira/browse/HDDS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-3374:
-
Status: Patch Available (was: Open)
> OMVolumeSetOwnerRequest doesn't check if user is already the owner
[
https://issues.apache.org/jira/browse/HDDS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3374:
-
Labels: pull-request-available (was: )
> OMVolumeSetOwnerRequest doesn't check if user is
smengcl opened a new pull request #806: HDDS-3374. OMVolumeSetOwnerRequest
doesn't check if user is already the owner
URL: https://github.com/apache/hadoop-ozone/pull/806
## What changes were proposed in this pull request?
1. OMVolumeSetOwnerRequest doesn't check if the user is
[
https://issues.apache.org/jira/browse/HDDS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-3374:
-
Description:
1. OMVolumeSetOwnerRequest doesn't check if the user is already the owner
2. It also doesn't
Siyao Meng created HDDS-3374:
Summary: OMVolumeSetOwnerRequest doesn't check if the user is
already the owner
Key: HDDS-3374
URL: https://issues.apache.org/jira/browse/HDDS-3374
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDDS-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-3374:
-
Summary: OMVolumeSetOwnerRequest doesn't check if user is already the owner
(was:
smengcl edited a comment on issue #696: HDDS-3056. Allow users to list volumes
they have access to, and optionally allow all users to list all volumes
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-611991079
I'm able to dig a bit into the root cause of the timeout in the
smengcl edited a comment on issue #696: HDDS-3056. Allow users to list volumes
they have access to, and optionally allow all users to list all volumes
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-611991079
I'm able to dig a bit into the root cause of the timeout in the
smengcl edited a comment on issue #696: HDDS-3056. Allow users to list volumes
they have access to, and optionally allow all users to list all volumes
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-611991079
I'm able to dig a bit into the root cause of the timeout in the
smengcl edited a comment on issue #696: HDDS-3056. Allow users to list volumes
they have access to, and optionally allow all users to list all volumes
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-611991079
I'm able to dig a bit into the root cause of the timeout.
smengcl edited a comment on issue #696: HDDS-3056. Allow users to list volumes
they have access to, and optionally allow all users to list all volumes
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-611991079
I'm able to dig a bit into the root cause of the timeout.
smengcl commented on issue #696: HDDS-3056. Allow users to list volumes they
have access to, and optionally allow all users to list all volumes
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-611991079
I'm able to dig a bit into the root cause of the timeout.
Turns
[
https://issues.apache.org/jira/browse/HDDS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen O'Donnell resolved HDDS-3135.
-
Fix Version/s: 0.6.0
Resolution: Fixed
> Enable test added in HDDS-3084 when
[
https://issues.apache.org/jira/browse/HDDS-3135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3135:
-
Labels: pull-request-available (was: )
> Enable test added in HDDS-3084 when blocking issues are
sodonnel merged pull request #790: HDDS-3135. Enable topology acceptance test
added in HDDS-3084 to read data when racks stopped
URL: https://github.com/apache/hadoop-ozone/pull/790
This is an automated message from the
sodonnel commented on issue #790: HDDS-3135. Enable topology acceptance test
added in HDDS-3084 to read data when racks stopped
URL: https://github.com/apache/hadoop-ozone/pull/790#issuecomment-611950792
Thanks for the review. I will go ahead and merge this one now.
sodonnel commented on issue #668: HDDS-3139. Pipeline placement should max out
pipeline usage
URL: https://github.com/apache/hadoop-ozone/pull/668#issuecomment-611950545
Thanks for the update. Its a holiday weekend here in Europe, so it will
probably be Tuesday before I get to look at
timmylicheng commented on issue #668: HDDS-3139. Pipeline placement should max
out pipeline usage
URL: https://github.com/apache/hadoop-ozone/pull/668#issuecomment-611927572
> > @sodonnel I rebase the code with minor conflicts in test class, but the
test won't pass. I took a close look
Attila Doroszlai created HDDS-3373:
--
Summary: Intermittent failure in TestDnRatisLogParser
Key: HDDS-3373
URL: https://issues.apache.org/jira/browse/HDDS-3373
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-3373:
---
Attachment: TEST-org.apache.hadoop.ozone.dn.ratis.TestDnRatisLogParser.xml
[
https://issues.apache.org/jira/browse/HDDS-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3372:
-
Labels: pull-request-available (was: )
> Delete HISTORY.txt
> --
>
>
dineshchitlangia opened a new pull request #805: HDDS-3372. Delete HISTORY.txt
URL: https://github.com/apache/hadoop-ozone/pull/805
## What changes were proposed in this pull request?
Deleted old HISTORY.txt missed during HDDS-2294
## What is the link to the Apache JIRA
Dinesh Chitlangia created HDDS-3372:
---
Summary: Delete HISTORY.txt
Key: HDDS-3372
URL: https://issues.apache.org/jira/browse/HDDS-3372
Project: Hadoop Distributed Data Store
Issue Type: Bug
55 matches
Mail list logo
