You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/12/03 04:58:58 UTC

[jira] [Commented] (HBASE-17234) Allow alternate Readers/Writers; currently hardcoded

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

stack commented on HBASE-17234:
-------------------------------

Chatting w/ [~mbertozzi] today, he makes a good point. Factory for Writers make sense. At read time, no. At read time, factory makes no sense. At read time you need to peek at the file to see what Reader implementation to use. This means that whatever the Writer, they always write a trailer aways of the same format. A parse of the format figures which Reader impl to use.

> Allow alternate Readers/Writers; currently hardcoded
> ----------------------------------------------------
>
>                 Key: HBASE-17234
>                 URL: https://issues.apache.org/jira/browse/HBASE-17234
>             Project: HBase
>          Issue Type: Task
>          Components: io
>            Reporter: stack
>         Attachments: HBASE-17234.master.001.patch
>
>
> Allow alternate HFile Reader and Writers. For Writers, we have WriterFactory so you'd think it possible to supply a different Writer but in actuality, WriterFactory is hardcoded.
> Read side does something else altogether complicated by fact that Reader presumes trailer and that it has to take a Stream.
> Yeah, expecting someone would provide their own Reader/Writer is a little unexpected.... but....



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)