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

Allow for custom Singer catalogs #314

Open
judahrand opened this issue Jan 21, 2020 · 1 comment
Open

Allow for custom Singer catalogs #314

judahrand opened this issue Jan 21, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@judahrand
Copy link
Contributor

I guess in the context of Pipelinewise a Singer 'stream' is a 'table'. It would be nice to be able to edit the Pipelinewise 'tables' to not pull all columns. Is this something which could be supported?

@koszti
Copy link
Contributor

koszti commented Jan 24, 2020

This is currently not supported and every column selected automatically. In case of schema changes newly added columns are picked up automatically as well.

Defining which columns to extract is basically possible but requires some development. A possible solution would be to define it in the tap YAML files in this format:

schemas:
  - source_schema: "my_db"        # Source schema (aka. database) in MySQL/ MariaDB with tables
    target_schema: "my_db"        # Target schema in the destination Data Warehouse
    tables:
      - table_name: "table_one"
        replication_method: "LOG_BASED"   # One of INCREMENTAL, LOG_BASED and FULL_TABLE
        columns:
          - column_one
          - column_two

@koszti koszti added the enhancement New feature or request label Jan 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants