[
https://issues.apache.org/jira/browse/HBASE-18878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189226#comment-16189226
]
Duo Zhang commented on HBASE-18878:
-----------------------------------
Oh, just see your first comment. If we want to hide some methods, I prefer
using an interface. I think you can open a new jira to do this first.
For the optional change I need to consider it again. In my original design, I
tend to use Optional for all possible null parameters and return values. I
think this is really useful as if an parameter or return value is not an
Optional then you must provide it or do not need to do null check. For now
either you need to dig deeply to see if it could be null, or you need null
check everywhere which makes the code ugly...
Give me some time. I need to rethink that if method overload can solve the
problem.
Thanks.
> Use Optional instead of Nullable annotation in ObserverContext to better
> describe that the caller may not be presented
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-18878
> URL: https://issues.apache.org/jira/browse/HBASE-18878
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0-alpha-4
>
> Attachments: HBASE-18878.master.001.patch, HBASE-18878.patch,
> HBASE-18878-v1.patch
>
>
> I've already done lots of Nullable to Optional change when purging the
> interfaces for CP. This is a big one so open a separated issue for it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
