Skip to content

Conversation

@StevenLuMT
Copy link
Member

Descriptions of the changes in this PR:

Motivation

Using KeyValueStorage.Batch more rigorously: use KeyValueStorage.Batch, close it in finally.

This modification is not caused by a fault. I just found that the code is not written rigorously enough and is prone to bugs when I was combing through it.

Changes

  1. Every time use KeyValueStorage.Batch, close it in finally.

@StevenLuMT StevenLuMT changed the title Using KeyValueStorage.Batch more rigorously Every time use KeyValueStorage.Batch, close it in finally Apr 9, 2025
Copy link
Member

@hezhangjian hezhangjian left a comment

Choose a reason for hiding this comment

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

Can we put newBatch in the try statements?

@StevenLuMT StevenLuMT force-pushed the master-addFinalRelease branch from 151d81c to 22e4ecf Compare April 9, 2025 08:09
@StevenLuMT
Copy link
Member Author

Can we put newBatch in the try statements?

Good suggestion, I changed the way of coding it, let's take a look @hezhangjian

@StevenLuMT StevenLuMT merged commit c64dc8a into apache:master Apr 9, 2025
23 checks passed
@zymap zymap added this to the 4.18.0 milestone Apr 10, 2025
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.

5 participants