Skip to content

Tags: opensearch-project/anomaly-detection

Tags

3.0.0.0-alpha1

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Adding release notes for 3.0-alpha1 (#1432)

Signed-off-by: Junwei Dai <junweid@amazon.com>
Co-authored-by: Junwei Dai <junweid@amazon.com>

2.19.1.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Increment version to 2.19.1-SNAPSHOT (#1421)

Signed-off-by: opensearch-ci-bot <opensearch-infra@amazon.com>
Co-authored-by: opensearch-ci-bot <opensearch-infra@amazon.com>

2.19.0.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add release notes for 2.19.0 (#1412) (#1418)

* Add release notes for 2.19.0



* Addressed PR comments



---------


(cherry picked from commit ff200b2)

Signed-off-by: Owais <owaiskazi19@gmail.com>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

1.3.20.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Increment version to 1.3.20-SNAPSHOT (#1286)

Signed-off-by: opensearch-ci-bot <opensearch-infra@amazon.com>
Co-authored-by: opensearch-ci-bot <opensearch-infra@amazon.com>

2.18.0.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fix race condition in PageListener (#1351) (#1353)

* Fix race condition in PageListener

This PR
- Introduced an `AtomicInteger` called `pagesInFlight` to track the number of pages currently being processed. 
- Incremented `pagesInFlight` before processing each page and decremented it after processing is complete
- Adjusted the condition in `scheduleImputeHCTask` to check both `pagesInFlight.get() == 0` (all pages have been processed) and `sentOutPages.get() == receivedPages.get()` (all responses have been received) before scheduling the `imputeHC` task. 
- Removed the previous final check in `onResponse` that decided when to schedule `imputeHC`, relying instead on the updated counters for accurate synchronization.

These changes address the race condition where `sentOutPages` might not have been incremented in time before checking whether to schedule the `imputeHC` task. By accurately tracking the number of in-flight pages and sent pages, we ensure that `imputeHC` is executed only after all pages have been fully processed and all responses have been received.

Testing done:
1. Reproduced the race condition by starting two detectors with imputation. This causes an out of order illegal argument exception from RCF due to this race condition. Also verified the change fixed the problem.
2. added an IT for the above scenario.



* make sure increment before schedule



---------


(cherry picked from commit f62885a)

Signed-off-by: Kaituo Li <kaituo@amazon.com>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

2.17.1.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Increment version to 2.17.1-SNAPSHOT (#1318)

Signed-off-by: opensearch-ci-bot <opensearch-infra@amazon.com>
Co-authored-by: opensearch-ci-bot <opensearch-infra@amazon.com>

2.17.0.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Fix Security Tests After Changes to Permissions Requirements (#1308) (#…

…1310)

This PR addresses errors in security tests caused by recent changes in opensearch-project/security#4719. Previously, users needed both AD full access and source index permissions to fully utilize anomaly detection (AD). AD full access has already included all alias and mapping permissions.  it was inconsistent not to include index search permission, which would otherwise force users to create an additional role. The change in the referenced PR aimed to simplify user management.

Due to this change, existing security tests that relied on a user having AD full access but lacking data search permission would no longer trigger the expected search permission exception. This PR addresses that issue by creating a new user role with only AD read permission (note we didn't change ad read access permission in the referenced PR) and without source index search permission, ensuring the tests correctly validate the lack of search permissions.

Testing Done:
* Verified that previously failing security tests now pass


(cherry picked from commit 0aebc6d)

Signed-off-by: Kaituo Li <kaituo@amazon.com>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

1.3.19.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added release notes for 1.3.19 (#1283)

Signed-off-by: owaiskazi19 <owaiskazi19@gmail.com>

2.16.0.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
add 2.16 release note (#1268) (#1270)

(cherry picked from commit eb7aad4)

Signed-off-by: Jackie Han <jkhanjob@gmail.com>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

1.3.18.0

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Increment version to 1.3.18-SNAPSHOT (#1227)

Signed-off-by: opensearch-ci-bot <opensearch-infra@amazon.com>
Co-authored-by: opensearch-ci-bot <opensearch-infra@amazon.com>