You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yup, this is correct behavior. Kafka Connect ArangoDB does not create collections or databases at all -- it's your responsibility to do so beforehand. While it's theoretically possible to figure out what kind of collection you will need (edge collections are the ones with _to and _from fields so look for those fields), there's no way to predict what kind of indices you're going to need. Indices are super important to having a performant database and auto-creating collections enables users to forget about them.
That's definitely one of the next things I'd like to do with this. I've been working converting the existing docker compose development setup to use a clustered ArangoDB via Kubernetes first. The clustered form is much more difficult to use as a source system due to the architecture but starting with that first helps us avoid writing code into a corner.
I have below configuration
"transforms.cdc.type": "io.github.jaredpetersen.kafkaconnectarangodb.sink.transforms.Cdc",
"arangodb.database.name": "development",
Issue
Synch connector not creating collection on target database if that is not present .
The text was updated successfully, but these errors were encountered: