Release notes for 2.19 #5318
Merged
Release notes for 2.19 #5318
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
rishabh6788
requested review from
dblock,
peterzhuamazon,
gaiksaya,
zelinh,
prudhvigodithi,
Divyaasm and
tianleh
as code owners
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5318 +/- ##
=======================================
Coverage 92.04% 92.04%
=======================================
Files 202 202
Lines 7036 7036
=======================================
Hits 6476 6476
Misses 560 560 ☔ View full report in Codecov by Sentry. |
gaiksaya
reviewed
Feb 11, 2025
Comment on lines
+14
to
+122
| * Feat: only support visual editor alerts to navigate to discover([#368](https://github.com/opensearch-project/dashboards-assistant/pull/368)) | ||
| * Feat: return 404 instead of 500 for missing agent config name([#384](https://github.com/opensearch-project/dashboards-assistant/pull/384)) | ||
| * Feat: Update UI for In-context summarization in Alerts table([#392](https://github.com/opensearch-project/dashboards-assistant/pull/392)) | ||
| * Feat: Hide "stop generation" and regenerate button based on feature flag([#394](https://github.com/opensearch-project/dashboards-assistant/pull/394)) | ||
| * Feat: Chatbot entry UI redesign([#396](https://github.com/opensearch-project/dashboards-assistant/pull/396)) | ||
| * Feat: Set logo config in assistant and read logo by config([#401](https://github.com/opensearch-project/dashboards-assistant/pull/401)) | ||
| * Feat: Update dropdown list button label and remove popover title([#407](https://github.com/opensearch-project/dashboards-assistant/pull/407)) | ||
| * Feat: Use feature flag to disable the delete conversation api([#409](https://github.com/opensearch-project/dashboards-assistant/pull/409)) | ||
| * Feat: Disable the rename conversation api using feature flag([#410](https://github.com/opensearch-project/dashboards-assistant/pull/410)) |
There was a problem hiding this comment.
Just wondering if we should remove the Feat: wording?
There was a problem hiding this comment.
It is present in all our previous release notes.
| ### Opensearch Skills | ||
|
|
||
|
|
||
| * bump byte buddy version from 1.15.4 to 1.15.10 ([#466](https://github.com/opensearch-project/skills/pull/466)) |
There was a problem hiding this comment.
Suggested change
| * bump byte buddy version from 1.15.4 to 1.15.10 ([#466](https://github.com/opensearch-project/skills/pull/466)) | |
| * Bump byte buddy version from 1.15.4 to 1.15.10 ([#466](https://github.com/opensearch-project/skills/pull/466)) |
| ### Opensearch Alerting | ||
|
|
||
|
|
||
| * optimize execution of workflow consisting of bucket-level followed by doc-level monitors ([#1729](https://github.com/opensearch-project/alerting/pull/1729)) |
There was a problem hiding this comment.
Suggested change
| * optimize execution of workflow consisting of bucket-level followed by doc-level monitors ([#1729](https://github.com/opensearch-project/alerting/pull/1729)) | |
| * Optimize execution of workflow consisting of bucket-level followed by doc-level monitors ([#1729](https://github.com/opensearch-project/alerting/pull/1729)) |
| ### Opensearch Common Utils | ||
|
|
||
|
|
||
| * add should\_create\_single\_alert\_for\_findings field to security-analytics ([#757](https://github.com/opensearch-project/common-utils/pull/757)) |
There was a problem hiding this comment.
Suggested change
| * add should\_create\_single\_alert\_for\_findings field to security-analytics ([#757](https://github.com/opensearch-project/common-utils/pull/757)) | |
| * Add should\_create\_single\_alert\_for\_findings field to security-analytics ([#757](https://github.com/opensearch-project/common-utils/pull/757)) |
|
|
||
| * Experimental derived source functionality for k-NN vectors optimizes storage by removing vectors from the JSON source and dynamically injecting them when needed, supporting flat vector mappings, object fields, and single-level nested fields. | ||
|
|
||
| **DEPRECATION NOTICES** |
There was a problem hiding this comment.
Suggested change
| **DEPRECATION NOTICES** | |
| #### DEPRECATION NOTICES |
Comment on lines
+163
to
+166
|
|
||
|
|
There was a problem hiding this comment.
same format all across and previous releases. Doesn't really matter when rendered.
Signed-off-by: Rishabh Singh <sngri@amazon.com>
Co-authored-by: Sayali Gaikawad <61760125+gaiksaya@users.noreply.github.com> Signed-off-by: Rishabh Singh <rishabhksingh@gmail.com>
Co-authored-by: Sayali Gaikawad <61760125+gaiksaya@users.noreply.github.com> Signed-off-by: Rishabh Singh <rishabhksingh@gmail.com>
Signed-off-by: Rishabh Singh <sngri@amazon.com>
peterzhuamazon
approved these changes
Feb 11, 2025
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
Added release notes for OpenSearch-2.19 release.
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.