Skip to content

fix zclient retry logic for customized callback and test#39

Open
xyuanlu wants to merge 15 commits into
metaclientfrom
zkClient_Async_retry
Open

fix zclient retry logic for customized callback and test#39
xyuanlu wants to merge 15 commits into
metaclientfrom
zkClient_Async_retry

Conversation

@xyuanlu

@xyuanlu xyuanlu commented Feb 1, 2023

Copy link
Copy Markdown
Owner

Issues

  • My PR addresses the following Helix issues and references them in the PR description:

(apache#200 - Link your issue number here: You can write "Fixes #XXX". Please use the proper keyword so that the issue gets closed automatically. See https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue
Any of the following keywords can be used: close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved)

Description

  • Here are some details about my PR, including screenshots of any UI changes:

(Write a concise description including what, why, how)

Tests

  • The following tests are written for this issue:

(List the names of added unit/integration tests)

  • The following is the result of the "mvn test" command on the appropriate module:

(If CI test fails due to known issue, please specify the issue and test PR locally. Then copy & paste the result of "mvn test" to here.)

Changes that Break Backward Compatibility (Optional)

  • My PR contains changes that break backward compatibility or previous assumptions for certain methods or API. They include:

(Consider including all behavior changes for public methods or API. Also include these changes in merge description so that other developers are aware of these changes. This allows them to make relevant code changes in feature branches accounting for the new method/API behavior.)

Documentation (Optional)

  • In case of new functionality, my PR adds documentation in the following wiki page:

(Link the GitHub wiki you added)

Commits

  • My commits all reference appropriate Apache Helix GitHub issues in their subject lines. In addition, my commits follow the guidelines from "How to write a good git commit message":
    1. Subject is separated from body by a blank line
    2. Subject is limited to 50 characters (not including Jira issue reference)
    3. Subject does not end with a period
    4. Subject uses the imperative mood ("add", not "adding")
    5. Body wraps at 72 characters
    6. Body explains "what" and "why", not "how"

Code Quality

  • My diff has been formatted using helix-style.xml
    (helix-style-intellij.xml if IntelliJ IDE is used)

xyuanlu and others added 15 commits October 20, 2022 09:49
Add new submodule meta client - a generic metadata client
Add listener interfaces and factory class for metaclient interface
Add Meta client factory and ZkMetaClient constructor
…implementation (apache#2333)

Prepare zkclient for meta-client DataChangeListener add new method in IZkDataListener
Implement boolean flag connectOnInit in zkclient for decoupling
Override equals and hashcode for the converter class
Add basic CRUD for ZkMetaClient and test
Metaclient - Op and OpResult Logic for transactional suppor
Metaclient - Implementation of Create from CRUD operations
* Implement data change listener for ZkMetaClient and test
… zkclient (apache#2346)

Prepare zkclient and implement new adapter for child change listener.
1. Implementation of the transactionOp() operation method in zkMetaClient. This method enables transactional support by converting metaclient operations into zk ops and running the zk.multi() method. The results are converted back from zk opResults to metaclient opResults.
2. Created a separate util class zkMetaClientUtil for Util functions and the logic behind the implementation of transactionOp().
Refactoring MetaClient Exception. Creating separate exception directory.
Rename and reformat metaclient test and util
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants