[jira] [Created] (HADOOP-16682) Remove unnecessary toString()

2019-11-04 Thread Jeetesh Mangwani (Jira) 
Jeetesh Mangwani created HADOOP-16682:
-

 Summary: Remove unnecessary toString()
 Key: HADOOP-16682
 URL: https://issues.apache.org/jira/browse/HADOOP-16682
 Project: Hadoop Common
  Issue Type: Sub-task
Reporter: Jeetesh Mangwani
Assignee: Jeetesh Mangwani


Remove toString() from permission.toString() in the line here: 
https://github.com/apache/hadoop/blob/04a6c095cf6d09b6ad417f1f7b7c64fbfdc9d5e4/hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azurebfs/AzureBlobFileSystemStore.java#L386



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Created] (HADOOP-16681) mvn javadoc:javadoc fails in hadoop-aws

2019-11-04 Thread Xieming Li (Jira) 
Xieming Li created HADOOP-16681:
---

 Summary: mvn javadoc:javadoc fails in hadoop-aws
 Key: HADOOP-16681
 URL: https://issues.apache.org/jira/browse/HADOOP-16681
 Project: Hadoop Common
  Issue Type: Bug
  Components: documentation
Reporter: Xieming Li
Assignee: Xieming Li


mvn javadoc:javadoc fails in hadoop-aws module.

{code}
[ERROR] 
/Users/sri/projects/hadoop-mirror/hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/impl/NetworkBinding.java:117:
 error: semicolon missing
[ERROR]* https://forums.aws.amazon.com/thread.jspa?messageID=796829=0
{code}

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

[jira] [Resolved] (HADOOP-16484) S3A to warn or fail if S3Guard is disabled

2019-11-04 Thread Gabor Bota (Jira) 


 [ 
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

> S3A to warn or fail if S3Guard is disabled
> --
>
> Key: HADOOP-16484
> URL: https://issues.apache.org/jira/browse/HADOOP-16484
> Project: Hadoop Common
>  Issue Type: Sub-task
>  Components: fs/s3
>Affects Versions: 3.2.0
>Reporter: Steve Loughran
>Assignee: Gabor Bota
>Priority: Minor
> Fix For: 3.3.0
>
>
> A seemingly recurrent problem with s3guard is "people who think S3Guard is 
> turned on but really it isn't"
> It's not immediately obvious this is the case, and the fact S3Guard is off 
> tends to surface after some intermittent failure has actually been detected.
> Propose: add a configuration parameter which chooses what to do when an S3A 
> FS is instantiated without S3Guard
> * silent : today; do nothing.
> * status: give s3guard on/off status
> * inform: log FS is instantiated without s3guard
> * warn: Warn that data may be at risk in workflows
> * fail
> deployments could then choose which level of reaction they want. I'd make the 
> default "inform" for now; any on-prem object store deployment should switch 
> to silent, and if you really want strictness, fail is the ultimate option



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org