Skip to content

Add Thread::getId() to Thread::threadId() migration documentation #8

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add Thread::getId() to Thread::threadId() migration documentation #8

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions release-notes/opensearch-documentation-release-notes-2.19.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,3 +34,11 @@ The OpenSearch 2.19.0 documentation includes the following additions and updates
- Add documentation for pruning neural sparse vectors [#8984](https://github.com/opensearch-project/documentation-website/pull/8984)
- Add document the usage of update document API with ingest pipeline [#8874](https://github.com/opensearch-project/documentation-website/pull/8874)
- Update innerHits of nested k-NN fields [#8822](https://github.com/opensearch-project/documentation-website/pull/8822)

## Updates to existing documentation

- Replace Thread::getId() with Thread::threadId() [#18237](https://github.com/opensearch-project/OpenSearch/pull/18237)
- Deprecated usages of `Thread::getId()` have been replaced with `Thread::threadId()` introduced in Java 19.
- This change ensures compatibility with newer Java versions and eliminates deprecation warnings.
- The updates are scoped to actual `Thread` usage and do not affect domain-specific `getId()` calls on objects like `Task`, `Node`, etc.
- This change improves code maintainability and future-proofs the codebase against Java updates.