Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for size based minion UpsertCompactMerge task #14634

Open
tibrewalpratik17 opened this issue Dec 11, 2024 · 0 comments
Open

Support for size based minion UpsertCompactMerge task #14634

tibrewalpratik17 opened this issue Dec 11, 2024 · 0 comments
Assignees
@tibrewalpratik17
Labels
feature request minion

Comments

@tibrewalpratik17
Copy link
Contributor

Similar to #12225
Follow-up from #14477 (comment)

Right now, we use maxNumRecordsPerTask / maxNumRecordsPerSegment for tracking the output segment size in UpsertCompactMerge task. But we have moved to using size-based thresholds for most realtime segments during ingestion and using size is more intuitive rather than row-count.

The issue is to track adding support for output-segment size based config for UpsertCompactMerge task specifically.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tibrewalpratik17 tibrewalpratik17

Labels
feature request minion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tibrewalpratik17