yugabyte-db
https://github.com/yugabyte/yugabyte-db
C++
YugaByteDB is a high-performance, transactional database for building distributed cloud services. It currently supports Redis API (as a true DB), Cassandra API and SQL is coming very soon.
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
C++ not yet supported75 Subscribers
Add a CodeTriage badge to yugabyte-db
Help out
- Issues
- [YSQL][ConnMgr] Per-client sequence state: keep currval, lastval and the cached range across backend switches
- [YSQL][ConnMgr] pooled_with_curval_lastval: currval and lastval leak between logical clients, and nextval goes backwards for one client
- [YSQL][ConnMgr] session sequence mode: a rolled-back nextval, or one served from an already cached range, does not make the connection sticky
- [YSQL][ConnMgr] After setval, the same logical client's next nextval can come from another backend's stale cached range
- [YSQL][ConnMgr] ysql_conn_mgr_sequence_support_mode accepts any value, its RUNTIME tag has no effect, and the #27024 fallback only runs for a misspelled value
- [YSQL][ConnMgr] Add a yb_conn_mgr preload module and a YB message dispatch hook
- [YSQL][ConnMgr] Add sequence state provider hooks in sequence.c
- [YSQL][ConnMgr] Backend: report sequence state at transaction end and load it on attach
- [YSQL][ConnMgr] Hold each logical client's sequence state and load it when the client changes backend
- [YSQL][ConnMgr] Make the session sequence mode use per-client state instead of stickiness
- Docs
- C++ not yet supported