hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18811) Introduce the limited private to filter
Date Sun, 17 Sep 2017 16:29:02 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169340#comment-16169340

Chia-Ping Tsai commented on HBASE-18811:

We should not expose the inner class/logic to Public Client. Right? All methods in observer
are embedded in our server-side logic, so we make them IA.LimitedPrivate. All methods in filters
are also embedded in our server-side logic, but we expose them as Public Client. The BC we
need to guarantee is that the built-in filters must works as before (class name and arguments),
even if we make drastic changes to it's impl. 

> Introduce the limited private to filter
> ---------------------------------------
>                 Key: HBASE-18811
>                 URL: https://issues.apache.org/jira/browse/HBASE-18811
>             Project: HBase
>          Issue Type: Task
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>             Fix For: 2.0.0-alpha-4
>         Attachments: HBASE-18811.v0.patch
> We have many powerful callback functions to help user to build amazing application/services.
The most of functions are declared as IA.LimitedPrivate excluding the filters. As i see it,
the IA.LimitedPrivate will make the improvement of filter more flexible. Also, we can introduce
more server-side components to filters. In conclusion, we should consider adding the limited
private level for filter.

This message was sent by Atlassian JIRA

View raw message