You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2019/09/29 10:14:00 UTC

[jira] [Created] (HBASE-23093) Avoid Optional Anti-Patterns

Viraj Jasani created HBASE-23093:
------------------------------------

             Summary: Avoid Optional Anti-Patterns
                 Key: HBASE-23093
                 URL: https://issues.apache.org/jira/browse/HBASE-23093
             Project: HBase
          Issue Type: Improvement
    Affects Versions: 3.0.0, 2.3.0, 1.6.0
            Reporter: Viraj Jasani
            Assignee: Viraj Jasani


Optional should be used as a return type only. It's a neat solution for handling data that might  not be present. We should avoid using Optional Anti-Patterns i.e. using it as a field or parameter type due to these reasons:

1. Using Optional parameters causing conditional logic inside the methods is not productive.

2. Packing an argument in an Optional is suboptimal for the compiler and does an unnecessary wrapping.



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