Configurable output format parameters #813
Closed
lovromazgon
started this conversation in
General
Replies: 2 comments 3 replies
-
I personally prefer options 2 and 4, option 2 for the consistency between the names, and option 4 for the simplicity. |
Beta Was this translation helpful? Give feedback.
3 replies
-
This has been implemented and shipped in Conduit 0.6 🎉 Read more about the feature: https://conduit.io/docs/connectors/output-formats |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We want to make sure the user can configure what the destination connector produces (relevant issue: #531). Since we introduced SDK middleware this is the best place to add this so all destination connectors can benefit from it.
I already started working on this (relevant PR: ConduitIO/conduit-connector-sdk#48) but have a hard time deciding on the config parameters and their names. Here's what I want to achieve with these parameters:
The first parameter chooses the internal structure, the second chooses the encoding into bytes.
I identified a couple of options (currently the PR uses
option 1option 4):Option 1 - type and options separate
Option 2 - options nested
Option 3 - type and options together in one parameter
In this example options are separated from the value itself with a space.
Option 4 - both types together (MIME type)
Here we essentially use a MIME type with the structure like
type/subtype
.I'm interested in your opinions and ideas!
Beta Was this translation helpful? Give feedback.
All reactions