Haris Osmanagić

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 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...

@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...

Comment by @lovromazgon: > Not for this PR, but I'll mention it before I forget. I realized that having a builtin schema registry could create the expectation that the [`avro.decode`](https://conduit.io/docs/processors/builtin/avro.decode)...

@mm-zacharydavison Thanks for reporting the issue! You're right in that the lifecycle methods shouldn't be an issue. I'll look into this. Btw, we've updated the SDK in the Elasticsearch connector....

> Is there potentially a compatibility issue with the protobufs used? > Do I need to also build latest conduit from master? I don't _think_ that should be needed, but...

Gotcha... So with that, and also with the fact the log destination is working, we can be 99% sure it's the ES connector, and I don't think using latest Conduit...

@mm-zacharydavison Please try the latest `main` branch from the ES connector now, the issue should be fixed. If it works for your case too, I'll cut a release.

No problems at all, you helped us more with filing the issue and the very detailed instructions how to reproduce it. :muscle:

Btw, the issue was the following: The Postgres connector is encoding all records using Avro. The ES connector got those records in their encoded form (hence that error message about...