Bug #71277 Mysql Applier track log Pos
Submitted: 2 Jan 2014 17:19 Modified: 5 Mar 2014 17:37
Reporter: Nijjwol Lamsal Email Updates:
Status: Closed Impact on me:
Category:MySQL Utilities: Binlog Events Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[2 Jan 2014 17:19] Nijjwol Lamsal
Mysql-Hadoop-Applier doesn't keep track of the last Log Position, so when it needs a restart or fails, the log file is re-read rather than from the last Log Pos.
This is a key feature to consider if implementing the Applier. 


How to repeat:
Restart mysql-hadoop-applier.
[7 Jan 2014 15:15] Michael Albert
The "offset" parameter to sync_connect_and_authenticate() is unused and presumably should be removed.

This is relevant because the "offset" is apparently intended to be the offset into the current "bin log" file, but that is being handled elsewhere (start_binlog_dump()), and in any case the offset is not of much use without the "bin log" file name (which is not being passed to sync_connect_and_authenticate()).

[5 Mar 2014 17:37] Paul DuBois
Fixed in 0.2.0.
Not a released product (and no docs for it) yet. No changelog entry needed.