[jira] [Assigned] (HDDS-4155) Directory and filename can end up with same name in a path

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4155: Assignee: Bharat Viswanadham > Directory and filename can end up with same name in

[jira] [Comment Edited] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186062#comment-17186062 ] Bharat Viswanadham edited comment on HDDS-4097 at 8/27/20, 7:20 PM:

[jira] [Commented] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186062#comment-17186062 ] Bharat Viswanadham commented on HDDS-4097: -- AWS S3 also allows creating a key wit

[jira] [Commented] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17185970#comment-17185970 ] Bharat Viswanadham commented on HDDS-4097: -- [~arp] Yes, correct. > S3/Ozone Fil

[jira] [Updated] (HDDS-4155) Directory and filename can end up with same name

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4155: - Description: Scenario: Create Key via S3, and Create Directory through Fs. # open key ->

[jira] [Updated] (HDDS-4155) Directory and filename can end up with same name in a path

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4155: - Summary: Directory and filename can end up with same name in a path (was: Directory and f

[jira] [Updated] (HDDS-4155) Directory and filename can end up with same name

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4155: - Environment: (was: Scenario: # Create key -> /a/b/c # CreateDirectory -> /a/b/c # Co

[jira] [Created] (HDDS-4155) Directory and filename can end up with same name

Bharat Viswanadham created HDDS-4155: Summary: Directory and filename can end up with same name Key: HDDS-4155 URL: https://issues.apache.org/jira/browse/HDDS-4155 Project: Hadoop Distributed Data

[jira] [Updated] (HDDS-4155) Directory and filename can end up with same name

[ https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4155: - Description: Scenario: # Create key -> /a/b/c # CreateDirectory -> /a/b/c # CommitKey -

[jira] [Created] (HDDS-4154) Enable S3 robot tests with ozone.om.enable.filesystem.paths enabled

Bharat Viswanadham created HDDS-4154: Summary: Enable S3 robot tests with ozone.om.enable.filesystem.paths enabled Key: HDDS-4154 URL: https://issues.apache.org/jira/browse/HDDS-4154 Project: Hado

[jira] [Commented] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184184#comment-17184184 ] Bharat Viswanadham commented on HDDS-4097: -- {quote}Why do we need that specific s

[jira] [Resolved] (HDDS-4020) ACL commands like getacl and setacl should return a response only when Native Authorizer is enabled

[ https://issues.apache.org/jira/browse/HDDS-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4020. -- Resolution: Won't Fix > ACL commands like getacl and setacl should return a response onl

[jira] [Created] (HDDS-4124) Verify parent directories and file system semantics during initiate MPU

Bharat Viswanadham created HDDS-4124: Summary: Verify parent directories and file system semantics during initiate MPU Key: HDDS-4124 URL: https://issues.apache.org/jira/browse/HDDS-4124 Project:

[jira] [Assigned] (HDDS-4124) Verify parent directories and file system semantics during initiate MPU

[ https://issues.apache.org/jira/browse/HDDS-4124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4124: Assignee: Bharat Viswanadham > Verify parent directories and file system semantics

[jira] [Updated] (HDDS-4117) Normalize Keypath for listKeys.

[ https://issues.apache.org/jira/browse/HDDS-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4117: - Status: Patch Available (was: Open) > Normalize Keypath for listKeys. >

[jira] [Updated] (HDDS-4117) Normalize Keypath for listKeys.

[ https://issues.apache.org/jira/browse/HDDS-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4117: - Labels: (was: pull-request-available) > Normalize Keypath for listKeys. > -

[jira] [Updated] (HDDS-4117) Normalize Keypath for listKeys.

[ https://issues.apache.org/jira/browse/HDDS-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4117: - Description: When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the Ke

[jira] [Created] (HDDS-4117) Normalize Keypath for listKeys.

Bharat Viswanadham created HDDS-4117: Summary: Normalize Keypath for listKeys. Key: HDDS-4117 URL: https://issues.apache.org/jira/browse/HDDS-4117 Project: Hadoop Distributed Data Store

[jira] [Commented] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177116#comment-17177116 ] Bharat Viswanadham commented on HDDS-4097: -- Hi [~elek] Thank You for reviewing d

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

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

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

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

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

Bharat Viswanadham created HDDS-4102: Summary: Normalize Keypath for lookupKey Key: HDDS-4102 URL: https://issues.apache.org/jira/browse/HDDS-4102 Project: Hadoop Distributed Data Store I

[jira] [Resolved] (HDDS-4067) Implement toString for OMTransactionInfo

[ https://issues.apache.org/jira/browse/HDDS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4067. -- Fix Version/s: 0.7.0 Resolution: Fixed > Implement toString for OMTransactionInfo

[jira] [Updated] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4097: - Description: This Jira is to implement changes required to use Ozone buckets when data is

[jira] [Updated] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4097: - Description: This Jira is to implement changes required to use Ozone buckets when data is

[jira] [Updated] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4097: - Description: This Jira is to implement changes required to use Ozone buckets when data is

[jira] [Updated] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4097: - Attachment: Ozone FileSystem Paths Enabled.docx Ozone filesystem path enabl

[jira] [Assigned] (HDDS-4097) S3/Ozone Filesystem inter-op

[ https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4097: Assignee: Bharat Viswanadham > S3/Ozone Filesystem inter-op > -

[jira] [Created] (HDDS-4097) S3/Ozone Filesystem inter-op

Bharat Viswanadham created HDDS-4097: Summary: S3/Ozone Filesystem inter-op Key: HDDS-4097 URL: https://issues.apache.org/jira/browse/HDDS-4097 Project: Hadoop Distributed Data Store Issu

[jira] [Updated] (HDDS-4068) Client Retry for ipc.client.connect.max.retries when first OM is down

[ https://issues.apache.org/jira/browse/HDDS-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4068: - Component/s: Ozone Client > Client Retry for ipc.client.connect.max.retries when first OM

[jira] [Updated] (HDDS-4068) Client Retry for ipc.client.connect.max.retries when first OM is down

[ https://issues.apache.org/jira/browse/HDDS-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4068: - Component/s: OM HA > Client Retry for ipc.client.connect.max.retries when first OM is down

[jira] [Resolved] (HDDS-4063) Fix InstallSnapshot in OM HA

[ https://issues.apache.org/jira/browse/HDDS-4063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4063. -- Fix Version/s: 0.6.0 Resolution: Fixed > Fix InstallSnapshot in OM HA > -

[jira] [Commented] (HDDS-4068) Client Retry for ipc.client.connect.max.retries when first OM is down

[ https://issues.apache.org/jira/browse/HDDS-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171849#comment-17171849 ] Bharat Viswanadham commented on HDDS-4068: -- cc [~arp]] [~hanishakoneru] Any thoug

[jira] [Updated] (HDDS-4068) Client Retry for ipc.client.connect.max.retries when first OM is down

[ https://issues.apache.org/jira/browse/HDDS-4068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4068: - Description: Right now retry logic on client to OM is, it will try connect to OM1, if it i

[jira] [Created] (HDDS-4068) Client Retry for ipc.client.connect.max.retries when first OM is down

Bharat Viswanadham created HDDS-4068: Summary: Client Retry for ipc.client.connect.max.retries when first OM is down Key: HDDS-4068 URL: https://issues.apache.org/jira/browse/HDDS-4068 Project: Ha

[jira] [Commented] (HDDS-4067) Implement toString for OMTransactionInfo

[ https://issues.apache.org/jira/browse/HDDS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171847#comment-17171847 ] Bharat Viswanadham commented on HDDS-4067: -- I have added you to the contributor l

[jira] [Assigned] (HDDS-4067) Implement toString for OMTransactionInfo

[ https://issues.apache.org/jira/browse/HDDS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4067: Assignee: Rui Wang > Implement toString for OMTransactionInfo > ---

[jira] [Commented] (HDDS-1745) Add integration test for createDirectory for OM HA

[ https://issues.apache.org/jira/browse/HDDS-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171837#comment-17171837 ] Bharat Viswanadham commented on HDDS-1745: -- Opened one new Jira https://issues.a

[jira] [Updated] (HDDS-4067) Implement toString for OMTransactionInfo

[ https://issues.apache.org/jira/browse/HDDS-4067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4067: - Labels: newbie (was: ) > Implement toString for OMTransactionInfo > -

[jira] [Created] (HDDS-4067) Implement toString for OMTransactionInfo

Bharat Viswanadham created HDDS-4067: Summary: Implement toString for OMTransactionInfo Key: HDDS-4067 URL: https://issues.apache.org/jira/browse/HDDS-4067 Project: Hadoop Distributed Data Store

[jira] [Commented] (HDDS-1745) Add integration test for createDirectory for OM HA

[ https://issues.apache.org/jira/browse/HDDS-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171635#comment-17171635 ] Bharat Viswanadham commented on HDDS-1745: -- [~amaliujia] Sorry missed this ping.

[jira] [Comment Edited] (HDDS-1745) Add integration test for createDirectory for OM HA

[ https://issues.apache.org/jira/browse/HDDS-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17171635#comment-17171635 ] Bharat Viswanadham edited comment on HDDS-1745 at 8/5/20, 5:15 PM: -

[jira] [Resolved] (HDDS-3446) Enable TestOzoneManagerRestart test cases

[ https://issues.apache.org/jira/browse/HDDS-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-3446. -- Fix Version/s: 0.7.0 Resolution: Fixed > Enable TestOzoneManagerRestart test case

[jira] [Commented] (HDDS-4020) ACL commands like getacl and setacl should return a response only when Native Authorizer is enabled

[ https://issues.apache.org/jira/browse/HDDS-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166748#comment-17166748 ] Bharat Viswanadham commented on HDDS-4020: -- Hi [~pifta] Thanks for the suggestion

[jira] [Updated] (HDDS-4044) Deprecate ozone.s3g.volume.name

[ https://issues.apache.org/jira/browse/HDDS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4044: - Component/s: S3 > Deprecate ozone.s3g.volume.name > --- > >

[jira] [Updated] (HDDS-4044) Deprecate ozone.s3g.volume.name

[ https://issues.apache.org/jira/browse/HDDS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4044: - Target Version/s: 0.6.0 > Deprecate ozone.s3g.volume.name > --

[jira] [Assigned] (HDDS-4044) Deprecate ozone.s3g.volume.name

[ https://issues.apache.org/jira/browse/HDDS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4044: Assignee: Bharat Viswanadham > Deprecate ozone.s3g.volume.name > --

[jira] [Updated] (HDDS-4044) Deprecate ozone.s3g.volume.name

[ https://issues.apache.org/jira/browse/HDDS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4044: - Priority: Blocker (was: Major) > Deprecate ozone.s3g.volume.name > --

[jira] [Created] (HDDS-4044) Deprecate ozone.s3g.volume.name

Bharat Viswanadham created HDDS-4044: Summary: Deprecate ozone.s3g.volume.name Key: HDDS-4044 URL: https://issues.apache.org/jira/browse/HDDS-4044 Project: Hadoop Distributed Data Store I

[jira] [Updated] (HDDS-4044) Deprecate ozone.s3g.volume.name

[ https://issues.apache.org/jira/browse/HDDS-4044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4044: - Description: HDDS-3612 introduced bucket links. After this feature now we don't need this

[jira] [Updated] (HDDS-3955) Unable to list intermediate paths on keys created using S3G.

[ https://issues.apache.org/jira/browse/HDDS-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3955: - Fix Version/s: 0.6.0 > Unable to list intermediate paths on keys created using S3G. >

[jira] [Resolved] (HDDS-4011) Update S3 related documentation

[ https://issues.apache.org/jira/browse/HDDS-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4011. -- Fix Version/s: 0.6.0 Resolution: Fixed > Update S3 related documentation > --

[jira] [Assigned] (HDDS-4040) OFS use deleteObjects when delete directory

[ https://issues.apache.org/jira/browse/HDDS-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4040: Assignee: Siyao Meng (was: Bharat Viswanadham) > OFS use deleteObjects when delete

[jira] [Assigned] (HDDS-4040) OFS use deleteObjects when delete directory

[ https://issues.apache.org/jira/browse/HDDS-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4040: Assignee: Bharat Viswanadham (was: Siyao Meng) > OFS use deleteObjects when delete

[jira] [Created] (HDDS-4040) OFS use deleteObjects when delete directory

Bharat Viswanadham created HDDS-4040: Summary: OFS use deleteObjects when delete directory Key: HDDS-4040 URL: https://issues.apache.org/jira/browse/HDDS-4040 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-4025) Add test for creating encrypted key

[ https://issues.apache.org/jira/browse/HDDS-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4025: - Fix Version/s: 0.7.0 Resolution: Fixed Status: Resolved (was: Patch Avai

[jira] [Resolved] (HDDS-4007) Generate encryption info for the bucket outside bucket lock

[ https://issues.apache.org/jira/browse/HDDS-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4007. -- Fix Version/s: 0.7.0 Resolution: Fixed > Generate encryption info for the bucket

[jira] [Updated] (HDDS-3955) Unable to list intermediate paths on keys created using S3G.

[ https://issues.apache.org/jira/browse/HDDS-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3955: - Issue Type: New Feature (was: Bug) > Unable to list intermediate paths on keys created us

[jira] [Assigned] (HDDS-4010) S3G startup fails when multiple service ids are configured.

[ https://issues.apache.org/jira/browse/HDDS-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4010: Assignee: Bharat Viswanadham > S3G startup fails when multiple service ids are conf

[jira] [Updated] (HDDS-4010) S3G startup fails when multiple service ids are configured.

[ https://issues.apache.org/jira/browse/HDDS-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4010: - Labels: pull-request-available (was: newbie pull-request-available) > S3G startup fails w

[jira] [Updated] (HDDS-4022) Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket

[ https://issues.apache.org/jira/browse/HDDS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4022: - Labels: (was: S3) > Ozone s3 API return 400 Bad Request for head-bucket for non existing

[jira] [Created] (HDDS-4022) Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket

Bharat Viswanadham created HDDS-4022: Summary: Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket Key: HDDS-4022 URL: https://issues.apache.org/jira/browse/HDDS-4022 Proje

[jira] [Updated] (HDDS-4022) Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket

[ https://issues.apache.org/jira/browse/HDDS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4022: - Reporter: Namit Maheshwari (was: Bharat Viswanadham) > Ozone s3 API return 400 Bad Reques

[jira] [Updated] (HDDS-4022) Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket

[ https://issues.apache.org/jira/browse/HDDS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4022: - Component/s: S3 > Ozone s3 API return 400 Bad Request for head-bucket for non existing buc

[jira] [Updated] (HDDS-4022) Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket

[ https://issues.apache.org/jira/browse/HDDS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4022: - Target Version/s: 0.6.0 Priority: Blocker (was: Major) > Ozone s3 API return

[jira] [Updated] (HDDS-4022) Ozone s3 API return 400 Bad Request for head-bucket for non existing bucket

[ https://issues.apache.org/jira/browse/HDDS-4022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4022: - Labels: S3 (was: ) > Ozone s3 API return 400 Bad Request for head-bucket for non existing

[jira] [Updated] (HDDS-3998) Shorten Ozone FS Hadoop compatibility module names

[ https://issues.apache.org/jira/browse/HDDS-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3998: - Fix Version/s: 0.7.0 Resolution: Fixed Status: Resolved (was: Patch Avai

[jira] [Updated] (HDDS-3827) Intermittent failure in TestKeyManagerUnit#listMultipartUploads

[ https://issues.apache.org/jira/browse/HDDS-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3827: - Fix Version/s: 0.7.0 Resolution: Fixed Status: Resolved (was: Patch Avai

[jira] [Created] (HDDS-4011) Update S3 related documentation

Bharat Viswanadham created HDDS-4011: Summary: Update S3 related documentation Key: HDDS-4011 URL: https://issues.apache.org/jira/browse/HDDS-4011 Project: Hadoop Distributed Data Store I

[jira] [Updated] (HDDS-4010) S3G startup fails when multiple service ids are configured.

[ https://issues.apache.org/jira/browse/HDDS-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4010: - Labels: newbie (was: ) > S3G startup fails when multiple service ids are configured. > --

[jira] [Created] (HDDS-4010) S3G startup fails when multiple service ids are configured.

Bharat Viswanadham created HDDS-4010: Summary: S3G startup fails when multiple service ids are configured. Key: HDDS-4010 URL: https://issues.apache.org/jira/browse/HDDS-4010 Project: Hadoop Distr

[jira] [Commented] (HDDS-3999) OM NPE and shutdown while S3MultipartUploadCommitPartResponse#checkAndUpdateDB

[ https://issues.apache.org/jira/browse/HDDS-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163120#comment-17163120 ] Bharat Viswanadham commented on HDDS-3999: -- [~maobaolong] I hope you have not sta

[jira] [Comment Edited] (HDDS-3999) OM NPE and shutdown while S3MultipartUploadCommitPartResponse#checkAndUpdateDB

[ https://issues.apache.org/jira/browse/HDDS-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163112#comment-17163112 ] Bharat Viswanadham edited comment on HDDS-3999 at 7/22/20, 10:47 PM: ---

[jira] [Comment Edited] (HDDS-3999) OM NPE and shutdown while S3MultipartUploadCommitPartResponse#checkAndUpdateDB

[ https://issues.apache.org/jira/browse/HDDS-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163112#comment-17163112 ] Bharat Viswanadham edited comment on HDDS-3999 at 7/22/20, 10:44 PM: ---

[jira] [Updated] (HDDS-3999) OM NPE and shutdown while S3MultipartUploadCommitPartResponse#checkAndUpdateDB

[ https://issues.apache.org/jira/browse/HDDS-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3999: - Priority: Blocker (was: Major) > OM NPE and shutdown while S3MultipartUploadCommitPartRes

[jira] [Updated] (HDDS-3999) OM NPE and shutdown while S3MultipartUploadCommitPartResponse#checkAndUpdateDB

[ https://issues.apache.org/jira/browse/HDDS-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3999: - Attachment: test-repro.patch > OM NPE and shutdown while S3MultipartUploadCommitPartRespon

[jira] [Commented] (HDDS-3999) OM NPE and shutdown while S3MultipartUploadCommitPartResponse#checkAndUpdateDB

[ https://issues.apache.org/jira/browse/HDDS-3999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163112#comment-17163112 ] Bharat Viswanadham commented on HDDS-3999: -- Hi [~maobaolong] Thanks for reporting

[jira] [Resolved] (HDDS-4003) Delete the redundant word of the description

[ https://issues.apache.org/jira/browse/HDDS-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham resolved HDDS-4003. -- Fix Version/s: 0.7.0 Resolution: Fixed > Delete the redundant word of the descrip

[jira] [Commented] (HDDS-4008) Recon should fallback to ozone.om.service.ids when the internal service id is not defined.

[ https://issues.apache.org/jira/browse/HDDS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163064#comment-17163064 ] Bharat Viswanadham commented on HDDS-4008: -- If single OM HA is a common case, the

[jira] [Comment Edited] (HDDS-4008) Recon should fallback to ozone.om.service.ids when the internal service id is not defined.

[ https://issues.apache.org/jira/browse/HDDS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163035#comment-17163035 ] Bharat Viswanadham edited comment on HDDS-4008 at 7/22/20, 7:59 PM:

[jira] [Commented] (HDDS-4008) Recon should fallback to ozone.om.service.ids when the internal service id is not defined.

[ https://issues.apache.org/jira/browse/HDDS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163035#comment-17163035 ] Bharat Viswanadham commented on HDDS-4008: -- [~avijayan] ozone.om.internal.service

[jira] [Comment Edited] (HDDS-4008) Recon should fallback to ozone.om.service.ids when the internal service id is not defined.

[ https://issues.apache.org/jira/browse/HDDS-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163035#comment-17163035 ] Bharat Viswanadham edited comment on HDDS-4008 at 7/22/20, 7:58 PM:

[jira] [Updated] (HDDS-4007) Generate encryption info for the bucket outside bucket lock

[ https://issues.apache.org/jira/browse/HDDS-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4007: - Component/s: Security Ozone Manager Issue Type: Improvement (was: Bu

[jira] [Created] (HDDS-4007) Generate encryption info for the bucket outside bucket lock

Bharat Viswanadham created HDDS-4007: Summary: Generate encryption info for the bucket outside bucket lock Key: HDDS-4007 URL: https://issues.apache.org/jira/browse/HDDS-4007 Project: Hadoop Distr

[jira] [Updated] (HDDS-4006) Disallow MPU on encrypted buckets.

[ https://issues.apache.org/jira/browse/HDDS-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4006: - Summary: Disallow MPU on encrypted buckets. (was: S3 MPU not supported on encrypted bucke

[jira] [Updated] (HDDS-4006) S3 MPU not supported on encrypted buckets

[ https://issues.apache.org/jira/browse/HDDS-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4006: - Target Version/s: 0.6.0 (was: 0.7.0) > S3 MPU not supported on encrypted buckets > --

[jira] [Updated] (HDDS-4006) S3 MPU not supported on encrypted buckets

[ https://issues.apache.org/jira/browse/HDDS-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4006: - Priority: Blocker (was: Major) > S3 MPU not supported on encrypted buckets >

[jira] [Assigned] (HDDS-4006) S3 MPU not supported on encrypted buckets

[ https://issues.apache.org/jira/browse/HDDS-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4006: Assignee: Bharat Viswanadham > S3 MPU not supported on encrypted buckets >

[jira] [Updated] (HDDS-4005) Support S3 MPU on encrypted buckets

[ https://issues.apache.org/jira/browse/HDDS-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4005: - Summary: Support S3 MPU on encrypted buckets (was: S3 MPU not supported on encrypted buck

[jira] [Updated] (HDDS-4006) S3 MPU not supported on encrypted buckets

[ https://issues.apache.org/jira/browse/HDDS-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4006: - Description: With HDDS-3612 buckets created via ozone are also accessible via S3. This has

[jira] [Updated] (HDDS-4006) S3 MPU not supported on encrypted buckets

[ https://issues.apache.org/jira/browse/HDDS-4006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4006: - Description: With HDDS-3612 buckets created via ozone are also accessible via S3. This has

[jira] [Updated] (HDDS-4005) S3 MPU not supported on encrypted buckets

[ https://issues.apache.org/jira/browse/HDDS-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4005: - Issue Type: New Feature (was: Bug) > S3 MPU not supported on encrypted buckets >

[jira] [Created] (HDDS-4006) S3 MPU not supported on encrypted buckets

Bharat Viswanadham created HDDS-4006: Summary: S3 MPU not supported on encrypted buckets Key: HDDS-4006 URL: https://issues.apache.org/jira/browse/HDDS-4006 Project: Hadoop Distributed Data Store

[jira] [Created] (HDDS-4005) S3 MPU not supported on encrypted buckets

Bharat Viswanadham created HDDS-4005: Summary: S3 MPU not supported on encrypted buckets Key: HDDS-4005 URL: https://issues.apache.org/jira/browse/HDDS-4005 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-4005) S3 MPU not supported on encrypted buckets

[ https://issues.apache.org/jira/browse/HDDS-4005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-4005: - Target Version/s: 0.7.0 > S3 MPU not supported on encrypted buckets >

[jira] [Assigned] (HDDS-4003) Delete the redundant word of the description

[ https://issues.apache.org/jira/browse/HDDS-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-4003: Assignee: Ho-Chin Lin > Delete the redundant word of the description >

[jira] [Updated] (HDDS-3985) Update proto.lock files

[ https://issues.apache.org/jira/browse/HDDS-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3985: - Resolution: Not A Problem Status: Resolved (was: Patch Available) > Update proto.

[jira] [Created] (HDDS-3993) Create volume required for S3G during OM startup

Bharat Viswanadham created HDDS-3993: Summary: Create volume required for S3G during OM startup Key: HDDS-3993 URL: https://issues.apache.org/jira/browse/HDDS-3993 Project: Hadoop Distributed Data

[jira] [Assigned] (HDDS-3985) Update proto.lock files

[ https://issues.apache.org/jira/browse/HDDS-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham reassigned HDDS-3985: Assignee: Bharat Viswanadham (was: Vivek Ratnavel Subramanian) > Update proto.lock

[jira] [Updated] (HDDS-3985) Update proto.lock files

[ https://issues.apache.org/jira/browse/HDDS-3985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Viswanadham updated HDDS-3985: - Status: Patch Available (was: Open) > Update proto.lock files > --- >

<    1   2   3   4   5   6   7   8   >