Skip to content

JAVA-2995 make CodecNotFoundException extend DriverException#1598

Merged
absurdfarce merged 3 commits into
apache:4.xfrom
smiklosovic:JAVA-2995
May 26, 2022
Merged

JAVA-2995 make CodecNotFoundException extend DriverException#1598
absurdfarce merged 3 commits into
apache:4.xfrom
smiklosovic:JAVA-2995

Conversation

@smiklosovic

Copy link
Copy Markdown
Contributor

No description provided.

@smiklosovic

Copy link
Copy Markdown
Contributor Author

@adutra would you mind to take a look? I just found this low-hanger as I was creating 3022 :D

@smiklosovic smiklosovic force-pushed the JAVA-2995 branch 4 times, most recently from ad646dc to 9f7fdc0 Compare May 25, 2022 10:53

@adutra adutra left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed in the Jira ticket, I'd like to see a note in the upgrade guide because this is in theory a breaking change, which is not allowed in a minor version.

@smiklosovic

Copy link
Copy Markdown
Contributor Author

@adutra please run the build again, I addressed your comments.

@adutra

adutra commented May 25, 2022

Copy link
Copy Markdown
Contributor

I pushed a few fixes for the upgrade guide. I think this is looking good but I'm still torn on the idea of including this breaking change in a minor. I will leave this open for now and wait for others to chime in, maybe @absurdfarce ?

@absurdfarce

Copy link
Copy Markdown
Contributor

I too have been going back and forth on the question of whether we roll this out in anything less than a major release, and I think ultimately I'd argue that we shouldn't. While the risk of surprising behaviour for this specific change may be fairly small it certainly is a possibility for some users... and I'd rather be very clear about that from a semver perspective.

@absurdfarce

Copy link
Copy Markdown
Contributor

After sleeping on this I'm reversing myself; I'm going to put this into 4.15.0 with a note in the upgrade guide. It's very consistent with how we've handled similar issues in the past, and going to 5.0 for this change seems like it would create more confusion (to say nothing of false expectations of major new features/improvements).

@absurdfarce absurdfarce merged commit decabed into apache:4.x May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants