-
Notifications
You must be signed in to change notification settings - Fork 281
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
Replace opensearch class names with opendistro class names during serialization and restore them back during deserialization #1278
Conversation
…ialization and restore them back during deserialization
Codecov Report
@@ Coverage Diff @@
## main #1278 +/- ##
============================================
+ Coverage 64.71% 64.73% +0.01%
+ Complexity 3195 3193 -2
============================================
Files 247 247
Lines 17191 17230 +39
Branches 3042 3045 +3
============================================
+ Hits 11126 11154 +28
- Misses 4517 4526 +9
- Partials 1548 1550 +2
Continue to review full report at Codecov.
|
I tested a mixed cluster with 1 Opensearch master node and 2 Elasticsearch data nodes. node1: Opensearch (localhost:9200)
|
Execute privileged actions using AccessController Refactored code to simplify and generalize name replacement in serialization descriptor
…ialization and restore them back during deserialization (opensearch-project#1278)
…ring serialization and restore them back during deserialization (opensearch-project#1278)" This reverts commit 4abbafc. Signed-off-by: cliu123 <[email protected]>
…ring serialization and restore them back during deserialization (#1278)" (#1691) This reverts commit 4abbafc. Signed-off-by: cliu123 <[email protected]>
…ialization and restore them back during deserialization (opensearch-project#1278)
…ring serialization and restore them back during deserialization (opensearch-project#1278)" (opensearch-project#1691) This reverts commit 4abbafc. Signed-off-by: cliu123 <[email protected]>
opensearch-security pull request intake form
Please provide as much details as possible to get feedback/acceptance on your PR quickly
Category: (Enhancement, New feature, Bug fix, Test fix, Refactoring, Maintenance, Documentation)
bug fix
Github Issue # or road-map entry, if available: [BUG] [class_not_found_exception] during rolling upgrade on security enabled cluster #1259
Description of changes: To be backward compatible it is necessary to preserve wire protocol between nodes. Changing package names caused wire protocol incompatibility. To restore compatibility, we can replace package names during serialization and restore them back during deserialization.
Why these changes are required? to support mixed cluster during rolling upgrade
What is the old behavior before changes and new behavior after changes? (Please add any example/logs/screen-shot if available)
Testing done: (Please provide details of testing done: Unit testing, integration testing and manual testing)
TO-DOs, if any: (Please describe pending items and provide Github issues# for each of them)
Is it backport from main branch? (If yes, please add backport PR # and commits #)
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
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.