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

[Backport 0.24] Updates exporter position when skipping if possible #5434

Merged
merged 1 commit into from
Sep 28, 2020

Conversation

npepinpe
Copy link
Member

@npepinpe npepinpe commented Sep 25, 2020

Description

Backport of #5388. A simple cherry-pick where I had to fix a merge conflict in the ExporterDirector.ExporterContainer#updateLastExportedRecordPosition, since 0.24 does not have a metric there (which 0.25 will have).

Related issues

closes #3166

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

  • The changes are backwards compatibility with previous versions
  • If it fixes a bug then PRs are created to backport the fix to the last two minor versions

Testing:

  • There are unit/integration tests that verify all acceptance criterias of the issue
  • New tests are written to ensure backwards compatibility with further versions
  • The behavior is tested manually
  • The impact of the changes is verified by a benchmark

Documentation:

  • The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
  • New content is added to the release announcement

- allows compaction to occur even when an exporter skips all records iff
  it is up to date
- keeps track of last acknowledged and unacknowledged position of
  exporters in ExporterContainer
- when skipping a record (whether for all, or a single exporter), if the
  exporter is up to date (meaning its last acknowledged position is
  greater than or equal to its last unacknowledged position), then
  automatically acknowledge that position
@npepinpe npepinpe requested a review from saig0 September 25, 2020 15:58
@npepinpe npepinpe self-assigned this Sep 25, 2020
@npepinpe npepinpe changed the title Updates exporter position when skipping if possible [Backport 0.24] Updates exporter position when skipping if possible Sep 25, 2020
Copy link
Member

@saig0 saig0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🍪

bors r+

zeebe-bors bot added a commit that referenced this pull request Sep 28, 2020
5434: [Backport 0.24] Updates exporter position when skipping if possible r=saig0 a=npepinpe

## Description

Backport of #5388. A simple cherry-pick where I had to fix a merge conflict in the `ExporterDirector.ExporterContainer#updateLastExportedRecordPosition`, since 0.24 does not have a metric there (which 0.25 will have).

## Related issues

closes #3166

## Definition of Done

_Not all items need to be done depending on the issue and the pull request._

Code changes:
* [x] The changes are backwards compatibility with previous versions
* [x] If it fixes a bug then PRs are created to [backport](https://github.com/zeebe-io/zeebe/compare/stable/0.24...develop?expand=1&template=backport_template.md&title=[Backport%200.24]) the fix to the last two minor versions

Testing:
* [x] There are unit/integration tests that verify all acceptance criterias of the issue
* [ ] New tests are written to ensure backwards compatibility with further versions
* [x] The behavior is tested manually
* [ ] The impact of the changes is verified by a benchmark 

Documentation: 
* [ ] The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
* [ ] New content is added to the [release announcement](https://drive.google.com/drive/u/0/folders/1DTIeswnEEq-NggJ25rm2BsDjcCQpDape)


Co-authored-by: Nicolas Pépin-Perreault <nicolas.pepin-perreault@camunda.com>
@zeebe-bors
Copy link
Contributor

zeebe-bors bot commented Sep 28, 2020

Build failed:

zeebe-bors bot added a commit that referenced this pull request Sep 28, 2020
5435: [Backport 0.23] Updates exporter position when skipping if possible r=saig0 a=npepinpe

## Description

Backport of #5434. A simple cherry-pick of the 0.24 back port to avoid the merge conflict again (see the 0.24 backport issue on this).

## Related issues

closes #3166

## Definition of Done

_Not all items need to be done depending on the issue and the pull request._

Code changes:
* [x] The changes are backwards compatibility with previous versions
* [x] If it fixes a bug then PRs are created to [backport](https://github.com/zeebe-io/zeebe/compare/stable/0.24...develop?expand=1&template=backport_template.md&title=[Backport%200.24]) the fix to the last two minor versions

Testing:
* [x] There are unit/integration tests that verify all acceptance criterias of the issue
* [ ] New tests are written to ensure backwards compatibility with further versions
* [x] The behavior is tested manually
* [ ] The impact of the changes is verified by a benchmark 

Documentation: 
* [ ] The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
* [ ] New content is added to the [release announcement](https://drive.google.com/drive/u/0/folders/1DTIeswnEEq-NggJ25rm2BsDjcCQpDape)


Co-authored-by: Nicolas Pépin-Perreault <nicolas.pepin-perreault@camunda.com>
@saig0
Copy link
Member

saig0 commented Sep 28, 2020

bors retry

@zeebe-bors
Copy link
Contributor

zeebe-bors bot commented Sep 28, 2020

Build succeeded:

@zeebe-bors zeebe-bors bot merged commit be71ad7 into stable/0.24 Sep 28, 2020
@zeebe-bors zeebe-bors bot deleted the backports-024/5388-update-exporter branch September 28, 2020 05:21
github-merge-queue bot pushed a commit that referenced this pull request Mar 14, 2024
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.

None yet

2 participants