Update unique keys for latest issues transform to catch all updates #15700
Conversation
This file contains hidden or 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
clement-fouque
added
breaking change
bugfix
|
I confirmed locally that the transform is working as expected. |
🚀 Benchmarks reportTo see the full report comment with |
efd6
reviewed
Oct 20, 2025
clement-fouque
changed the title
… unique keys transformation
|
I’ve updated the title and PR description, and changed the version from 2.18.0 to 2.17.1. Initially, I thought this was a breaking change. However, since the transform is deleted and recreated, it’s not a breaking change after all. @efd6, could you please review? Thanks. |
andrewkroh
added
the
Team:Security-Service Integrations
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
💚 Build Succeeded
History
|
efd6
approved these changes
Oct 21, 2025
|
Package github - 2.17.1 containing this change is available at https://epr.elastic.co/package/github/2.17.1/ |
alexreal1314
pushed a commit
to alexreal1314/integrations
that referenced
this pull request
Oct 22, 2025
…lastic#15700) * refactor(transform): update unique keys for latest issues and bump version to 2.0.0 * refactor(transform): bump version to 2.17.0 and update changelog with bugfix details * chore(manifest): bump version to 2.18.0 * chore: update version to 2.17.1 and enhance changelog description for unique keys transformation
agithomas
pushed a commit
to agithomas/integrations
that referenced
this pull request
Oct 30, 2025
…lastic#15700) * refactor(transform): update unique keys for latest issues and bump version to 2.0.0 * refactor(transform): bump version to 2.17.0 and update changelog with bugfix details * chore(manifest): bump version to 2.18.0 * chore: update version to 2.17.1 and enhance changelog description for unique keys transformation
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.
Proposed commit message
This pull request updates the configuration for the GitHub issues Elasticsearch transform to improve how the latest state of issues is tracked and stored. The main focus is on making the transform more robust by using more reliable unique keys and bumping the transform version.
The previous transform wasn't taking into account all updates (e.g. adding a label to an issue). Since the field
github.issues.updated_atchanges each time the issue is updated, this field covers more use cases that the initialgithub.issues.created_atfield. I've also changed the unique issue identifier from url togithub.issues.id.Key changes:
Transform logic improvements:
unique_keyfields inlatest_issues/transform.ymlto usegithub.issues.idandgithub.issues.updated_atinstead of repository and URL fields. This ensures that the transform identifies the latest issue state more reliably and efficiently.Versioning:
_meta.fleet_transform_versionfrom1.0.0to2.0.0to indicate a breaking change and trigger reinstallation and restart of the transform.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots