Hello everyone .. I was reading through the docs (...
# troubleshooting
b
Hello everyone .. I was reading through the docs (https://docs.meltano.com/concepts/plugins/) and wanted to make sure that I can achieve the following: I have a one extractor (tap-mysql) that is configured to read from a specific db .. is it possible to add another section to meltano.yml file where I can configure it to read from another source? something like this - can I have another tap-mysql that is configured to read from the other db?
Copy code
environments:
- name: dev
- name: staging
- name: prod
  config:
    plugins:
      extractors:
      - name: tap-mysql
        config:
          host: $DB_HOST
          port: $DB_PORT
          user: $DB_USER
          database: $DB_NAME
          password: $DB_PASSWORD
          filter_dbs: $DB_NAME
        select:
        - "*-sessions.*"
        metadata:
          "*-sessions":
            replication-method: INCREMENTAL
            replication-key: updated_at
      loaders:
      - name: target-s3-csv
        config:
          aws_access_key_id: key
          aws_secret_access_key: access_key 
          s3_bucket: bucket
          s3_key_prefix: prefix
d
Sure, plugin inheritance feature would do the job (https://docs.meltano.com/guide/plugin-management#plugin-inheritance)
b
thanks a lot @Denis I. .. is it possible to inherit it from a specific version of tap-mysql? because I forked the repo and changed to my needs ..
Copy code
extractors:
  - name: tap-mysql
    variant: transferwise
    pip_url: git+<https://github.com/B2tGame/pipelinewise-tap-mysql-ONMO.git@master>
  - name: tap-mysql-cms
    inherit_from: tap-mysql
I guess this section
inherit_from: tap-mysql
references the most recent version not the one I forked and referenced in our github, right?
d
@bassel
inherit_from
just declares inheritance from the previously defined plugin. That means you can define any tap and than inherit it, and even re-define it again (https://docs.meltano.com/concepts/project#inheriting-plugin-definitions) And don’t forget to define custom (forked) plugin’s capabilities and settings (https://docs.meltano.com/guide/plugin-management/#custom-plugins)