Tianli Feng

Results 26 comments of Tianli Feng

> Regarding these changes for the plugins, do we have an ETA on when OpenSearch and OpenSearch-Dashboards will rename their references? Hi @qreshi 😄 Such class/method names that in OpenSearch...

> Since this issue is currently tagged as `2.0.0` and on the roadmap should we disambiguate that by detailing a high-level summary of what we expect to be done by...

After the incomplete attempt to provide alternative `allowlist` APIs as well as keeping the existing whitelist APIs in this PR, I decided not to deprecate the `whitelist` APIs before replacing...

### The plan to resolve the issue: **Result:** - On `2.x` branch: 1. There are deprecation notice to all public and protected class/method/variable names in the code, which contain "master"...

This is the plan to resolve the issue. ## Goal of the enhancement Replace non-inclusive terminology "master" throughout this repository with inclusive one. ## Context #### What is "inclusive language"?...

Hi all, We proposed to use "ClusterManager" as the replacement to the node role "master", after hearing opinions from PR #564. "leader" is a concise name, but the responsibilities of...

@peternied Thank you for your suggestion! I knew this campaign lack a mechanism to validate the achievement, it looks like a feasible solution. 😄

Other failure with different error message. 1 https://github.com/opensearch-project/OpenSearch/pull/4115#issuecomment-1204413850 https://build.ci.opensearch.org/job/gradle-check/1383/ ``` > Task :plugins:repository-s3:yamlRestTest REPRODUCE WITH: ./gradlew ':plugins:repository-s3:yamlRestTest' --tests "org.opensearch.repositories.s3.RepositoryS3ClientYamlTestSuiteIT.test {yaml=repository_s3/20_repository_permanent_credentials/Delete a non existing snapshot}" -Dtests.seed=6AEAC5574EE779EE -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=pt-BR -Dtests.timezone=Africa/Nairobi...

Hi abdalians, Thank you for pointing it out! I transferred the issue from Alerting plugin repo to here, as it's related to the front-end part. Besides, I labeled the issue...