Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • A architecture
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Soong ETL ecosystem
  • architecture
  • Issues
  • #1
Closed (moved) (moved)
Open
Issue created Jan 19, 2019 by Soong ETL ecosystem@soongetlOwner

Naming: "Task" interfaces and classes

Soong has a concept (currently called a "task") which represents one step in a larger migration process. The "task" is the main object which would be managed by ETL tools - one would run a sequence of tasks to perform a complex migration (such as a full website) from one data store to another. Not all tasks are necessarily ETL processes - some might perform housekeeping (such as creating SQL tables in a destination database to be loaded). A single ETL task would be expected to migrate one specific type of data - articles, tags, user accounts, etc.

Is "task" the best language to use to describe this concept? Would "process" be better? Any other suggestions?

These are the current components:

interface TaskInterface: The base interface for all types of tasks, and the one which tools/applications would normally deal with directly.

interface EtlTaskInterface extends TaskInterface: Adds methods specific to ETL tasks.

class Task implements TaskInterface: A basic implementation of task management.

class EtlTask extends Task implements EtlTaskInterface: A basic implementation of ETL-specific task management. It should be noted that the migrate() method here is the linchpin of Soong - the place where the basic components (extractors, transformers, loaders) are constructed and evoked to execute a migration.

Assignee
Assign to
Time tracking