hbase-issues mailing list archives

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

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

Dave Latham commented on HBASE-18811:
-------------------------------------

The idea here is that Filters should no longer be part of the client API, but move to being
internals, like coprocessors?
As one HBase user, we'd be sorry to see this.  We do have custom filters deployed, but have
shied away from coprocessors due to the lesser degree of stability and higher degree of complexity.
 

I think a discussion on the dev list would probably be good before making this change.

> 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