Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IGNITE-13596 Flag to distinguish DataRecord on primary and backup added #8904

Merged
merged 3 commits into from
Mar 25, 2021

Conversation

nizhikov
Copy link
Contributor

@nizhikov nizhikov commented Mar 19, 2021

This PR introduces primary flag for WAL DataRecord.
Flag will be used in Ignite CDC application to distinguish changes that happened on primary and backup.

The Contribution Checklist

  • There is a single JIRA ticket related to the pull request.
  • The web-link to the pull request is attached to the JIRA ticket.
  • The JIRA ticket has the Patch Available state.
  • The pull request body describes changes that have been made.
    The description explains WHAT and WHY was made instead of HOW.
  • The pull request title is treated as the final commit message.
    The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue.
  • A reviewer has been mentioned through the JIRA comments
    (see the Maintainers list)
  • The pull request has been checked by the Teamcity Bot and
    the green visa attached to the JIRA ticket (see TC.Bot: Check PR)

Notes

If you need any help, please email dev@ignite.apache.org or ask anу advice on http://asf.slack.com #ignite channel.

@nizhikov
Copy link
Contributor Author

Hello, @Mmuzaf , @NSAmelchev

Can you, please, take a look at my changes?

IGNITE-13596 Flag in DataRecord to differentiate records on primary and backup nodes

IGNITE-13596 Flag in DataRecord to differentiate records on primary and backup nodes

IGNITE-13596 Flag in DataRecord to differentiate records on primary and backup nodes
@nizhikov nizhikov merged commit db8bb81 into apache:ignite-cdc Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants