[
https://issues.apache.org/jira/browse/HADOOP-16772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16772.
-
Resolution: Fixed
> Extract version numbers to head of pom.xml (addendum)
>
[
https://issues.apache.org/jira/browse/HADOOP-16772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008832#comment-17008832
]
Gabor Bota commented on HADOOP-16772:
-
+1 on PR #1774
> Extract version numbers to head of pom.xml
[
https://issues.apache.org/jira/browse/HADOOP-16450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16450.
-
Resolution: Fixed
> ITestS3ACommitterFactory failing, S3 client is not inconsistent
>
[
https://issues.apache.org/jira/browse/HADOOP-16424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16424.
-
Resolution: Fixed
Got +1 on #1691 from [~ste...@apache.org]. Committing.
> S3Guard fsck:
Gabor Bota created HADOOP-16745:
---
Summary: S3Guard fsck: Use enum instead of int for severity in
violations
Key: HADOOP-16745
URL: https://issues.apache.org/jira/browse/HADOOP-16745
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-16729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16729.
-
Resolution: Fixed
> Extract version numbers to head of pom.xml
>
[
https://issues.apache.org/jira/browse/HADOOP-16729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16987685#comment-16987685
]
Gabor Bota commented on HADOOP-16729:
-
+1 on #1730 and #1732. Committing.
> Extract version
[
https://issues.apache.org/jira/browse/HADOOP-16741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16986821#comment-16986821
]
Gabor Bota commented on HADOOP-16741:
-
Sure [~ste...@apache.org]
> Document `dynamodb:TagResource`
[
https://issues.apache.org/jira/browse/HADOOP-16741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reassigned HADOOP-16741:
---
Assignee: Gabor Bota
> Document `dynamodb:TagResource` an explicit client-side permission
[
https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16709.
-
Resolution: Fixed
> S3Guard: Make authoritative mode exclusive for metadata - don't check for
[
https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982609#comment-16982609
]
Gabor Bota commented on HADOOP-16709:
-
Got +1 on PR #1721 from [~ste...@apache.org]. Committing.
>
[
https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16709:
Summary: [S3Guard] Make authoritative mode exclusive for metadata - don't
check for expiry for
[
https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16709:
Summary: S3Guard: Make authoritative mode exclusive for metadata - don't
check for expiry for
[
https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16709:
Summary: Make authoritative mode exclusive for metadata - don't check for
expiry for
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16484:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> S3A to warn or fail if
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16976514#comment-16976514
]
Gabor Bota commented on HADOOP-16484:
-
Got +1 on GitHub Pull Request #1714 from
[
https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reassigned HADOOP-16709:
---
Assignee: Gabor Bota
> Consider having the ability to turn off TTL in S3Guard +
[
https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16975000#comment-16975000
]
Gabor Bota commented on HADOOP-16709:
-
Talking offline with [~ste...@apache.org] we figured out
[
https://issues.apache.org/jira/browse/HADOOP-16706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reassigned HADOOP-16706:
---
Assignee: Gabor Bota
> ITestClientUrlScheme fails for accounts which don't support HTTP
>
[
https://issues.apache.org/jira/browse/HADOOP-16709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16974210#comment-16974210
]
Gabor Bota commented on HADOOP-16709:
-
Sure. I can do this. The general idea behind expiry was that
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16484:
Status: Patch Available (was: In Progress)
https://github.com/apache/hadoop/pull/1714 as the
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16484 started by Gabor Bota.
---
> S3A to warn or fail if S3Guard is disabled
>
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16970505#comment-16970505
]
Gabor Bota commented on HADOOP-16484:
-
Sure, I'm happy to do this.
> S3A to warn or fail if
[
https://issues.apache.org/jira/browse/HADOOP-16473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reassigned HADOOP-16473:
---
Assignee: Gabor Bota
> S3Guard prune to only remove auth dir marker if files (not
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16484.
-
Fix Version/s: 3.3.0
Target Version/s: 3.3.0 (was: 3.2.2)
Resolution: Fixed
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966594#comment-16966594
]
Gabor Bota commented on HADOOP-16484:
-
+1 from [~ste...@apache.org] on PR #1661, committed to
[
https://issues.apache.org/jira/browse/HADOOP-16424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16424 started by Gabor Bota.
---
> S3Guard fsck: Check internal consistency of the MetadataStore
>
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16484 started by Gabor Bota.
---
> S3A to warn or fail if S3Guard is disabled
>
[
https://issues.apache.org/jira/browse/HADOOP-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16653.
-
Resolution: Fixed
> S3Guard DDB overreacts to no tag access
>
[
https://issues.apache.org/jira/browse/HADOOP-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960909#comment-16960909
]
Gabor Bota commented on HADOOP-16653:
-
+1 on PR#1660 from [~ste...@apache.org]. Committing.
>
[
https://issues.apache.org/jira/browse/HADOOP-16424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16953649#comment-16953649
]
Gabor Bota commented on HADOOP-16424:
-
Our code should not be creating orphan entries. If we have
[
https://issues.apache.org/jira/browse/HADOOP-16424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16898870#comment-16898870
]
Gabor Bota edited comment on HADOOP-16424 at 10/17/19 11:35 AM:
Tasks
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952938#comment-16952938
]
Gabor Bota edited comment on HADOOP-16484 at 10/16/19 3:29 PM:
---
I removed
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16952938#comment-16952938
]
Gabor Bota commented on HADOOP-16484:
-
I removed status (merged with inform) so at inform level it
[
https://issues.apache.org/jira/browse/HADOOP-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951043#comment-16951043
]
Gabor Bota commented on HADOOP-16653:
-
It was cleary in the docs, so I'll update that as well:
[
https://issues.apache.org/jira/browse/HADOOP-16653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16951043#comment-16951043
]
Gabor Bota edited comment on HADOOP-16653 at 10/14/19 2:47 PM:
---
It was
[
https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949341#comment-16949341
]
Gabor Bota commented on HADOOP-16349:
-
https://github.com/apache/hadoop/pull/1576
Fixed in
[
https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16349.
-
Resolution: Fixed
> DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry
[
https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16520.
-
Resolution: Fixed
> Race condition in DDB table init and waiting threads
>
[
https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16949339#comment-16949339
]
Gabor Bota commented on HADOOP-16520:
-
+1 on #1576 from [~ste...@apache.org]. Committing. Thanks.
[
https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16520:
Summary: Race condition in DDB table init and waiting threads (was: race
condition in DDB table
[
https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16942161#comment-16942161
]
Gabor Bota commented on HADOOP-16349:
-
I'm going to fix this with HADOOP-16520
>
[
https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16349 started by Gabor Bota.
---
> DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn on retry
>
[
https://issues.apache.org/jira/browse/HADOOP-16349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reassigned HADOOP-16349:
---
Assignee: Gabor Bota
> DynamoDBMetadataStore.getVersionMarkerItem() to log at info/warn
[
https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16520 started by Gabor Bota.
---
> race condition in DDB table init and waiting threads
>
[
https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16938690#comment-16938690
]
Gabor Bota commented on HADOOP-16520:
-
I'll try to solve this the other way: add the version marker
[
https://issues.apache.org/jira/browse/HADOOP-16579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reassigned HADOOP-16579:
---
Assignee: Norbert Kalmar
> Upgrade to Apache Curator 4.2.0 in Hadoop
>
[
https://issues.apache.org/jira/browse/HADOOP-16529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16529.
-
Resolution: Workaround
> Allow AZURE_CREATE_REMOTE_FILESYSTEM_DURING_INITIALIZATION to be set
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937551#comment-16937551
]
Gabor Bota commented on HADOOP-16138:
-
That is true. Sorry [~ayushtkn].
The way I plan to fix it:
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16138.
-
Target Version/s: 3.3.0
Resolution: Fixed
> hadoop fs mkdir / of nonexistent abfs
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16935762#comment-16935762
]
Gabor Bota commented on HADOOP-16138:
-
+1 by [~ste...@apache.org] on PR #1302. Committing.
>
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16565:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Region must be provided
[
https://issues.apache.org/jira/browse/HADOOP-16547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16547.
-
Resolution: Fixed
> s3guard prune command doesn't get AWS auth chain from FS
>
[
https://issues.apache.org/jira/browse/HADOOP-16547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932692#comment-16932692
]
Gabor Bota commented on HADOOP-16547:
-
+1 on PR 1402. Committed.
> s3guard prune command doesn't
[
https://issues.apache.org/jira/browse/HADOOP-16484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reassigned HADOOP-16484:
---
Assignee: Gabor Bota
> S3A to warn or fail if S3Guard is disabled
>
[
https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16520 stopped by Gabor Bota.
---
> race condition in DDB table init and waiting threads
>
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932216#comment-16932216
]
Gabor Bota commented on HADOOP-16565:
-
+1 from [~ste...@apache.org] on PR 1454. Committing.
>
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16565:
Status: Patch Available (was: In Progress)
> Region must be provided when requesting session
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16565 started by Gabor Bota.
---
> Region must be provided when requesting session credentials or
>
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16565:
Summary: Region must be provided when requesting session credentials or
SdkClientException will
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reopened HADOOP-16565:
-
Reopened to add a message.
> Fix "com.amazonaws.SdkClientException: Unable to find a region via
[
https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16520 started by Gabor Bota.
---
> race condition in DDB table init and waiting threads
>
[
https://issues.apache.org/jira/browse/HADOOP-16520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota reassigned HADOOP-16520:
---
Assignee: Gabor Bota
> race condition in DDB table init and waiting threads
>
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16565.
-
Resolution: Workaround
> Fix "com.amazonaws.SdkClientException: Unable to find a region via
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929284#comment-16929284
]
Gabor Bota commented on HADOOP-16565:
-
It worked with the following STS config:
{noformat}
[
https://issues.apache.org/jira/browse/HADOOP-16565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16929242#comment-16929242
]
Gabor Bota commented on HADOOP-16565:
-
I don't have any STS endpoint besides
{noformat}
[
https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16566.
-
Resolution: Fixed
> S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of
>
[
https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928734#comment-16928734
]
Gabor Bota commented on HADOOP-16566:
-
+1 by [~ste...@apache.org] on #1433 PR.
Committing.
>
[
https://issues.apache.org/jira/browse/HADOOP-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16423.
-
Resolution: Fixed
> S3Guarld fsck: Check metadata consistency from S3 to metadatastore (log)
>
[
https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928693#comment-16928693
]
Gabor Bota commented on HADOOP-16566:
-
maybe, but it would be better to update guava everywhere.
>
[
https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-16566 started by Gabor Bota.
---
> S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of
>
Gabor Bota created HADOOP-16566:
---
Summary: S3Guard fsck: Use org.apache.hadoop.util.StopWatch
instead of com.google.common.base.Stopwatch
Key: HADOOP-16566
URL: https://issues.apache.org/jira/browse/HADOOP-16566
[
https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16566:
Component/s: fs/s3
> S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of
>
[
https://issues.apache.org/jira/browse/HADOOP-16566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16566:
Affects Version/s: 3.3.0
> S3Guard fsck: Use org.apache.hadoop.util.StopWatch instead of
>
Gabor Bota created HADOOP-16565:
---
Summary: Fix "com.amazonaws.SdkClientException: Unable to find a
region via the region provider chain."
Key: HADOOP-16565
URL: https://issues.apache.org/jira/browse/HADOOP-16565
[
https://issues.apache.org/jira/browse/HADOOP-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16928449#comment-16928449
]
Gabor Bota commented on HADOOP-16423:
-
+1 from [~ste...@apache.org] on PR #1208. Committing.
Gabor Bota created HADOOP-16564:
---
Summary: S3Guarld fsck: Add docs to the first iteration
(S3->ddbMS, -verify)
Key: HADOOP-16564
URL: https://issues.apache.org/jira/browse/HADOOP-16564
Project: Hadoop
Gabor Bota created HADOOP-16563:
---
Summary: S3Guard fsck: Detect if a directory if authoritative and
highlight errors if detected in it
Key: HADOOP-16563
URL: https://issues.apache.org/jira/browse/HADOOP-16563
[
https://issues.apache.org/jira/browse/HADOOP-16507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926405#comment-16926405
]
Gabor Bota commented on HADOOP-16507:
-
++ additional task:
Add `-verbose` arg to the fsck with
[
https://issues.apache.org/jira/browse/HADOOP-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16924058#comment-16924058
]
Gabor Bota commented on HADOOP-16550:
-
Merged PR #9
> Spark config name error on the Launching
[
https://issues.apache.org/jira/browse/HADOOP-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16550.
-
Resolution: Fixed
> Spark config name error on the Launching Applications Using Docker
[
https://issues.apache.org/jira/browse/HADOOP-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16550:
Description:
On the "Launching Applications Using Docker Containers" page at the "Example:
[
https://issues.apache.org/jira/browse/HADOOP-16550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16923501#comment-16923501
]
Gabor Bota commented on HADOOP-16550:
-
Sure, thanks for the contribution [~attilapiros].
LGTM, +1.
[
https://issues.apache.org/jira/browse/HADOOP-16529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913420#comment-16913420
]
Gabor Bota commented on HADOOP-16529:
-
Note: a possible fix for this could be to add
{code:java}
Gabor Bota created HADOOP-16529:
---
Summary: Allow
AZURE_CREATE_REMOTE_FILESYSTEM_DURING_INITIALIZATION to be set from abfs.xml
property
Key: HADOOP-16529
URL: https://issues.apache.org/jira/browse/HADOOP-16529
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913415#comment-16913415
]
Gabor Bota commented on HADOOP-16138:
-
I found out what's happening. We auto-create all containers
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908308#comment-16908308
]
Gabor Bota commented on HADOOP-16138:
-
Based on offline discussion with [~mackrorysd] we agreed
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16138:
Status: In Progress (was: Patch Available)
> hadoop fs mkdir / of nonexistent abfs container
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota updated HADOOP-16138:
Status: Patch Available (was: In Progress)
> hadoop fs mkdir / of nonexistent abfs container
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908062#comment-16908062
]
Gabor Bota commented on HADOOP-16138:
-
So I've created a test for it (new test class for testing
[
https://issues.apache.org/jira/browse/HADOOP-16416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908006#comment-16908006
]
Gabor Bota edited comment on HADOOP-16416 at 8/15/19 11:28 AM:
---
You
[
https://issues.apache.org/jira/browse/HADOOP-16416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16908006#comment-16908006
]
Gabor Bota commented on HADOOP-16416:
-
+1 on patch v003, even if checkstyle has it's own issues
[
https://issues.apache.org/jira/browse/HADOOP-16505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907281#comment-16907281
]
Gabor Bota commented on HADOOP-16505:
-
Thanks for working on this [~viczsaurav], and [~jojochuang]
[
https://issues.apache.org/jira/browse/HADOOP-16416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907171#comment-16907171
]
Gabor Bota commented on HADOOP-16416:
-
Thanks for working on this [~pingsutw]!
Please note that we
[
https://issues.apache.org/jira/browse/HADOOP-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16500.
-
Resolution: Fixed
Fix Version/s: 3.3.0
Committed to trunk.
> S3ADelegationTokens to
[
https://issues.apache.org/jira/browse/HADOOP-16500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16907034#comment-16907034
]
Gabor Bota commented on HADOOP-16500:
-
+1 for GitHub Pull Request #1269. Committing this.
>
Gabor Bota created HADOOP-16507:
---
Summary: S3Guard fsck: Add option to configure severity (level)
for the scan
Key: HADOOP-16507
URL: https://issues.apache.org/jira/browse/HADOOP-16507
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-16138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16905158#comment-16905158
]
Gabor Bota commented on HADOOP-16138:
-
Not recently, but I plan to fix this this week.
> hadoop fs
[
https://issues.apache.org/jira/browse/HADOOP-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16903982#comment-16903982
]
Gabor Bota commented on HADOOP-16481:
-
thanks for working on this [~ste...@apache.org]; +1;
[
https://issues.apache.org/jira/browse/HADOOP-16481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Bota resolved HADOOP-16481.
-
Resolution: Fixed
Fix Version/s: 3.3.0
Target Version/s: 3.3.0
>
101 - 200 of 1339 matches
Mail list logo
