Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add release notes for PinnableSlice #2037

Conversation

maysamyabandeh
Copy link
Contributor

No description provided.

@facebook-github-bot
Copy link
Contributor

@maysamyabandeh updated the pull request - view changes

@facebook-github-bot
Copy link
Contributor

@maysamyabandeh updated the pull request - view changes

HISTORY.md Outdated
@@ -2,6 +2,9 @@
## Unreleased
### Public API Change
* Support dynamically change `stats_dump_period_sec` option via SetDBOptions().
* DB::Get in place of std::string accepts PinnableSlice, which avoids the extra memcpy of value to std::string in most of cases.
** PinnableSlice releases the pinned resources that contain the value when it is destructed or when ::Reset() is called on it.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should not use the subitems like using **
I think it won't be readable when we do the release https://github.com/maysamyabandeh/rocksdb/blob/66174bc720a0e213f74f399cebc56bc247856d0f/HISTORY.md

HISTORY.md Outdated
@@ -2,6 +2,9 @@
## Unreleased
### Public API Change
* Support dynamically change `stats_dump_period_sec` option via SetDBOptions().
* DB::Get in place of std::string accepts PinnableSlice, which avoids the extra memcpy of value to std::string in most of cases.
* PinnableSlice releases the pinned resources that contain the value when it is destructed or when ::Reset() is called on it.
* The old API that accepts std::string is deprecated
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you clarify what does "deprecated" mean? In this code base, we previously use "deprecated" as something already not supported. It's arguable whether we are using this word in a correct way, but I don't want people to get confused.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sure. Will remove the term deprecated.

@facebook-github-bot
Copy link
Contributor

@maysamyabandeh updated the pull request - view changes

@facebook-github-bot
Copy link
Contributor

@maysamyabandeh updated the pull request - view changes

@facebook-github-bot
Copy link
Contributor

@maysamyabandeh has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@maysamyabandeh updated the pull request - view changes - changes since last import

@facebook-github-bot
Copy link
Contributor

@maysamyabandeh has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants