-
Notifications
You must be signed in to change notification settings - Fork 996
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.
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
Allow ingestion job grouping/consolidation to be configurable #825
Conversation
/test test-end-to-end-batch-dataflow |
/retest |
@pyalex: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest |
/kind feature |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pyalex, woop The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
Decision regarding how to group sources and stores into IngestionJobs is extracted from
JobCoordinatorService
toJobGroupingStrategy
. Thus it's now configurable withfeast.jobs.consolidate-jobs-per-source
whether to create one job per Source (and write to all stores from one job) or one job per pair Source-Store and write only to one store in job. The latter is default.Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: