Konstantin Shvachko commented on HDFS-13399:

??We are allowed to break compatibility at minor releases.??

Just to make sure we are on the same page. Hadoop *requires* backward 
compatibility for minor releases. So please NO breaking! As I look at it we 
cannot break compatibility ever: we can only add new methods, parameters, etc. 
and deprecate old ones.
Package-private is not a part of API, so it can change.

??Should we consider creating client and server side configuration for enabling 
/ disabling AlignmentContext processing???

I don't think we need a config parameter for that.  This is controlled by the 
code. If you pass an {{AlignmentContext}} as non null parameter it is used. M/R 
clients for example wont need it, so null will be used by default.

> Make Client field AlignmentContext non-static.
> ----------------------------------------------
>                 Key: HDFS-13399
>                 URL: https://issues.apache.org/jira/browse/HDFS-13399
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: HDFS-12943
>            Reporter: Plamen Jeliazkov
>            Assignee: Plamen Jeliazkov
>            Priority: Major
>         Attachments: HDFS-13399-HDFS-12943.000.patch, 
> HDFS-13399-HDFS-12943.001.patch
> In HDFS-12977, DFSClient's constructor was altered to make use of a new 
> static method in Client that allowed one to set an AlignmentContext. This 
> work is to remove that static field and make each DFSClient pass it's 
> AlignmentContext down to the proxy Call level.

This message was sent by Atlassian JIRA

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

Reply via email to