This project is archived. Its data is read-only. This project is read-only.
Relationship between name and namespace is confusing when adding a custom plugin
Mathieu Hinderyckx [wrote on Slack](https://meltano.slack.com/archives/CFG3C3C66/p1589494294100200): >>> I also find it confusing when adding an extractor via a custom tap (so in my case tap-mysql) what the identifiers (e.g. name and namespace) are. I used the command `meltano add --custom extractor tap-mysql` as the example on the homepage uses `tap-***` as well so I assumed the argument in that command was the type of tap I was adding. This isn’t the case, the argument is the identifier of the integration (so e.g. multiple mysql integrations would be added as `meltano add --custom extractor random-name-1, meltano add --custom extractor random-name-2` )? then the first line of the wizard says `The 'namespace' refers to the data source name.` As a result I thought this was the place where I was supposed to name the integration (random-name-1). Then the executable defaults to the namespace, while it would be better to default to the package name (e.g. tap-mysql). >>> @aroder [responded](https://meltano.slack.com/archives/CFG3C3C66/p1589498297104400?thread_ts=1589494294.100200&cid=CFG3C3C66): >>> I found this confusing as well. I think I could get used to it, but just changing the wording from "namespace" would help a lot I expected to run `meltano add --custom extractor <official-tap-name>` but as I learn more I see why that wouldn't be ideal >>>
issue