Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Backwards compatibility future plans

See original GitHub issue

Thank you for this great library. We have integrated CloudEvents in our system already and would like to start using this library too.

There were some breaking changes between v0.1 and v0.2 in the CloudEvents specs and I see that at the moment cloudevents/sdk-java is backwards compatible. (example)

But since these are versions before the major version v1.0, could you please tell me if you intend to always keep backwards compatibility in the future for any new versions of CloudEvents specs (for any future breaking changes)?

It is important for us to be able to gradually update our events with every new CloudEvent version. This results in a Kafka topic with multiple versions of CloudEvents. To avoid creating custom adapters, it would be great to only rely on the cloudevents/sdk-java library no matter which version of CloudEvents we use.

Thanks, Cristian

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:10 (8 by maintainers)

github_iconTop GitHub Comments

slinkydevelopercommented, May 6, 2020

IMO all major versions should be backwards compatible. Upgrading services to publish/consume new version of the CloudEvents is done one stream at a time. In a distributed system it is almost impossible to update all producers and consumers at the same time.

I’m sorry, I explained myself badly. Both sdk 1.x and 2.x supports cloudevents spec versions 0.3 and 1.0, so they should be able to talk each other, if that’s what you mean. APIs however will be different, in order to simplify the usage of the sdk and this unfortunately requires breaking the Java APIs

matzewcommented, Feb 11, 2020

I like the idea of deprecation.

and perhaps add some function to go from 0.x -> 1.0 as a conversion hook

Read more comments on GitHub >

github_iconTop Results From Across the Web

Nintendo won't commit to backwards compatibility for its next ...
Nintendo was asked about backwards compatibility on future hardware during a recent financial Q&A session.
Read more >
Xbox says there will be 'no more backwards compatible ...
Xbox has stated that the 76 games added to its backwards compatibility catalogue this week will be the last to be added.
Read more >
Microsoft confirms future backward compatibility plans for ...
Microsoft has reached out to Destructoid to expand a bit on its backward compatibility plans, and it's looking like good news.
Read more >
Is full backwards compatibility coming to PS5? This new ...
Sony may finally have a backwards compatibility solution to go head-to-head with Microsoft's popular Xbox Game Pass, as PlayStation ...
Read more >
Xbox Backwards Compatibility Is Teaching The Industry About ...
While Xbox has no plans to introduce any further backwards compatible titles from the original Xbox and Xbox 360 libraries in the future, ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found