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.

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

Enable Data Operations for Updates #552

Open
cristianvasquez opened this issue Oct 18, 2024 · 0 comments
Open

Enable Data Operations for Updates #552

cristianvasquez opened this issue Oct 18, 2024 · 0 comments

Comments

@cristianvasquez
Copy link

cristianvasquez commented Oct 18, 2024

Description

The objective of this task is to implement a mechanism that allows users to query data sources and schedule new transformation jobs based on those queries.

Features

  • Select Sources: Users should be able to create and define queries to select data sources according to various criteria, facilitating targeted data processing.
  • Schedule New Jobs: The sources identified through the queries can be utilized to initiate new transformation jobs, ensuring efficient handling of relevant data.
  • Prevent Concurrent Processing: Implement locking mechanisms during transformations to prevent concurrent processing and race conditions. Locks should be released once the transformation is complete or has failed, allowing for further actions.

Metadata Requirements

Ensure that the operational metadata has sufficient granularity and that the queries are expressive enough to support Data Operations effectively.

User Interface Proposal

Propose an interface or API that enables users to edit and inspect the results of the queries for scheduling new jobs. This interaction should be user-friendly and accessible through a UI or a Jupyter notebook, designed for users with basic Python knowledge.

Deliverables

  • Examples of Selection Queries: Provide examples of queries that can be used to select notices and batches.

  • Demonstrator: Create a demonstrator that showcases a common operation, illustrating how to select and schedule sources for transformation.

Constraints

  • During transformations, ensure that notices are locked to prevent concurrent processing and race conditions.
  • Clean up any obsolete or unused components in the codebase.
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

No branches or pull requests

1 participant