Provide users with more flexibility in the destination schema names

The destination schema name can't be configured by the users. For instance, for the Postgres connector, we have to choose a prefix (that is unique among ALL connectors). Then, the schema in which the data is located is used in the destination schema. For example, if I use my_prefix as the connector's prefix and my data is in the default public schema of my database, the destination schema will be: my_prefix_public. Having "_public" appended to my schema in my destination warehouse is not meaningful. I would much prefer to be able to assign a destination schema name to a source schema name.

A similar problem arises with the MySQL connector. If we have different databases (i.e., different connectors), we can't choose the same prefix. Choosing the same prefix would allow us to have consistency in schema names in the destination. Allowing users to use the same prefix across connectors, or even better, allowing users to choose their own destination schema name would provide users with much more flexibility in terms of schema naming convention.