Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

kdb-rm /: does not remove everything #2550

Closed
markus2330 opened this issue Mar 27, 2019 · 6 comments
Closed

kdb-rm /: does not remove everything #2550

markus2330 opened this issue Mar 27, 2019 · 6 comments

Comments

@markus2330
Copy link
Contributor

markus2330 commented Mar 27, 2019

Cascading removal of keys with globbing (_) seems to fail.

Steps to Reproduce the Problem

kdb setmeta spec/tests/_/hello default world
kdb rm -r /tests

Expected Result

That afterwards all keys are removed.

Actual Result

The key is still there. Due to #2456 the output is:

kdb ls /tests
#> /tests/_/hello

But the actual key is of course spec/tests/_/hello

System Information

  • Elektra Version: master

Further Log Files and Output

@markus2330 markus2330 added the bug label Mar 27, 2019
@kodebach
Copy link
Member

This may be a problem in ksCut, because kdb rm -r /tests should still include everything below spec/tests (and therefore spec/tests/_/hello), no matter if globbing is used or not.

It may also be the problem that I encountered once (and never again), where somehow a cascading key ended up in the stored dump file and I had to manually remove it.

@markus2330
Copy link
Contributor Author

Thank you for the confirmation and the tip where the problem is.

@stale
Copy link

stale bot commented May 5, 2020

I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@stale stale bot added the stale label May 5, 2020
@stale stale bot removed the stale label May 5, 2020
@markus2330
Copy link
Contributor Author

To be solved with #3742

@stale
Copy link

stale bot commented Apr 2, 2022

I mark this issue stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping the issue by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@stale stale bot added the stale label Apr 2, 2022
@stale
Copy link

stale bot commented Apr 16, 2022

I closed this issue now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@stale stale bot closed this as completed Apr 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants