[jira] [Updated] (HADOOP-13868) New defaults for S3A multi-part configuration

[ https://issues.apache.org/jira/browse/HADOOP-13868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-13868: --- Resolution: Fixed Status: Resolved (was: Patch Available) > New defaults for S3A

[jira] [Commented] (HADOOP-13868) New defaults for S3A multi-part configuration

[ https://issues.apache.org/jira/browse/HADOOP-13868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888395#comment-16888395 ] Sean Mackrory commented on HADOOP-13868: Bit-rot after only 2 1/2 years? Imagine that! Actually

[jira] [Commented] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16882398#comment-16882398 ] Sean Mackrory commented on HADOOP-15729: Oh it was an obsolete import. Pull request created:

[jira] [Updated] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15729: --- Attachment: (was: HADOOP-15729.002.patch) > [s3a] stop treat fs.s3a.max.threads as the

[jira] [Updated] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15729: --- Attachment: HADOOP-15729.002.patch > [s3a] stop treat fs.s3a.max.threads as the long-term

[jira] [Updated] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15729: --- Status: Patch Available (was: Open) Resubmitting as checkstyle output has expired. >

[jira] [Updated] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15729: --- Status: Open (was: Patch Available) > [s3a] stop treat fs.s3a.max.threads as the

[jira] [Commented] (HADOOP-13980) S3Guard CLI: Add fsck check command

[ https://issues.apache.org/jira/browse/HADOOP-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880424#comment-16880424 ] Sean Mackrory commented on HADOOP-13980: {quote}Export metadatastore and S3 bucket

[jira] [Updated] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16396: --- Resolution: Fixed Status: Resolved (was: Patch Available) Thanks, [~gabor.bota].

[jira] [Created] (HADOOP-16409) Allow authoritative mode on non-qualified paths

Sean Mackrory created HADOOP-16409: -- Summary: Allow authoritative mode on non-qualified paths Key: HADOOP-16409 URL: https://issues.apache.org/jira/browse/HADOOP-16409 Project: Hadoop Common

[jira] [Commented] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16876283#comment-16876283 ] Sean Mackrory commented on HADOOP-16396: Submitted an iteration based on your feedback via PR.

[jira] [Commented] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875275#comment-16875275 ] Sean Mackrory commented on HADOOP-16396: Added a couple of other things: * Ability to specify

[jira] [Updated] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16396: --- Attachment: HADOOP-16396.003.patch > Allow authoritative mode on a subdirectory >

[jira] [Updated] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16396: --- Status: Patch Available (was: Open) > Allow authoritative mode on a subdirectory >

[jira] [Commented] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875113#comment-16875113 ] Sean Mackrory commented on HADOOP-16396: I see what I'm missing: listStatus does write-backs.

[jira] [Updated] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16396: --- Attachment: HADOOP-16396.002.patch > Allow authoritative mode on a subdirectory >

[jira] [Commented] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873692#comment-16873692 ] Sean Mackrory commented on HADOOP-16396: Attaching my current state, although I'm not done. My

[jira] [Updated] (HADOOP-16396) Allow authoritative mode on a subdirectory

[ https://issues.apache.org/jira/browse/HADOOP-16396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16396: --- Attachment: HADOOP-16396.001.patch > Allow authoritative mode on a subdirectory >

[jira] [Created] (HADOOP-16396) Allow authoritative mode on a subdirectory

Sean Mackrory created HADOOP-16396: -- Summary: Allow authoritative mode on a subdirectory Key: HADOOP-16396 URL: https://issues.apache.org/jira/browse/HADOOP-16396 Project: Hadoop Common

[jira] [Commented] (HADOOP-13551) hook up AwsSdkMetrics to hadoop metrics

[ https://issues.apache.org/jira/browse/HADOOP-13551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873409#comment-16873409 ] Sean Mackrory commented on HADOOP-13551: As an update, every time someone has asked about this,

[jira] [Updated] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15729: --- Status: Patch Available (was: Open) > [s3a] stop treat fs.s3a.max.threads as the

[jira] [Commented] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872630#comment-16872630 ] Sean Mackrory commented on HADOOP-15729: So I tried out some of the same 1 GB uploads in the

[jira] [Updated] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15729: --- Attachment: HADOOP-15729.002.patch > [s3a] stop treat fs.s3a.max.threads as the long-term

[jira] [Comment Edited] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872396#comment-16872396 ] Sean Mackrory edited comment on HADOOP-15729 at 6/25/19 2:55 PM: -

[jira] [Comment Edited] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872396#comment-16872396 ] Sean Mackrory edited comment on HADOOP-15729 at 6/25/19 2:32 PM: -

[jira] [Commented] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16872396#comment-16872396 ] Sean Mackrory commented on HADOOP-15729: Having slept on it, I think we should go ahead and

[jira] [Commented] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16871830#comment-16871830 ] Sean Mackrory commented on HADOOP-15729: Attach a patch with my proposed change. Unfortunately,

[jira] [Updated] (HADOOP-15729) [s3a] stop treat fs.s3a.max.threads as the long-term minimum

[ https://issues.apache.org/jira/browse/HADOOP-15729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15729: --- Attachment: HADOOP-15729.001.patch > [s3a] stop treat fs.s3a.max.threads as the long-term

[jira] [Updated] (HADOOP-16211) Update guava to 27.0-jre in hadoop-project branch-3.2

[ https://issues.apache.org/jira/browse/HADOOP-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16211: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Update guava to

[jira] [Commented] (HADOOP-16211) Update guava to 27.0-jre in hadoop-project branch-3.2

[ https://issues.apache.org/jira/browse/HADOOP-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863098#comment-16863098 ] Sean Mackrory commented on HADOOP-16211: Thanks for getting to the bottom of that. Will commit,

[jira] [Updated] (HADOOP-16213) Update guava to 27.0-jre in hadoop-project branch-3.1

[ https://issues.apache.org/jira/browse/HADOOP-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16213: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Update guava to

[jira] [Commented] (HADOOP-16213) Update guava to 27.0-jre in hadoop-project branch-3.1

[ https://issues.apache.org/jira/browse/HADOOP-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863097#comment-16863097 ] Sean Mackrory commented on HADOOP-16213: Thanks for getting to the bottom of that. Build looks

[jira] [Commented] (HADOOP-16213) Update guava to 27.0-jre in hadoop-project branch-3.1

[ https://issues.apache.org/jira/browse/HADOOP-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858775#comment-16858775 ] Sean Mackrory commented on HADOOP-16213: Same as HADOOP-16211 - +1 on the code, but there's a

[jira] [Commented] (HADOOP-16211) Update guava to 27.0-jre in hadoop-project branch-3.2

[ https://issues.apache.org/jira/browse/HADOOP-16211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16858767#comment-16858767 ] Sean Mackrory commented on HADOOP-16211: +1 on the patch, but I don't immediately recognize the

[jira] [Updated] (HADOOP-16212) Update guava to 27.0-jre in hadoop-project branch-3.0

[ https://issues.apache.org/jira/browse/HADOOP-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16212: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed. As discussed

[jira] [Commented] (HADOOP-16212) Update guava to 27.0-jre in hadoop-project branch-3.0

[ https://issues.apache.org/jira/browse/HADOOP-16212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854601#comment-16854601 ] Sean Mackrory commented on HADOOP-16212: +1. Will commit... > Update guava to 27.0-jre in

[jira] [Resolved] (HADOOP-16321) ITestS3ASSL+TestOpenSSLSocketFactory failing with java.lang.UnsatisfiedLinkErrors

[ https://issues.apache.org/jira/browse/HADOOP-16321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory resolved HADOOP-16321. Resolution: Fixed > ITestS3ASSL+TestOpenSSLSocketFactory failing with >

[jira] [Commented] (HADOOP-15999) S3Guard: Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840846#comment-16840846 ] Sean Mackrory commented on HADOOP-15999: {quote} Seems like a common case{quote} Yeah that's

[jira] [Comment Edited] (HADOOP-15999) S3Guard: Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16840846#comment-16840846 ] Sean Mackrory edited comment on HADOOP-15999 at 5/15/19 10:49 PM: --

[jira] [Commented] (HADOOP-16281) ABFS: Rename operation, GetFileStatus before rename operation and throw exception on the driver side

[ https://issues.apache.org/jira/browse/HADOOP-16281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832524#comment-16832524 ] Sean Mackrory commented on HADOOP-16281: [~DanielZhou] I actually hadn't thought of it being

[jira] [Updated] (HADOOP-16222) Fix new deprecations after guava 27.0 update in trunk

[ https://issues.apache.org/jira/browse/HADOOP-16222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16222: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Fix new deprecations

[jira] [Commented] (HADOOP-16222) Fix new deprecations after guava 27.0 update in trunk

[ https://issues.apache.org/jira/browse/HADOOP-16222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16825327#comment-16825327 ] Sean Mackrory commented on HADOOP-16222: +1. Note that it's no longer clean - YARN-9495 already

[jira] [Comment Edited] (HADOOP-16085) S3Guard: use object version or etags to protect against inconsistent read after replace/overwrite

[ https://issues.apache.org/jira/browse/HADOOP-16085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820236#comment-16820236 ] Sean Mackrory edited comment on HADOOP-16085 at 4/17/19 3:58 PM: - Left

[jira] [Commented] (HADOOP-16085) S3Guard: use object version or etags to protect against inconsistent read after replace/overwrite

[ https://issues.apache.org/jira/browse/HADOOP-16085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820236#comment-16820236 ] Sean Mackrory commented on HADOOP-16085: Left some feedback in-line on the pull-request (and

[jira] [Commented] (HADOOP-16246) Unbounded thread pool maximum pool size in S3AFileSystem TransferManager

[ https://issues.apache.org/jira/browse/HADOOP-16246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815024#comment-16815024 ] Sean Mackrory commented on HADOOP-16246: Yeah it was actually almost the reverse, IIRC. A

[jira] [Commented] (HADOOP-16246) Unbounded thread pool maximum pool size in S3AFileSystem TransferManager

[ https://issues.apache.org/jira/browse/HADOOP-16246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814954#comment-16814954 ] Sean Mackrory commented on HADOOP-16246: {quote}The documentation only warns against having a

[jira] [Comment Edited] (HADOOP-16210) Update guava to 27.0-jre in hadoop-project trunk

[ https://issues.apache.org/jira/browse/HADOOP-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809130#comment-16809130 ] Sean Mackrory edited comment on HADOOP-16210 at 4/3/19 7:21 PM:

[jira] [Commented] (HADOOP-16210) Update guava to 27.0-jre in hadoop-project trunk

[ https://issues.apache.org/jira/browse/HADOOP-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809130#comment-16809130 ] Sean Mackrory commented on HADOOP-16210: {quote}-1 javac 19m 7s root generated 15 new

[jira] [Commented] (HADOOP-16210) Update guava to 27.0-jre in hadoop-project trunk

[ https://issues.apache.org/jira/browse/HADOOP-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16809125#comment-16809125 ] Sean Mackrory commented on HADOOP-16210: The failure is the libprotoc version mismatch I

[jira] [Commented] (HADOOP-16210) Update guava to 27.0-jre in hadoop-project trunk

[ https://issues.apache.org/jira/browse/HADOOP-16210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807140#comment-16807140 ] Sean Mackrory commented on HADOOP-16210: Beyond the findbugs issues, I'm supportive of this

[jira] [Commented] (HADOOP-15625) S3A input stream to use etags to detect changed source files

[ https://issues.apache.org/jira/browse/HADOOP-15625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775467#comment-16775467 ] Sean Mackrory commented on HADOOP-15625: Just as a heads up for anyone else following along,

[jira] [Commented] (HADOOP-15999) [s3a] Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16774397#comment-16774397 ] Sean Mackrory commented on HADOOP-15999: FWIW I'm not seeing that test failure, but can't dig

[jira] [Commented] (HADOOP-16101) Use lighter-weight alternatives to innerGetFileStatus where possible

[ https://issues.apache.org/jira/browse/HADOOP-16101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763826#comment-16763826 ] Sean Mackrory commented on HADOOP-16101: The other detail here is that we don't think we need

[jira] [Commented] (HADOOP-15999) [s3a] Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763800#comment-16763800 ] Sean Mackrory commented on HADOOP-15999: +1 on the patch. I filed HADOOP-15619 to make sure we

[jira] [Created] (HADOOP-16101) Use lighter-weight alternatives to innerGetFileStatus where possible

Sean Mackrory created HADOOP-16101: -- Summary: Use lighter-weight alternatives to innerGetFileStatus where possible Key: HADOOP-16101 URL: https://issues.apache.org/jira/browse/HADOOP-16101 Project:

[jira] [Commented] (HADOOP-15582) Document ABFS

[ https://issues.apache.org/jira/browse/HADOOP-15582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16761081#comment-16761081 ] Sean Mackrory commented on HADOOP-15582: I can probably take care of this next week. >

[jira] [Commented] (HADOOP-16085) S3Guard: use object version to protect against inconsistent read after replace/overwrite

[ https://issues.apache.org/jira/browse/HADOOP-16085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758726#comment-16758726 ] Sean Mackrory commented on HADOOP-16085: {quote}object version can be up to 1024

[jira] [Commented] (HADOOP-16085) S3Guard: use object version to protect against inconsistent read after replace/overwrite

[ https://issues.apache.org/jira/browse/HADOOP-16085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758672#comment-16758672 ] Sean Mackrory commented on HADOOP-16085: Thanks for submitting a patch [~ben.roling]. Haven't

[jira] [Commented] (HADOOP-16041) UserAgent string for ABFS

[ https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755525#comment-16755525 ] Sean Mackrory commented on HADOOP-16041: Committed. Confirmed, for everyone's reference, that

[jira] [Comment Edited] (HADOOP-16041) UserAgent string for ABFS

[ https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755439#comment-16755439 ] Sean Mackrory edited comment on HADOOP-16041 at 1/29/19 10:39 PM: -- +1.

[jira] [Commented] (HADOOP-16041) UserAgent string for ABFS

[ https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16755439#comment-16755439 ] Sean Mackrory commented on HADOOP-16041: +1. Will commit. > UserAgent string for ABFS >

[jira] [Commented] (HADOOP-16041) UserAgent string for ABFS

[ https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752888#comment-16752888 ] Sean Mackrory commented on HADOOP-16041: Looks pretty good to me. Test failure is unrelated and

[jira] [Commented] (HADOOP-15999) [s3a] Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16742638#comment-16742638 ] Sean Mackrory commented on HADOOP-15999: After a preliminary review I think this looks pretty

[jira] [Commented] (HADOOP-16041) UserAgent string for ABFS

[ https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16740666#comment-16740666 ] Sean Mackrory commented on HADOOP-16041: In the case of CDH (and I believe Hortonworks /

[jira] [Commented] (HADOOP-16041) UserAgent string for ABFS

[ https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739970#comment-16739970 ] Sean Mackrory commented on HADOOP-16041: {quote}As/when a successor to htrace is added, making

[jira] [Commented] (HADOOP-16041) UserAgent string for ABFS

[ https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739969#comment-16739969 ] Sean Mackrory commented on HADOOP-16041: {quote}Partner Service{quote} To be clear, that's not

[jira] [Comment Edited] (HADOOP-16041) UserAgent string for ABFS

[ https://issues.apache.org/jira/browse/HADOOP-16041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739969#comment-16739969 ] Sean Mackrory edited comment on HADOOP-16041 at 1/11/19 2:49 AM: -

[jira] [Updated] (HADOOP-16027) [DOC] Effective use of FS instances during S3A integration tests

[ https://issues.apache.org/jira/browse/HADOOP-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-16027: --- Resolution: Fixed Fix Version/s: 3.3.0 Status: Resolved (was: Patch

[jira] [Commented] (HADOOP-16027) [DOC] Effective use of FS instances during S3A integration tests

[ https://issues.apache.org/jira/browse/HADOOP-16027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16738490#comment-16738490 ] Sean Mackrory commented on HADOOP-16027: +1, committed. Nit: added the empty lines between what

[jira] [Updated] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15860: --- Component/s: (was: fs/adl) fs/azure > ABFS: Throw

[jira] [Updated] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15860: --- Resolution: Fixed Fix Version/s: 3.3.0 Status: Resolved (was: Patch

[jira] [Comment Edited] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732191#comment-16732191 ] Sean Mackrory edited comment on HADOOP-15860 at 1/2/19 4:19 PM: +1

[jira] [Commented] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732191#comment-16732191 ] Sean Mackrory commented on HADOOP-15860: +1 (although nit: I added whitespace before {'s where

[jira] [Commented] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16732172#comment-16732172 ] Sean Mackrory commented on HADOOP-15819: I wouldn't have thought so as I think you have to go

[jira] [Commented] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16730004#comment-16730004 ] Sean Mackrory commented on HADOOP-15860: So the issue isn't that path is null, the issue is

[jira] [Resolved] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory resolved HADOOP-15819. Resolution: Fixed > S3A integration test failures: FileSystem is closed! - without

[jira] [Commented] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729682#comment-16729682 ] Sean Mackrory commented on HADOOP-15819: Committed. Thank you for the excellent work here

[jira] [Commented] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729681#comment-16729681 ] Sean Mackrory commented on HADOOP-15860: Cancel that - many tests fail. Need to add a check

[jira] [Commented] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16729291#comment-16729291 ] Sean Mackrory commented on HADOOP-15860: +1, will commit. > ABFS: Throw

[jira] [Commented] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725544#comment-16725544 ] Sean Mackrory commented on HADOOP-15819: Ah - FS.key not being set is the piece I was missing.

[jira] [Comment Edited] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725538#comment-16725538 ] Sean Mackrory edited comment on HADOOP-15860 at 12/20/18 2:59 AM: -- So

[jira] [Commented] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725538#comment-16725538 ] Sean Mackrory commented on HADOOP-15860: So there's a checkstyle issue to fix (space before the

[jira] [Commented] (HADOOP-15819) S3A integration test failures: FileSystem is closed! - without parallel test run

[ https://issues.apache.org/jira/browse/HADOOP-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16724301#comment-16724301 ] Sean Mackrory commented on HADOOP-15819: The only failure I see with this patch is the

[jira] [Comment Edited] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721703#comment-16721703 ] Sean Mackrory edited comment on HADOOP-15860 at 12/14/18 7:30 PM: --

[jira] [Commented] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16721703#comment-16721703 ] Sean Mackrory commented on HADOOP-15860: Also instead of just catching the exceptions, we

[jira] [Commented] (HADOOP-15860) ABFS: Throw IllegalArgumentException when Directory/File name ends with a period(.)

[ https://issues.apache.org/jira/browse/HADOOP-15860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16720899#comment-16720899 ] Sean Mackrory commented on HADOOP-15860: Thanks for the patch [~shwetayakkali]. For the most

[jira] [Comment Edited] (HADOOP-15999) [s3a] Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719468#comment-16719468 ] Sean Mackrory edited comment on HADOOP-15999 at 12/12/18 9:35 PM: --

[jira] [Commented] (HADOOP-15999) [s3a] Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719468#comment-16719468 ] Sean Mackrory commented on HADOOP-15999: {quote}We might just want to make that configurable

[jira] [Updated] (HADOOP-15988) Should be able to set empty directory flag to TRUE in DynamoDBMetadataStore#innerGet when using authoritative directory listings

[ https://issues.apache.org/jira/browse/HADOOP-15988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15988: --- Resolution: Fixed Fix Version/s: 3.3.0 Status: Resolved (was: Patch

[jira] [Commented] (HADOOP-15428) s3guard bucket-info will create s3guard table if FS is set to do this automatically

[ https://issues.apache.org/jira/browse/HADOOP-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719117#comment-16719117 ] Sean Mackrory commented on HADOOP-15428: Yeah that's more direct. Tweaked it a bit and updated.

[jira] [Updated] (HADOOP-15428) s3guard bucket-info will create s3guard table if FS is set to do this automatically

[ https://issues.apache.org/jira/browse/HADOOP-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15428: --- Resolution: Fixed Status: Resolved (was: Patch Available) > s3guard bucket-info

[jira] [Updated] (HADOOP-15428) s3guard bucket-info will create s3guard table if FS is set to do this automatically

[ https://issues.apache.org/jira/browse/HADOOP-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15428: --- Release Note: If -unguarded flag is passed to `hadoop s3guard bucket-info`, it will now

[jira] [Updated] (HADOOP-15999) [s3a] Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15999: --- Attachment: out-of-band-operations.patch > [s3a] Better support for out-of-band operations

[jira] [Resolved] (HADOOP-15841) ABFS: change createRemoteFileSystemDuringInitialization default to true

[ https://issues.apache.org/jira/browse/HADOOP-15841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory resolved HADOOP-15841. Resolution: Won't Fix > ABFS: change createRemoteFileSystemDuringInitialization default

[jira] [Commented] (HADOOP-15999) [s3a] Better support for out-of-band operations

[ https://issues.apache.org/jira/browse/HADOOP-15999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718241#comment-16718241 ] Sean Mackrory commented on HADOOP-15999: Attaching a test that illustrates some of the nuances

[jira] [Created] (HADOOP-15999) [s3a] Better support for out-of-band operations

Sean Mackrory created HADOOP-15999: -- Summary: [s3a] Better support for out-of-band operations Key: HADOOP-15999 URL: https://issues.apache.org/jira/browse/HADOOP-15999 Project: Hadoop Common

[jira] [Updated] (HADOOP-15845) s3guard init and destroy command will create/destroy tables if ddb.table & region are set

[ https://issues.apache.org/jira/browse/HADOOP-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15845: --- Resolution: Fixed Status: Resolved (was: Patch Available) > s3guard init and

[jira] [Updated] (HADOOP-15987) ITestDynamoDBMetadataStore should check if test ddb table set properly before initializing the test

[ https://issues.apache.org/jira/browse/HADOOP-15987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15987: --- Resolution: Fixed Status: Resolved (was: Patch Available) Committed. Not worth

[jira] [Updated] (HADOOP-15845) s3guard init and destroy command will create/destroy tables if ddb.table & region are set

[ https://issues.apache.org/jira/browse/HADOOP-15845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Mackrory updated HADOOP-15845: --- Release Note: `hadoop s3guard destroy` and `hadoop s3guard init` now require a

[jira] [Commented] (HADOOP-15988) Should be able to set empty directory flag to TRUE in DynamoDBMetadataStore#innerGet when using authoritative directory listings

[ https://issues.apache.org/jira/browse/HADOOP-15988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16715805#comment-16715805 ] Sean Mackrory commented on HADOOP-15988: Good stuff. A few nits: * Can you clean up the

  1   2   3   4   5   6   7   8   9   10   >