[
https://issues.apache.org/jira/browse/RATIS-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15948472#comment-15948472
]
Hugo Louro commented on RATIS-8:
--------------------------------
[~enis] [~jingzhao] can you pleas review, thanks.
If we really want to avoid Optional at all cost, the only alternatives would be
to return null (not recommended), or to throw a checked exception in case of
invalid values, and let the client code handle it.
> Avoid using Optional for data fields in TransactionContext
> ----------------------------------------------------------
>
> Key: RATIS-8
> URL: https://issues.apache.org/jira/browse/RATIS-8
> Project: Ratis
> Issue Type: Improvement
> Reporter: Jing Zhao
> Assignee: Hugo Louro
> Attachments: RATIS-8.patch
>
>
> It's usually not recommended to use {{Optional}} as class fields. Let's use
> this jira to revisit the {{Optional}} usage in {{TransactionContext}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
