[
https://issues.apache.org/jira/browse/FLINK-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15119821#comment-15119821
]
PJ Van Aeken commented on FLINK-2055:
-------------------------------------
It appears I was wrong in my first comment.
HBase provides two output formats, and the TableOutputFormat (currently used in
Flink) still passes through the write path and thus the WAL and memstore,
unlike its bulk counterpart HFileOutputFormat2. That being said, the
TableOutputFormat does use BufferedMutator, which appearantly buffers the
requests client side and sends them across the wire in small batches. This
still has an inherent delay which is still completely different from the
milliseconds defined in the Flink API, and it can easily be avoided by using
the native HBase client API. Thoughts?
> Implement Streaming HBaseSink
> -----------------------------
>
> Key: FLINK-2055
> URL: https://issues.apache.org/jira/browse/FLINK-2055
> Project: Flink
> Issue Type: New Feature
> Components: Streaming, Streaming Connectors
> Affects Versions: 0.9
> Reporter: Robert Metzger
> Assignee: Hilmi Yildirim
>
> As per :
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Write-Stream-to-HBase-td1300.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
