chore: delete redundant Java header files

[caicancai]

Motivation:

as titile

Modification:

Describe the idea and modifications you've done.

Result:

Fixes #.

If there is no issue then describe the changes introduced by this PR.

Summary by CodeRabbit

• Refactor

  • Streamlined the configuration setup for applyDisruptor to enhance code readability and maintainability.

• Tests

  • Removed unnecessary imports in NodeTest.java to clean up the test dependencies.

[coderabbitai]

Walkthrough

The changes focus on optimizing and cleaning up the configuration of applyDisruptor in NodeImpl.java by reformatting method chaining and removing redundant comments. In the test file NodeTest.java, the unnecessary imports for ThreadPoolsFactory and MetricRegistry are removed to streamline the dependencies. These alterations aim to enhance code readability and maintainability.

Changes

Files	Change Summary
.../jraft/core/NodeImpl.java	Reformatted applyDisruptor method chaining, removed comments for a more concise configuration setup.
.../jraft/core/NodeTest.java	Removed unused imports (ThreadPoolsFactory and MetricRegistry) improving code cleanliness.

Poem

Amid the code, a dance so neat,
Disruptor chains now concise and sweet.
Imports refined, the test file sings,
Efficiency in every line, it brings.
Clean and crisp, our methods gleam,
In JRaft's core, we chase the dream.

---

Tip

Early access features

• OpenAI gpt-4o model for reviews and chat.

Note:

• You can disable early access features from the CodeRabbit UI or by setting early_access: false in the CodeRabbit configuration file.
• Please join our Discord Community to provide feedback and report issues.
• OSS projects are always opted into early access features.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a71fae7 and ece20f9.

Files selected for processing (2)

• jraft-core/src/main/java/com/alipay/sofa/jraft/core/NodeImpl.java (1 hunks)
• jraft-core/src/test/java/com/alipay/sofa/jraft/core/NodeTest.java (1 hunks)

Files skipped from review due to trivial changes (1)

• jraft-core/src/test/java/com/alipay/sofa/jraft/core/NodeTest.java

Additional comments not posted (1)

jraft-core/src/main/java/com/alipay/sofa/jraft/core/NodeImpl.java (1)

988-993: Reformatting Method Chaining for applyDisruptor Configuration

The reformatting of the applyDisruptor configuration improves readability by consolidating the method chaining into a single line. This is a subjective change and aligns with the code style preferences.

- this.applyDisruptor = DisruptorBuilder.<LogEntryAndClosure> newInstance()
-     .setRingBufferSize(this.raftOptions.getDisruptorBufferSize())
-     .setEventFactory(new LogEntryAndClosureFactory())
-     .setThreadFactory(new NamedThreadFactory("JRaft-NodeImpl-Disruptor-", true)) //
-     .setProducerType(ProducerType.MULTI)
-     .setWaitStrategy(new BlockingWaitStrategy())
-     .build();
+ this.applyDisruptor = DisruptorBuilder.<LogEntryAndClosure> newInstance().setRingBufferSize(this.raftOptions.getDisruptorBufferSize()).setEventFactory(new LogEntryAndClosureFactory()).setThreadFactory(new NamedThreadFactory("JRaft-NodeImpl-Disruptor-", true)).setProducerType(ProducerType.MULTI).setWaitStrategy(new BlockingWaitStrategy()).build();

[caicancai]

cc @fengjiachun PATL， thanks

[fengjiachun]

LGTM