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
Pipes are able to reference data types by their name (e.g. text-plain, avro-binary and so on). When a data type is component specific (e.g. aws2-s3:application-cloudevents) the data type name may use the component scheme as a prefix.
Users run into issues because they are using the component scheme as a prefix when referencing a data type but the Pipe specification must use "scheme" and "format" properties when referencing a data type
Problem
The Pipe specification uses "scheme" and "format" properties when referencing a data type:
…nces
- Allows data type references in Pipes to use component scheme as a prefix in the transformer name (e.g. format=aws2-s3:application-cloudevents)
- This is in addition to specifying "scheme" and "format" properties on the data type reference
…nces
- Allows data type references in Pipes to use component scheme as a prefix in the transformer name (e.g. format=aws2-s3:application-cloudevents)
- This is in addition to specifying "scheme" and "format" properties on the data type reference
- Allows data type references in Pipes to use component scheme as a prefix in the transformer name (e.g. format=aws2-s3:application-cloudevents)
- This is in addition to specifying "scheme" and "format" properties on the data type reference
Requirement
Pipes are able to reference data types by their name (e.g. text-plain, avro-binary and so on). When a data type is component specific (e.g. aws2-s3:application-cloudevents) the data type name may use the component scheme as a prefix.
Users run into issues because they are using the component scheme as a prefix when referencing a data type but the Pipe specification must use "scheme" and "format" properties when referencing a data type
Problem
The Pipe specification uses "scheme" and "format" properties when referencing a data type:
Proposal
We should also allow to use the component scheme as a prefix. Something like
Open questions
No response
The text was updated successfully, but these errors were encountered: