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
[RFE] Support LDAP transactions (RFC 5805) #581
Comments
Comment from pspacek at 2015-03-31 13:02:02 One more use-case: |
Comment from pspacek at 2015-03-31 13:53:21 Hmm, we apparently forgot to add other use cases to this ticket too:
|
Comment from pspacek at 2015-03-31 19:39:30 Please be so kind and try to estimate scope of this request. List of use cases is still growing. Thank you! |
Comment from jcholast at 2015-03-31 20:01:51 Transactions would also help to make IPA more robust, as we often do more than one operation per command. |
Comment from pspacek at 2015-03-31 20:29:49 This reminds me a crash we had in the past: Sure, it was a bug in bind-dyndb-ldap, but it nicely ilustrares how these 'impossible' states of data can cause problems elsewhere. |
Comment from nkinder (@nkinder) at 2015-03-31 20:58:54 The scope is large, and we are in the middle of evaluating different backend database implementations. This would have to come after we finish the backend work, as I expect that a good amount of the work to support transactions would need to be redone. |
Comment from pspacek at 2015-04-01 14:09:24 I'm not sure what you mean with "redone" - maybe we have the same thing in mind :-) I'm bringing this request up now with a hope that requirements for (eventual) support for LDAP transactions could be taken into account during backend evaluation and backend work so the amount of re-working could be minimized. |
Comment from lkrispen (@elkris) at 2015-04-07 17:15:36 I think there are two sides of this, just implementing support for client transactions is one thing, it would be some considerable work, but could be done. |
Comment from pspacek at 2015-04-07 17:51:57 I understand that concern. My point of view that not implementing it in DS just shifts the problem to dependent components which later leads to multiple implementations of transaction logic in multiple components which is IMHO not a good result. Big lock over a whole transaction could be an easy way to implement it but AFAIK RFC 5805 does not require it. Transactions could be also implemented in different ways, e.g.:
Maybe I'm missing something but it seems that this approach limits locking only to processing |
Comment from lkrispen (@elkris) at 2015-04-07 19:39:12 ok, reading the rfc I think it can be done the way you suggest and should avoid longer lockouts |
Comment from pspacek at 2015-04-16 21:56:29 Two more notes:
|
Comment from pspacek at 2017-02-11 22:51:27 Metadata Update from @pspacek:
|
Comment from firstyear (@Firstyear) at 2017-02-13 01:44:40 I wouldn't mind client transactions, but I would worry about write transactions causing delays. |
Comment from firstyear (@Firstyear) at 2017-02-13 01:44:47 Metadata Update from @Firstyear:
|
Comment from firstyear (@Firstyear) at 2017-02-15 00:42:32 Metadata Update from @Firstyear:
|
Comment from mreynolds (@mreynolds389) at 2017-05-08 22:02:39 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2017-10-18 21:31:15 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2020-05-20 16:18:17 Metadata Update from @mreynolds389:
|
Closing for now since there no plans to implement this. |
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/581
For IPA it would be handy to use LDAP transactions as defined in RFC 5805.
If I read Trac and 389 web correctly, there is some internal support for transactions but I didn't see transactions between supportedExtensions.
This RFE comes from IPA ticket 3415.
The text was updated successfully, but these errors were encountered: