[
https://issues.apache.org/jira/browse/FLINK-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126221#comment-15126221
]
ramkrishna.s.vasudevan commented on FLINK-2055:
-----------------------------------------------
Thanks for your inputs.
For the batch case Flink uses TableOutputFormat
{code}
this.table = new HTable(this.conf, tableName);
this.table.setAutoFlush(false, true);
LOG.info("Created table instance for " + tableName);
{code}
The above code explicitly sets AutoFlush to false. So there is that buffering
mechanism.
But for the Stream approach case - Atleast in the HBaseWriteStreamExample we
only do this
{code}
table = new HTable(conf, "flinkExample");
{code}
And call table.put(put). So here there is no buffering and every mutation is
sent immediately to the server. Are you finding something else here? Let me
know if am missing something here.
> 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)
