fix(exporters/elasticsearch-exporter): custom headers #4666
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* service tasks with custom headers that contains a dot can lead to mapping failures in ES * avoid mapping failures by disabling the index of custom headers for job and job batch records
|
@sdorokhova, this PR change the |
This was referenced Jun 4, 2020
sdorokhova
approved these changes
Jun 5, 2020
|
bors r+ |
|
@korthout , @sdorokhova : thank you for the fast review 🍪 |
Build succeeded |
zeebe-bors bot
added a commit
that referenced
this pull request
Jun 5, 2020
4669: [Backport] fix(exporters/elasticsearch-exporter): custom headers r=saig0 a=saig0 ## Description * service tasks with custom headers that contain a dot can lead to mapping failures in ES * avoid mapping failures by disabling the index of custom headers for job and job batch records ## Related issues backport of #4666 to `0.22` # Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
zeebe-bors bot
added a commit
that referenced
this pull request
Jun 5, 2020
4670: [Backport] fix(exporters/elasticsearch-exporter): custom headers r=saig0 a=saig0 ## Description * service tasks with custom headers that contains a dot can lead to mapping failures in ES * avoid mapping failures by disabling the index of custom headers for job and job batch records ## Related issues backport of #4666 to `0.23` # Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
zeebe-bors bot
added a commit
that referenced
this pull request
Jun 5, 2020
4669: [Backport] fix(exporters/elasticsearch-exporter): custom headers r=saig0 a=saig0 ## Description * service tasks with custom headers that contain a dot can lead to mapping failures in ES * avoid mapping failures by disabling the index of custom headers for job and job batch records ## Related issues backport of #4666 to `0.22` # Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
zeebe-bors bot
added a commit
that referenced
this pull request
Jun 5, 2020
4669: [Backport] fix(exporters/elasticsearch-exporter): custom headers r=saig0 a=saig0 ## Description * service tasks with custom headers that contain a dot can lead to mapping failures in ES * avoid mapping failures by disabling the index of custom headers for job and job batch records ## Related issues backport of #4666 to `0.22` # Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
zeebe-bors bot
added a commit
that referenced
this pull request
Jun 5, 2020
4669: [Backport] fix(exporters/elasticsearch-exporter): custom headers r=saig0 a=saig0 ## Description * service tasks with custom headers that contain a dot can lead to mapping failures in ES * avoid mapping failures by disabling the index of custom headers for job and job batch records ## Related issues backport of #4666 to `0.22` # Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
zeebe-bors bot
added a commit
that referenced
this pull request
Jun 5, 2020
4669: [Backport] fix(exporters/elasticsearch-exporter): custom headers r=saig0 a=saig0 ## Description * service tasks with custom headers that contain a dot can lead to mapping failures in ES * avoid mapping failures by disabling the index of custom headers for job and job batch records ## Related issues backport of #4666 to `0.22` # Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
github-merge-queue bot
pushed a commit
that referenced
this pull request
Mar 14, 2024
* refactor: migrate process instances diagram panel to Carbon * style: migrate statistics overlay component to Carbon * fix: fetch process statistics on filter change * chore: use spacing tokens for badges
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related issues
closes #4640
Pull Request Checklist
mvn clean install -DskipTestslocally before committing