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

The `GET_NEXT_VERSION` is not supported by MD entries update/delete #713

Closed
bochaco opened this issue Dec 5, 2018 · 0 comments · Fixed by #1119
Closed

The `GET_NEXT_VERSION` is not supported by MD entries update/delete #713

bochaco opened this issue Dec 5, 2018 · 0 comments · Fixed by #1119

Comments

@bochaco
Copy link
Member

@bochaco bochaco commented Dec 5, 2018

Analogously to the feature provided by the NFS emulation with the GET_NEXT_VERSION constant for updating and deleting files, it would be desirable to also support it by the MD API to update and delete entries.

@bochaco bochaco added the enhancement label Dec 5, 2018
@bochaco bochaco added this to Needs triage in SAFE Client Libs - vNext via automation Dec 5, 2018
@m-cat m-cat self-assigned this Jan 15, 2019
@m-cat m-cat removed their assignment Jul 31, 2019
@m-cat m-cat self-assigned this Dec 18, 2019
m-cat added a commit to m-cat/safe_client_libs that referenced this issue Dec 18, 2019
m-cat added a commit to m-cat/safe_client_libs that referenced this issue Dec 18, 2019
m-cat added a commit to m-cat/safe_client_libs that referenced this issue Jan 3, 2020
m-cat added a commit to m-cat/safe_client_libs that referenced this issue Jan 3, 2020
SAFE Client Libs - vNext automation moved this from Needs triage to Closed Jan 6, 2020
lionel1704 added a commit that referenced this issue Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
2 participants
You can’t perform that action at this time.