-
Notifications
You must be signed in to change notification settings - Fork 73
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.
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
Compatibility with segment replication #989
Comments
will respond later. |
revert change pr created - #999 @dreamer-89 do you have any instruction on how to test this to ensure the core side change is working well with AD? |
Thanks @jackiehanyang for working on this change. I commented on revert PR #999 |
I've conducted a comprehensive review of our backend and would like to share my insights on two key components:
As indicated in Issue #974, there's a slight delay of a few seconds. However, given that we operate with a minute-level delay, I believe this won't pose any significant concerns. In light of the above, I am inclined to approve Pull Request #999 . This should allow us to finalize the seg replication compatibility. |
We do need another approver. |
@kaituo @jackiehanyang : As PR #999 is merged and backported. Do you mind closing this issue if nothing else is pending. |
@kaituo @owaiskazi19 @jackiehanyang : Mind closing this issue if nothing else is pending |
Coming from #936 (comment) and with core now supporting real time reads for segment replication enabled indices (opensearch-project/OpenSearch#8536), we can revert #948 which enforces DOCUMENT replication strategy.
CC @kaituo @ohltyler
Request owners to label this issue with
2.10.0
release.The text was updated successfully, but these errors were encountered: