[
https://issues.apache.org/jira/browse/HBASE-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16169960#comment-16169960
]
Abhishek Singh Chouhan commented on HBASE-18811:
------------------------------------------------
Since filters are something that is directly used in the most basic client APIs
scans/gets shouldn't we atleast have an interface (eg. filter which is
currently an abstract class) that should be IA.Public and then we can keep the
implementations LimitedPrivate? That way we stick to the basic behavioral
guarantees and api contract and can change the implementations internally as
per our needs on the server side.
> 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)
