[
https://issues.apache.org/jira/browse/FLINK-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126027#comment-15126027
]
PJ Van Aeken commented on FLINK-2055:
-------------------------------------
For Flink batch, I think HFileOutputFormat2 is a valid approach, but so is the
TableOutputFormat. Possibly we could offer both, depending on the consistency
needs of the user. For Flink streaming however, right now we are suggesting to
also use TableOutputformat. I would propose we use the non-buffered HBase
native client instead (no output format, just the classes from the client
package). In a one-at-a-time processing scenario, buffering the writes in the
BufferedMutator seems like an unnecessary delay. Or it should at least be an
optional choice. Right now, the milliseconds we are defining seem to be a bit
redundant, since the BufferedMutator uses its own heuristics to determine when
to flush.
> 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)
