Skip to content

Fix default HTTPS protocol to use HttpsSegmentFetcher#17675

Open
ilamhs wants to merge 1 commit intoapache:masterfrom
ilamhs:fix-https-segment-fetcher-routing
Open

Fix default HTTPS protocol to use HttpsSegmentFetcher#17675
ilamhs wants to merge 1 commit intoapache:masterfrom
ilamhs:fix-https-segment-fetcher-routing

Conversation

@ilamhs
Copy link
Contributor

@ilamhs ilamhs commented Feb 10, 2026

The default segment fetcher for HTTPS protocol incorrectly returns HttpSegmentFetcher instead of HttpsSegmentFetcher. This means SSL configuration options in HttpsSegmentFetcher (including the renewable SSL context added in #17315) are never used for default HTTPS fetches.

This change:

  • Adds a dedicated HTTPS_SEGMENT_FETCHER instance
  • Initializes it alongside other default fetchers
  • Returns it for HTTPS protocol in getSegmentFetcher()
  • Updates javadoc and test to reflect correct behavior

Instructions:

  1. The PR has to be tagged with at least one of the following labels (*):
    1. feature
    2. bugfix
    3. performance
    4. ui
    5. backward-incompat
    6. release-notes (**)
  2. Remove these instructions before publishing the PR.

(*) Other labels to consider:

  • testing
  • dependencies
  • docker
  • kubernetes
  • observability
  • security
  • code-style
  • extension-point
  • refactor
  • cleanup

(**) Use release-notes label for scenarios like:

  • New configuration options
  • Deprecation of configurations
  • Signature changes to public methods/interfaces
  • New plugins added or old plugins removed

The default segment fetcher for HTTPS protocol incorrectly returns
HttpSegmentFetcher instead of HttpsSegmentFetcher. This means SSL
configuration options in HttpsSegmentFetcher (including the renewable
SSL context added in apache#17315) are never used for default HTTPS fetches.

This change:
- Adds a dedicated HTTPS_SEGMENT_FETCHER instance
- Initializes it alongside other default fetchers
- Returns it for HTTPS protocol in getSegmentFetcher()
- Updates javadoc and test to reflect correct behavior
@ilamhs ilamhs changed the title Fix default HTTPS protocol to use HttpsSegmentFetcher [bugfix] Fix default HTTPS protocol to use HttpsSegmentFetcher Feb 10, 2026
@ilamhs ilamhs changed the title [bugfix] Fix default HTTPS protocol to use HttpsSegmentFetcher Fix default HTTPS protocol to use HttpsSegmentFetcher Feb 10, 2026
Copy link
Contributor

@AlexanderKM AlexanderKM left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@codecov-commenter
Copy link

codecov-commenter commented Feb 10, 2026

❌ 1 Tests Failed:

Tests completed Failed Passed Skipped
10804 1 10803 45
View the top 3 failed test(s) by shortest run time
org.apache.pinot.controller.helix.core.minion.PinotTaskManagerDistributedLockingTest::testForceReleaseLockDuringTaskExecution
Stack Traces | 18.5s run time
Both createTask calls should have generated tasks expected [2] but found [3]
org.apache.pinot.controller.helix.core.minion.PinotTaskManagerDistributedLockingTest::testForceReleaseLockDuringTaskExecution
Stack Traces | 20.8s run time
Both createTask calls should have generated tasks expected [2] but found [3]
org.apache.pinot.integration.tests.TlsIntegrationTest::testRealtimeSegmentUploadDownload
Stack Traces | 30.4s run time
Failed to return result in 30000ms

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

@ilamhs
Copy link
Contributor Author

ilamhs commented Feb 10, 2026

Verified that the tests failures are independent of this PR.

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