Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / eventuate-foundation/eventuate-cdc issues and pull requests
#95 - MySqlBinaryLogClientOffsetStoreTest does not need to use leadership
Issue -
State: open - Opened by cer almost 4 years ago
#95 - MySqlBinaryLogClientOffsetStoreTest does not need to use leadership
Issue -
State: open - Opened by cer almost 4 years ago
#94 - (mysql binlog client) Ingnore offsets of binlog events not related to eventuate tables
Issue -
State: open - Opened by dartartem almost 4 years ago
#94 - (mysql binlog client) Ingnore offsets of binlog events not related to eventuate tables
Issue -
State: open - Opened by dartartem almost 4 years ago
#94 - (mysql binlog client) Ingnore offsets of binlog events not related to eventuate tables
Issue -
State: open - Opened by dartartem almost 4 years ago
#94 - (mysql binlog client) Ingnore offsets of binlog events not related to eventuate tables
Issue -
State: open - Opened by dartartem almost 4 years ago
#94 - (mysql binlog client) Ingnore offsets of binlog events not related to eventuate tables
Issue -
State: open - Opened by dartartem almost 4 years ago
#94 - (mysql binlog client) Ingnore offsets of binlog events not related to eventuate tables
Issue -
State: open - Opened by dartartem almost 4 years ago
#94 - (mysql binlog client) Ingnore offsets of binlog events not related to eventuate tables
Issue -
State: open - Opened by dartartem almost 4 years ago
#94 - (mysql binlog client) Ingnore offsets of binlog events not related to eventuate tables
Issue -
State: open - Opened by dartartem almost 4 years ago
#93 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash. Fixed exception handling in OffsetProcessor. Fixed related tests.
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#93 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash. Fixed exception handling in OffsetProcessor. Fixed related tests.
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#93 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash. Fixed exception handling in OffsetProcessor. Fixed related tests.
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#93 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash. Fixed exception handling in OffsetProcessor. Fixed related tests.
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#93 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash. Fixed exception handling in OffsetProcessor. Fixed related tests.
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#93 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash. Fixed exception handling in OffsetProcessor. Fixed related tests.
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#93 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash. Fixed exception handling in OffsetProcessor. Fixed related tests.
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#93 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash. Fixed exception handling in OffsetProcessor. Fixed related tests.
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#92 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash
Issue -
State: open - Opened by dartartem almost 4 years ago
- 6 comments
#92 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash
Issue -
State: open - Opened by dartartem almost 4 years ago
- 6 comments
#92 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash
Issue -
State: open - Opened by dartartem almost 4 years ago
- 6 comments
#92 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash
Issue -
State: open - Opened by dartartem almost 4 years ago
- 6 comments
#92 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash
Issue -
State: open - Opened by dartartem almost 4 years ago
- 6 comments
#92 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash
Issue -
State: open - Opened by dartartem almost 4 years ago
- 6 comments
#92 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash
Issue -
State: open - Opened by dartartem almost 4 years ago
- 6 comments
#92 - (mysql binlog client) Is it sufficient to save offsets only of insert/update events to properly recover on crash
Issue -
State: open - Opened by dartartem almost 4 years ago
- 6 comments
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#91 - UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#90 - Should the MySqlBinaryLogClientLifecycleListener.onCommunicationFailure()/onEventDeserializationFailure() stop event processing? stop the processing of messages if
Issue -
State: open - Opened by cer almost 4 years ago
#90 - Should the MySqlBinaryLogClientLifecycleListener.onCommunicationFailure()/onEventDeserializationFailure() stop event processing? stop the processing of messages if
Issue -
State: open - Opened by cer almost 4 years ago
#90 - Should the MySqlBinaryLogClientLifecycleListener.onCommunicationFailure()/onEventDeserializationFailure() stop event processing? stop the processing of messages if
Issue -
State: open - Opened by cer almost 4 years ago
#90 - Should the MySqlBinaryLogClientLifecycleListener.onCommunicationFailure()/onEventDeserializationFailure() stop event processing? stop the processing of messages if
Issue -
State: open - Opened by cer almost 4 years ago
#90 - Should the MySqlBinaryLogClientLifecycleListener.onCommunicationFailure()/onEventDeserializationFailure() stop event processing? stop the processing of messages if
Issue -
State: open - Opened by cer almost 4 years ago
#90 - Should the MySqlBinaryLogClientLifecycleListener.onCommunicationFailure()/onEventDeserializationFailure() stop event processing? stop the processing of messages if
Issue -
State: open - Opened by cer almost 4 years ago
#90 - Should the MySqlBinaryLogClientLifecycleListener.onCommunicationFailure()/onEventDeserializationFailure() stop event processing? stop the processing of messages if
Issue -
State: open - Opened by cer almost 4 years ago
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#89 - io.eventuate.local.mysql.binlog.UpdateRowsDeserializer.deserializeRow fails with EventDataDeserializationException No TableMapEventData has been found for table id
Issue -
State: open - Opened by dartartem almost 4 years ago
- 9 comments
#88 - Fixed Cdc MySql binlog reader healthcheck
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#88 - Fixed Cdc MySql binlog reader healthcheck
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#88 - Fixed Cdc MySql binlog reader healthcheck
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#88 - Fixed Cdc MySql binlog reader healthcheck
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#88 - Fixed Cdc MySql binlog reader healthcheck
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#88 - Fixed Cdc MySql binlog reader healthcheck
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#88 - Fixed Cdc MySql binlog reader healthcheck
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#88 - Fixed Cdc MySql binlog reader healthcheck
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#87 - CDC doesn't support MySQL 8.0
Issue -
State: open - Opened by huytmb almost 4 years ago
- 1 comment
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#86 - CDC becomes unhealthy because of Reader with id MySqlReader has not received message for 158602 milliseconds"
Issue -
State: open - Opened by cer almost 4 years ago
- 8 comments
#85 - Move HealthCheck logic into the reader classes
Issue -
State: open - Opened by cer almost 4 years ago
#85 - Move HealthCheck logic into the reader classes
Issue -
State: open - Opened by cer almost 4 years ago
#85 - Move HealthCheck logic into the reader classes
Issue -
State: open - Opened by cer almost 4 years ago
#85 - Move HealthCheck logic into the reader classes
Issue -
State: open - Opened by cer almost 4 years ago
#84 - CDC initially reports healthy and then becomes unhealthy
Issue -
State: open - Opened by cer almost 4 years ago
Labels: bug
#84 - CDC initially reports healthy and then becomes unhealthy
Issue -
State: open - Opened by cer almost 4 years ago
Labels: bug
#84 - CDC initially reports healthy and then becomes unhealthy
Issue -
State: open - Opened by cer almost 4 years ago
Labels: bug
#84 - CDC initially reports healthy and then becomes unhealthy
Issue -
State: open - Opened by cer almost 4 years ago
Labels: bug
#84 - CDC initially reports healthy and then becomes unhealthy
Issue -
State: open - Opened by cer almost 4 years ago
Labels: bug
#84 - CDC initially reports healthy and then becomes unhealthy
Issue -
State: open - Opened by cer almost 4 years ago
Labels: bug
#84 - CDC initially reports healthy and then becomes unhealthy
Issue -
State: open - Opened by cer almost 4 years ago
Labels: bug
#84 - CDC initially reports healthy and then becomes unhealthy
Issue -
State: open - Opened by cer almost 4 years ago
Labels: bug
#83 - #80, #81
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#83 - #80, #81
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#83 - #80, #81
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#83 - #80, #81
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#83 - #80, #81
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#83 - #80, #81
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#83 - #80, #81
Pull Request -
State: closed - Opened by dartartem almost 4 years ago
#83 - #80, #81
Pull Request -
State: closed - Opened by dartartem almost 4 years ago