[
https://issues.apache.org/jira/browse/HBASE-13094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15425313#comment-15425313
]
Lars Hofhansl commented on HBASE-13094:
---------------------------------------
Yep. Or we come up with an API that enforces this structurally.
For example we could adapt #4 to add an API to Get/Scan that instead only
controls whether the Filter.filterKeyValue (set as before with setFilter) is
evaluated either pre or post deletes. The effect would be the same as the patch
I have, but with a clean no-magic API. (Although that almost leads me back to
the approach of indicating the "pre-postness" in the Filter itself). Or one
could think about option #3 above.
> Consider Filters that are evaluated before deletes and see delete markers
> -------------------------------------------------------------------------
>
> Key: HBASE-13094
> URL: https://issues.apache.org/jira/browse/HBASE-13094
> Project: HBase
> Issue Type: Brainstorming
> Components: regionserver, Scanners
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Attachments: 13094-0.98.txt
>
>
> That would be good for full control filtering of all cells, such as needed
> for some transaction implementations.
> [~ghelmling]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
