opensearch-project / opensearch-project/security
[BUG] Potential regression in cross cluster searches from 3.7 -> 2.19
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 252
- Forks
- 395
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 76
Description
What is the bug?
Potential regression in cross cluster searches from OpenSearch 3.7 -> OpenSearch 2.19. Same security configuration allows for successful cross cluster search on OpenSearch 2.19 -> OpenSearch 2.19 setup. It's not clear to me whether this is an intended change and the security setup I had was always wrong or a regression. I wasn't able to find anything in release notes pointing at a change here
How can one reproduce the bug?
- Reproduction can be found in this repo: https://github.com/zakerf/opensearch-ccs-issue-reproduction
What is the expected behavior?
For my setup to keep working, or a notice of a breaking change somewhere
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reproduction repository linked in the issue and compare the cross-cluster search behavior between the OpenSearch 3.7 → 2.19 setup and the working 2.19 → 2.19 setup. Check relevant release notes and security configuration behavior first. Done means determining whether this is a regression or intentional breaking change, then fixing compatibility or documenting the required change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100