-
Notifications
You must be signed in to change notification settings - Fork 14
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
Introduced DatasetRegistry abstraction, encapsulating listing and resolution of datasets #941
Merged
zaychenko-sergei
merged 3 commits into
master
from
857-show-tables-query-times-out-after-a-minute
Nov 21, 2024
Merged
Introduced DatasetRegistry abstraction, encapsulating listing and resolution of datasets #941
zaychenko-sergei
merged 3 commits into
master
from
857-show-tables-query-times-out-after-a-minute
Nov 21, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
a5e494f
to
e7e895e
Compare
sergiimk
reviewed
Nov 15, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed changes in domain/
up until transform_elaboration_service
- will continue tomorrow.
sergiimk
reviewed
Nov 17, 2024
src/domain/task-system/services/src/task_logical_plan_runner_impl.rs
Outdated
Show resolved
Hide resolved
c701dd7
to
112638d
Compare
…esolution of datasets. Key changes: - Registry is backed by database-stored dataset entries, which are automatically maintained - Scope for `DatasetRepository` is now limited to support `DatasetRegistry` and in-memory dataset dependency graph - New concept of `ResolvedDataset`: a wrapper arround `Arc<dyn Dataset>`, aware of dataset identity - `DatasetRegistryRepoBridge` utility connects both abstractions in a simple way for testing needs - Query and Dataset Search functions now consider only the datasets accessible for current user - Core services now explicitly separate planning (transactional) and execution (non-transactional) processing phases - Similar decomposition introduced in task system execution logic - Revised implementation of core commands and services: `pull`, `push`, `reset`, `verify`, `compact`, setting watermark - More parallelism from `pull` command, allowing to mix ingest/sync/transform operations of the same depth level - Optimized `pull` flow, when a single non-recursive dataset is sent for processing - Batched form for dataset authorization checks - Ensuring correct transactionality for dataset lookup and authorization checks all over the code base - Passing multi/single tenancy as an enum configuration instead of boolean - Renamed outbox "durability" term to "delivery mechanism" to clarify the design intent - Greatly reduced complexity and code duplication of many use case and service tests with `oop` macro for inheritance of harnesses
112638d
to
02d8c7c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Related to #857.
Introduced
DatasetRegistry
abstraction, encapsulating listing and resolution of datasets.Key changes:
DatasetRepository
is now limited to supportDatasetRegistry
and in-memory dataset dependency graphResolvedDataset
: a wrapper arroundArc<dyn Dataset>
, aware of dataset identityDatasetRegistryRepoBridge
utility connects both abstractions in a simple way for testing needspull
,push
,reset
,verify
,compact
, setting watermarkkamu ui
andkamu system api-server
now require to be backed by a db transactionpull
command, allowing to mix ingest/sync/transform operations of the same depth levelpull
flow, when a single non-recursive dataset is sent for processingoop
macro for inheritance of harnessesChecklist before requesting a review