-
Notifications
You must be signed in to change notification settings - Fork 62
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
Replication namespace #464
Replication namespace #464
Conversation
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Niyazbek Torekeldi <78027392+Tokesh@users.noreply.github.com>
Changes AnalysisCommit SHA: 4629754 API ChangesSummary
ReportThe full API changes report is available at: https://github.com/opensearch-project/opensearch-api-specification/actions/runs/11893879787/artifacts/2201699624 API Coverage
|
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Should we split the docker-compose.yml into docker-compose-default, docker-compose-multinode.yml or something like that? |
wow, do you work even on weekends? |
Take a look at #472 that allows custom docker compose and tests. |
Thank you! It looks really good |
update current version
Signed-off-by: Tokesh <tokesh789@gmail.com>
Spec Test Coverage Analysis
|
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
I passed the biggest part of CI/CD. |
Signed-off-by: Tokesh <tokesh789@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great!
I added .yml files to Vale preprocessing in #660, let's rebase this once it's merged to make sure it worked.
index.number_of_replicas: 2 | ||
response: | ||
status: 200 | ||
- synopsis: Create replication rule. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extract autofollow into a separate file called autofollow.yaml
.
@@ -0,0 +1,127 @@ | |||
$schema: ../../../json_schemas/test_story.schema.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are multiple examples here surrounding replication, one that starts replication, so see if that can be extracted in a start.yaml
, and another that gets replication stats, belongs in stats.yaml
.
Basically think of how these examples could be used in various parts of the documentation on their own, even if it means duplicating some API calls in prologues and epilogues.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think i can divide to:
replica.yaml
stats.yaml
autofollow.yaml
replica-rules.yaml
And the code will be duplicated everywhere where we create an index and start replicating it, if it works, then I can divide it like this and do it in a few days.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That works. Maybe rename replica.yaml to index.yaml, that one will have the replication as the main act.
Generally these files match the namespace and/or the API path, not the "theme", so replica-rules is not a thing, it will need another name.
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Niyazbek Torekeldi <78027392+Tokesh@users.noreply.github.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Glad we have a passing build!
Go through the fields and check whether they are semantically meaningful and need to be a $ref
to something that exists (time values, index names, etc.).
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Signed-off-by: Tokesh <tokesh789@gmail.com>
Thank you for a explained review. I read _common schemes and tried to fix all the places, where i can implement them. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small one left, the rest LGTM!
type: object | ||
properties: | ||
settings: | ||
anyOf: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a combination of SettingsBody
and these? So should be allOf
.
Signed-off-by: dblock <dblock@amazon.com>
I made the change I suggested above and merged, thank you, this is great work @Tokesh! |
Oh, i just checked. Thank you so much for detailed reviews and help! It's a pleasure working with you! |
Description
adding replication namespace specs
Issues Resolved
[#232]
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.