but trying to understand how that works - like wha...
# troubleshooting
w
but trying to understand how that works - like what all is inherited? just the variant I selected?
and do I have to inherit from an existing extractor?
v
Have you tried it? 😄
w
lol - @visch - haven't found a way to do it
v
Do you have an example meltano.yml file and error we could look at to help you?
w
so it looks like if I change the pip url after i run the add extactor that will work
Copy code
### TEMPLATE (SQLSERVER) 
  - name: tap-mssql
    variant: buzzcutnorman
    pip_url: git+<https://github.com/BuzzCutNorman/tap-mssql.git>

### DW #1 (SQLSERVER) 
  - name: tap-mssql--dw1
    inherit_from: tap-mssql
    variant: buzzcutnorman
    pip_url: git+<https://github.com/BuzzCutNorman/tap-mssql.git>
so that works as expected
Copy code
### SQLSERVER CQV LOGSHIPPER -- WORKS
  - name: tap-mssql-diff
    inherit_from: tap-mssql
    variant: wintersrd
    pip_url: tap-mssql
that doesn't work -- which is what I got when I ran
Copy code
meltano add extractor tap-mssql-diff --inherit-from tap-mssql --variant wintersrd
so I think that command should have put the pip url into the yaml file for wintersrd but instead it just put
tap-mssql
I'm guess that because wintersrd is the default
however if I go and find the pipurl for wintersrd and put that in the pip_url that does seem to work
v
1. Can you share the full
meltano.yml
file you have 2. The error you're getting and the command you run to get that error
w
Copy code
- name: tap-mssql--diff
    inherit_from: tap-mssql
    variant: wintersrd
    pip_url: git+<https://github.com/wintersrd/pipelinewise-tap-mssql.git>
so all good now I think - just not behaving as expected by placing the wrong thing in the pip url when using the CLI -- but I do understand its an edge case
I think the CLI assumed I my intital inherit_from was using the default wintersrd and put tap-mssql into the pipurl. This doesn't work if your inherit from is the non default (like buzzcutnorman variant)
a
Yes I have experienced this too with target-postgres
w
I'm creating an issue
@andy_carter ^