hbase-issues mailing list archives

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

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

Anoop Sam John commented on HBASE-18811:
----------------------------------------

Filters are used at client end along with Scan/Get right?  WHy to change from Public?  As
per BC rules, the Limited private is less stricter than Public.  So am not getting why we
should reduce the BC agreement of the Filters.  Can u explain pls?

> 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
(v6.4.14#64029)

Mime
View raw message