Got it :)
Thanks
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
Interval - Yes.
TwoPhaseCommitSinkFunction - yes, but it depends how will you implement your
“Transaction” class, it wouldn’t make a lot of sense, but you could store
events inside the transaction “pojo”.
Piotrek
> On Oct 4, 2017, at 12:45 PM, nragon
> wrote:
>
> checkpointing interval ~=
checkpointing interval ~= transactions are being committed on each Flink
checkpoint
So, if i set my checkpoint interval to 1ms, every 1ms there will be
a commit, right?
If I understoop correctly, TwoPhaseCommitSinkFunction stores transactions
into it's state as for GenericWriteAheadSink it
What do you mean by "This always depends on checkpointing interval right?”?
In TwoPhaseCommitSinkFunction, transactions are being committed on each Flink
checkpoint. I guess same applies to GenericWriteAheadSink. The first one just
commits/pre-commits the data on checkpoint, second rewrites them
Thanks for you opinion on this.
TwoPhaseCommitSinkFunction would probably be the best solution overall.
Using this with something like Phoenix or Tephra would probably work.
This always depends on checkpointing interval right?
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.
Hi,
Do you mean buffer on state and you want to achieve exactly-once HBase sink? If
so keep in mind that you will need some kind of transactions support in HBase
to make it 100% reliable.
Without transactions, buffering messages on state only reduces chance of
duplicated records. How much “red
Anyone? :)
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
