[ 
https://issues.apache.org/jira/browse/HADOOP-17921?focusedWorklogId=656761&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-656761
 ]

ASF GitHub Bot logged work on HADOOP-17921:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Sep/21 20:16
            Start Date: 28/Sep/21 20:16
    Worklog Time Spent: 10m 
      Work Description: cnauroth commented on pull request #3463:
URL: https://github.com/apache/hadoop/pull/3463#issuecomment-928096868


   One other consideration is the behavior as it stands now for HDFS clusters 
that have disabled xattrs with `dfs.namenode.xattrs.enabled=false`.  (The 
default for this property is `true` in recent versions, and with a lot of 
people wanting at-rest encryption, it's become less common to set to `false`.)
   
   In current behavior, the NameNode will throw an `IOException` (not a more 
specific subclass) that propagates to the client.  DistCp will catch that and 
throw its own `XAttrsNotSupportedException`.
   
   With this patch, the NameNode still throws `IOException`, but now DistCp 
propagates that straight to the caller instead of throwing 
`XAttrsNotSupportedException`.  There is a risk that this could cause subtle 
behavioral differences for higher-layer tooling (Oozie? Airflow?) that 
coordinates DistCp jobs.
   
   I'm not certain there is a problem, but I agree with @steveloughran that 
there is reason to be cautious.  It's also difficult to anticipate if custom 
`FileSystem` implementers have overridden and thrown a different exception, 
despite the base class providing `UnsupportedOperationException` out of the box.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 656761)
    Time Spent: 1.5h  (was: 1h 20m)

> DistCp derives if XAttr is supported wrongly
> --------------------------------------------
>
>                 Key: HADOOP-17921
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17921
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Pravin Sinha
>            Assignee: Pravin Sinha
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {color:#0033b3}public static void 
> {color}{color:#00627a}checkFileSystemXAttrSupport{color}({color:#000000}FileSystem
>  {color}fs)
>  {color:#0033b3}throws {color}{color:#000000}XAttrsNotSupportedException 
> {color}{
>  {color:#0033b3}try {color}{
>  fs.getXAttrs({color:#0033b3}new 
> {color}Path({color:#000000}Path{color}.{color:#871094}SEPARATOR{color}));
>  } {color:#0033b3}catch {color}({color:#000000}Exception {color}e) {
>  {color:#0033b3}throw new 
> {color}XAttrsNotSupportedException({color:#067d17}"XAttrs not supported for 
> file system: "
> {color} + fs.getUri());
>  }
> }
> IOExecption will also be treated as if Xattr is not supported, which would be 
> wrong.
>  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to