You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "YiSheng Lien (Jira)" <ji...@apache.org> on 2019/09/18 18:56:00 UTC
[jira] [Commented] (HDDS-1738) Add nullable annotation for
OMResponse classes
[ https://issues.apache.org/jira/browse/HDDS-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932753#comment-16932753 ]
YiSheng Lien commented on HDDS-1738:
------------------------------------
Hi [~bharatviswa],
According the description of the issue,
May I know the details of the comment ?
(I think we can't add @nullable annotation for "all" OMResponse,
so maybe the details can help me to solve the issue)
> Add nullable annotation for OMResponse classes
> ----------------------------------------------
>
> Key: HDDS-1738
> URL: https://issues.apache.org/jira/browse/HDDS-1738
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: YiSheng Lien
> Priority: Major
> Labels: newbie
>
> This is to address [~arp] comment.
> A future improvement unrelated to your patch - replace null with Optional. Or at least add [@nullable|https://github.com/nullable] annotation on the parameter.
> Add @nullable for all OMResponse fields, where fields can be null.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org