Hi Enrico,
Great questions. The primary objective of the CloudEvents specification was
to improve interoperability across technologies. The specification was
created to enable technologies to create bindings or adapters to support
interchange, and it seems to be gaining momentum. Azure and GCP hav
Devin,
thanks for bringing up this discussion.
I have one high level question: what is the goal that we want to achieve ?
something like:
1) Use CloudEvents format natively in Pulsar Schema registry, so that
Pulsar clients can register their schema using that format
2) Publish on some HTTP endpoin
Maybe this is something we could discuss as part of Pulsar 3.0?
Seems like there's a pretty big difference between SchemaInfo and
CloudEvents in terms of the fields.
CloudEvents requires:
id: String
source: URI-reference
specversion: String
type: String
and optionally:
datacontentt
Hi recently discovered the discussion around creating a CloudEvent binding
for Pulsar. https://github.com/cloudevents/spec/pull/237
It appears that Pulsar doesn't meet their minimum requirements due to lack
of a standard protocol. See https://github.com/cloudevents/spec/pull/254
Their comment say
