You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2019/05/08 17:16:00 UTC

[jira] [Commented] (HBASE-22385) Consider "programmatic" HFiles

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

Lars Hofhansl commented on HBASE-22385:
---------------------------------------

[~jisaac], what we chatted about.

> Consider "programmatic" HFiles
> ------------------------------
>
>                 Key: HBASE-22385
>                 URL: https://issues.apache.org/jira/browse/HBASE-22385
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Lars Hofhansl
>            Priority: Major
>
> For various use case (among other there is mass deletes) it would be great if HBase had a mechanism for programmatic HFiles. I.e. HFiles (with HFileScanner and Reader) that produce KeyValue just like any other old HFile, but the key values produced are generated or produced by some other means rather than being physically read from some storage medium.
> In fact this could be a generalization for the various HFiles we have: (Normal) HFiles, HFileLinks, HalfStoreFiles, etc.
> A simple way could be to allow for storing a classname into the HFile. Upon reading the HFile HBase would instantiate an instance of that class and that instance is responsible for all further interaction with that HFile. For normal HFiles it would just be the normal HFileReader.
> (Remember this is Brainstorming)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)