Skip to content

Fix resultFormat of SegmentLoadStatusFetcher.#17987

Merged
cryptoe merged 1 commit intoapache:masterfrom
gianm:fix-segment-load-status-fetcher
May 8, 2025
Merged

Fix resultFormat of SegmentLoadStatusFetcher.#17987
cryptoe merged 1 commit intoapache:masterfrom
gianm:fix-segment-load-status-fetcher

Conversation

@gianm
Copy link
Contributor

@gianm gianm commented May 8, 2025

In #17846, SegmentLoadStatusFetcher was changed to send a resultFormat of "text/plain" rather than "objectLines". This effectively broke the feature of waiting for load status, since the load status would always be FAILED.

I am not sure why tests didn't catch this. I noticed it while running a local cluster.

In apache#17846, SegmentLoadStatusFetcher was changed to send a resultFormat
of "text/plain" rather than "objectLines". This effectively broke the
feature of waiting for load status, since the load status would always
be FAILED.
@gianm gianm added this to the 34.0.0 milestone May 8, 2025
@gianm gianm added the Bug label May 8, 2025
@github-actions github-actions bot added Area - Batch Ingestion Area - MSQ For multi stage queries - https://github.com/apache/druid/issues/12262 labels May 8, 2025
@cryptoe cryptoe merged commit 04ad5c5 into apache:master May 8, 2025
29 of 30 checks passed
@gianm gianm deleted the fix-segment-load-status-fetcher branch May 8, 2025 04:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area - Batch Ingestion Area - MSQ For multi stage queries - https://github.com/apache/druid/issues/12262 Bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants