hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6427) Pluggable compaction policies via coprocessors
Date Thu, 26 Jul 2012 18:07:35 GMT

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

Andrew Purtell commented on HBASE-6427:
---------------------------------------

Or use polymorphism?

{noformat}
+  public InternalScanner preFlush(final ObserverContext<RegionCoprocessorEnvironment>
c,
+      Store store, KeyValueScanner scanner) throws IOException;
+
+  @Deprecated
   public void preFlush(ObserverContext<RegionCoprocessorEnvironment> e) throws IOException;
{noformat}

{noformat}
+  public InternalScanner preCompact(final ObserverContext<RegionCoprocessorEnvironment>
c,
+      Store store, List<? extends KeyValueScanner> scanners, ScanType scanType, long
earliestPutTs)
+      throws IOException;
+
+  @Deprecated
   public void preCompact(ObserverContext<RegionCoprocessorEnvironment> e
...
{noformat}

                
> Pluggable compaction policies via coprocessors
> ----------------------------------------------
>
>                 Key: HBASE-6427
>                 URL: https://issues.apache.org/jira/browse/HBASE-6427
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Lars Hofhansl
>            Priority: Minor
>         Attachments: 6427-notReady.txt
>
>
> When implementing higher level stores on top of HBase it is necessary to allow dynamic
control over how long KVs must be kept around.
> Semi-static config options for ColumnFamilies (# of version or TTL) is not sufficient.
> The simplest way to achieve this is to have a pluggable class to determine the smallestReadpoint
for Region. That way outside code can control what KVs to retain.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message