feat : adhere to coding standards

[rajadilipkolli]

Summary by CodeRabbit

• New Features

  • Introduced a new configuration property to enable virtual threads in the Spring application.

• Chores

  • Updated license information to maintain current standards.

• Refactor

  • Modified method visibility for several methods, restricting access to package-private.
  • Removed @Bean annotation from a method, altering its registration as a Spring bean.

[coderabbitai]

Walkthrough

This pull request includes several updates across different files. The AnalyticsProducerApplicationIntegrationTest class has its license year updated from 2023 to 2025. The pom.xml file for the Kafka consumer has the version of the Google Java Format plugin updated from 1.25.0 to 1.25.2. Method visibility changes were made in the PageViewEventProcessor, PageCountSink, and ContainerConfiguration classes, changing their methods from public to package-private. Additionally, new configuration properties enabling virtual threads were added to the application.properties files in multiple modules.

Changes

File	Change Summary
kafka-streams/.../AnalyticsProducerApplicationIntegrationTest.java	- Updated license comment from 2023 to 2025
kafka-streams/.../pom.xml	- Updated Google Java Format plugin version from 1.25.0 to 1.25.2
kafka-streams/.../PageViewEventProcessor.java, kafka-streams/.../PageCountSink.java	- Changed method visibility from public to package-private for processInput and processStreamFromPcsTopic
kafka-spring-boot/.../ContainerConfiguration.java, kafka-spring-cloud-sample/.../ContainersConfig.java	- Changed method visibility from public to package-private for kafkaProperties
kafka-spring-cloud-sample/.../Receiver.java	- Removed @Bean annotation from receive method, changing its registration in Spring context
kafka-streams/.../application.properties, kafka-spring-boot/.../application.properties, kafka-avro/.../application.properties, kafka-spring-boot/.../application.properties	- Added property: spring.threads.virtual.enabled=true

Suggested labels

component : dsl-integration

Poem

In the code where rabbits play,
A new year dawns, hip-hip-hooray!
Methods tucked in cozy tight,
Virtual threads take joyful flight.
With each change, we hop and sway! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e709313 and e91d9ab.

📒 Files selected for processing (1)

• kafka-streams/analytics-spring-cloud-streams-kafka-consumer/pom.xml (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• kafka-streams/analytics-spring-cloud-streams-kafka-consumer/pom.xml

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build

---

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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

🧹 Nitpick comments (2)

kafka-streams/analytics-spring-cloud-streams-kafka-producer/src/main/resources/application.properties (1)

5-5: Ensure Consistent Documentation for Virtual Threads Configuration

The new property spring.threads.virtual.enabled=true correctly enables virtual threads for the producer module. Please consider adding an inline comment (or updating the project README) to explain the rationale and potential impact of enabling virtual threads. This will enhance maintainability and help new team members understand the intention behind this configuration.

kafka-streams/analytics-spring-cloud-streams-kafka-consumer/src/main/resources/application.properties (1)

5-5: Consistent Virtual Threads Configuration in Consumer Module

The addition of spring.threads.virtual.enabled=true in the consumer configuration aligns with the producer module update. As with the producer, consider adding a brief comment to explain why virtual threads are being enabled. This documentation will support adherence to coding standards by ensuring that configuration changes are clear and justified.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fad3edc and 8a2a29d.

📒 Files selected for processing (6)

• kafka-streams/analytics-spring-cloud-streams-kafka-consumer/pom.xml (1 hunks)
• kafka-streams/analytics-spring-cloud-streams-kafka-consumer/src/main/java/com/example/analytics/processor/PageViewEventProcessor.java (1 hunks)
• kafka-streams/analytics-spring-cloud-streams-kafka-consumer/src/main/java/com/example/analytics/sink/PageCountSink.java (1 hunks)
• kafka-streams/analytics-spring-cloud-streams-kafka-consumer/src/main/resources/application.properties (1 hunks)
• kafka-streams/analytics-spring-cloud-streams-kafka-producer/src/main/resources/application.properties (1 hunks)
• kafka-streams/analytics-spring-cloud-streams-kafka-producer/src/test/java/com/example/analytics/AnalyticsProducerApplicationIntegrationTest.java (1 hunks)

✅ Files skipped from review due to trivial changes (2)

• kafka-streams/analytics-spring-cloud-streams-kafka-producer/src/test/java/com/example/analytics/AnalyticsProducerApplicationIntegrationTest.java
• kafka-streams/analytics-spring-cloud-streams-kafka-consumer/pom.xml

🔇 Additional comments (2)

kafka-streams/analytics-spring-cloud-streams-kafka-consumer/src/main/java/com/example/analytics/sink/PageCountSink.java (1)

17-17: Good practice: Reduced method visibility.

Changing the processStreamFromPcsTopic method from public to package-private visibility adheres to the principle of least privilege. Since the method is annotated with @Bean, Spring can still detect and instantiate it without requiring public visibility. This change improves encapsulation while maintaining full functionality.

kafka-streams/analytics-spring-cloud-streams-kafka-consumer/src/main/java/com/example/analytics/processor/PageViewEventProcessor.java (1)

21-21: Good practice: Reduced method visibility.

Changing the processInput method from public to package-private visibility adheres to the principle of least privilege. Spring's component scanning can still detect and process @Bean methods without requiring public visibility. This change improves encapsulation without affecting functionality, and maintains consistency with the similar change in PageCountSink.