Skip to content

Conversation

@pengpeng-lu
Copy link
Contributor

No description provided.

@pengpeng-lu pengpeng-lu added the bug fix Change that fixes a bug label Oct 13, 2025
Copy link
Collaborator

@alecgrieser alecgrieser left a comment

Choose a reason for hiding this comment

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

Mostly looks good to me. I think I agree with the general approach here for the yaml tests, which is that we'll remove the various exclusions referencing #3206 in a subsequent minor version. Given that the new continuation logic went into 4.6.4.0, it would be nice to update the minor version to 4.8 as this feature is compatible with all 4.7 versions (but not all 4.6 or older versions). I believe @g31pranjal had a PR that was also going to target 4.8 (#3659). So, some amount of coordination is needed, either by having a third PR bump the version and merging both after this, or having one PR or the other make the minor version bump

synchronized (this) {
if (bytes == null) {
bytes = KeyValueCursorBase.Continuation.getInnerContinuation(new KeyValueCursorBase.Continuation(KeyValueCursorBase.Continuation.getInnerContinuation(baseContinuation.toBytes()), prefixLength, serializationMode).toBytes());
bytes = new KeyValueCursorBase.Continuation(KeyValueCursorBase.Continuation.getInnerContinuation(baseContinuation.toBytes()), prefixLength, serializationMode).toBytes();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think this is a mistake I made in the last PR. When we are in TO_OLD, it returns the same result as the modified version.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Okay, that makes sense. And walking through this, this only affected producing new continuations, not reading new continuations, so we should still be good to update the behavior to TO_NEW in this PR

Copy link
Collaborator

@alecgrieser alecgrieser left a comment

Choose a reason for hiding this comment

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

LGTM. It would still be good to coordinate on getting this into 4.8, but the substantive changes look good

synchronized (this) {
if (bytes == null) {
bytes = KeyValueCursorBase.Continuation.getInnerContinuation(new KeyValueCursorBase.Continuation(KeyValueCursorBase.Continuation.getInnerContinuation(baseContinuation.toBytes()), prefixLength, serializationMode).toBytes());
bytes = new KeyValueCursorBase.Continuation(KeyValueCursorBase.Continuation.getInnerContinuation(baseContinuation.toBytes()), prefixLength, serializationMode).toBytes();
Copy link
Collaborator

Choose a reason for hiding this comment

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

Okay, that makes sense. And walking through this, this only affected producing new continuations, not reading new continuations, so we should still be good to update the behavior to TO_NEW in this PR

@g31pranjal g31pranjal merged commit eb68481 into FoundationDB:main Oct 15, 2025
8 checks passed
g31pranjal added a commit that referenced this pull request Oct 15, 2025
Update minor version to `4.8` in response to #3659 and #3671.

These two changes activate features that are only intended to work with
version 4.7 and newer, so running in mixed mode with older versions is
not advised.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug fix Change that fixes a bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants