[
https://issues.apache.org/jira/browse/HDFS-9134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905935#comment-14905935
]
Haohui Mai commented on HDFS-9134:
----------------------------------
{code}
+ @Deprecated
+ long LEASE_SOFTLIMIT_PERIOD = HdfsConstants.LEASE_SOFTLIMIT_PERIOD;
+ @Deprecated
+ long LEASE_HARDLIMIT_PERIOD = HdfsConstants.LEASE_HARDLIMIT_PERIOD;
{code}
These two constants are mainly used in server side. It's better to not
deprecate them but just leave them as copies of the values from
{{HdfsConstants}}.
+1 once addressed.
> Move LEASE_{SOFTLIMIT,HARDLIMIT}_PERIOD constants from HdfsServerConstants to
> HdfsConstants
> -------------------------------------------------------------------------------------------
>
> Key: HDFS-9134
> URL: https://issues.apache.org/jira/browse/HDFS-9134
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Mingliang Liu
> Assignee: Mingliang Liu
> Attachments: HDFS-9134.000.patch
>
>
> As these two constants are used by {{DFSClient}} which is to be moved to
> {{hadoop-hdfs-client}} module (see [HDFS-8053]), we consider these two
> constants should be moved to {{hadoop-hdfs-client}} module. A good place is
> {{HdfsConstants}} which contains for both server and client side constants.
> This jiras tracks the effort of moving {{LEASE\_SOFTLIMIT\_PERIOD}} and
> {{LEASE_HARDLIMIT\_PERIOD}} constants from server side class
> {{HdfsServerConstants}} to client side class {{HdfsConstants}}. We'd better
> mark these keys as _@Deprecated_ for a while before totally deleting them, in
> case we break dependent code without being aware of it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)