Migrated from deprecated BrokerClient to new BrokerClient

[tarunk8924]

Title:
Improved Segment Load Status Fetcher: Enhanced Query Handling and Code Refactoring

Description:
This PR introduces improvements and refactoring to the SegmentLoadStatusFetcher in the Apache Druid project. The changes aim to improve code maintainability, enhance performance in segment loading operations, and ensure more reliable status checks when waiting for segments to load.

Key Changes:

1. Enhanced Query Handling:

   • Improved SQL query logic to handle additional segment scenarios, including on-demand and unknown segment types.
   • Ensured efficient filtering and robust conditional handling to better track segment loading.

2. Status Update Logic:

   • Simplified and optimized the status update mechanism.
   • Ensured accurate updates for segment status during the wait period, including proper tracking of states (success, failure, timeout).

3. Exception Handling Improvements:

   • Enhanced error handling during load status fetch operations.
   • Updated logic to avoid unnecessary task failures if an exception occurs during the segment wait.

4. Refactoring for Code Readability:

   • Reorganized methods to improve readability and reduce redundant operations.
   • Refactored the version condition creation logic to minimize computational overhead.

5. Thread Management:

   • Properly shutdown executor service to prevent resource leaks.
   • Added additional safety checks during concurrent operations.

Testing:*

• Verified the query execution against multiple broker scenarios.
• Conducted unit tests to ensure accurate segment status updates.
• Stress-tested the system to confirm that timeout and exception handling worked as expected.

Backward Compatibility:
The changes maintain backward compatibility with existing segment loading workflows in Apache Druid.

Reviewer Notes:

• Review the SQL query and version condition logic for correctness and efficiency.

• Validate exception handling mechanisms for edge cases.

• Ensure thread handling improvements are correctly implemented.
  This PR has:

• been self-reviewed.

  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

• added documentation for new or modified features or behaviors.

• a release note entry in the PR description.

• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.

• added or updated version, license, or notice information in licenses.yaml

• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.

• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.

• added integration tests.

• been tested in a test Druid cluster.

[kfaraz]

@tarunk8924 , thanks for the changes!
I think you have reformatted which has bloated up the diff making the review difficult.
Could you please take a look at the diff and revert the unnecessary changes?

[tarunk8924]

Yeah sure

…

On Thu, 30 Jan, 2025, 10:01 am Kashif Faraz, ***@***.***> wrote: @tarunk8924 <https://github.com/tarunk8924> , thanks for the changes! I think you have reformatted which has bloated up the diff making the review difficult. Could you please take a look at the diff and revert the unnecessary changes? — Reply to this email directly, view it on GitHub <#17681 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDCD2KALL3LSL5TACG5K7LD2NGTJTAVCNFSM6AAAAABWDOIPDOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRTGQ4TIOBVG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tarunk8924]

@kfaraz I have done the changes..!!!