[Schemas] Handle name conflicts about conduit HOT 3 OPEN

Our team discussed this today. Here are the solutions we discussed and the conclusion.

TL;DR

Conduit will make sure all schema names are unique by adding the connector ID and/or the pipeline ID to the name that a connector developer provides (which is going to be the collection name in most cases).

Long version:

Possible solutions

1. Make every name unique
   1a. Connector developers provide a name, that is "made unique" by Conduit by adding a prefix/suffix.
   1b. Connector developers don't provide a name.
2. Use "namespaces" (each connector gets one)

Discussion:

1. Make every name unique
   1a. Connector developers provide a name. Conduit "makes it unique" by adding a prefix/suffix.
   Pros: makes the connector code a bit more clear (by showing what a schema is referring to)
   Cons: The actual name is different. The original name is not valid anymore.

   1b. Connector developers don't provide a name. Conduit generates a random/unique name.
   Pros: Simple implementation.
   Cons: The schema registry internally is not well organized. This can done in a limited way by having structured names (e.g. pipeline ID + connector ID + schema name). The actual name is different. The original name is not valid anymore.

2. Use "namespaces" (each connector gets one)
   Confluent's SR has schema contexts. Works more or less like a prefix.

   Pros: intuitive way to organize schemas, easier cleanup
   Cons: the franz-go client doesn't support contexts as "first class citizens". What CURRENTLY can be done is to change the base URL, but that would mean one client per connector. We might also want to change the client to support schema contexts.

Conclusion

We're choosing 1a for the following reasons:

1. It's possible to dictate a structure of the IDs, which makes it easier to identify which schemas belong to which pipelines, which in turns makes cleanup easier.
2. A connector developer's involvement is minimal.

While it does require some care on a connector developer's behalf, because the actual schema name is different, it's still not a big problem, because the parameter name and docs will call it out.

from conduit.

The mentioned solution relies on a connector being able to identify themselves (the combination of the pipeline/connector ID and the name that a developer provided guarantees schema subject uniqueness). Tokens can be used for that. Lovro wrote down some thoughts how to do that: #1701 (comment)

from conduit.

@lovromazgon and I were discussing the implementation of this. There are a few points:

1. We're not quite happy with schema.Create() returning a schema with a different name, but there's no good solution.
2. Eventually, we'd like to organizes schemas into contexts.
3. There might be cases where a user (not necessarily a connector developer) might want to use an existing schema from an external schema registry. Prefixing the subject name with the connector ID always (as in the proposed solution) makes that impossible. So we're going to make that configurable.
4. A user will be able to:
   • specify a custom prefix
   • use the default prefix (connector ID)
   • use no prefix at all (subject name is exactly as in the connector code, e.g. the collection name)
5. The above will be make possible through 2 configuration parameters:
   • one to enable the prefix
   • one to specify the prefix
6. The default behavior is to use the connector ID as the prefix
7. Now the plot twist: we'll use context instead of prefix since we plan to organize schemas into contexts in future.

from conduit.