Repository navigation
DBAL Config Session Changes - #1518
Conversation
Includes Config Session, Locking, Transaction Size Limit.
|
@adyeung @anand-kumar-subramanian @kwangsuk @ayelrod This SONiC documentation PR has HLD descriptions for code PR sonic-net/sonic-mgmt-common#108 |
What is a use case of "config session"? |
It is to provide a way to configure/querying a candidate-datastore in addition to the already supported running-datastore, as mentioned on this line. |
|
|
||
| This will be enhanced for the following: | ||
|
|
||
| * Provide a way for querying a *candidate-datastore*, instead of the redis server's CONFIG_DB database selection. This can be supported in one of several ways: |
There was a problem hiding this comment.
In continuation to my earlier question , can you provide a usecase of "candidate datastore" in the community?
There was a problem hiding this comment.
In continuation to my earlier question , can you provide a usecase of "candidate datastore" in the community?
We are trying to get the Configuration Session functionality in. These DB Access Layer changes are one foundation for Configuration Session support.
The terms are defined in RESTCONF, and NETCONF protocols here.
Includes Config Session, Locking, Transaction Size Limit.