From 3ceaf762b9db8ec3a6c514fd8901d41c299d7573 Mon Sep 17 00:00:00 2001 From: AlbertZeyer Date: Sun, 3 Jan 2021 22:02:02 +0000 Subject: [PATCH] --- doc/forum/Reverse_index_key_to_list_of_file_paths.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Reverse_index_key_to_list_of_file_paths.mdwn diff --git a/doc/forum/Reverse_index_key_to_list_of_file_paths.mdwn b/doc/forum/Reverse_index_key_to_list_of_file_paths.mdwn new file mode 100644 index 0000000000..d6171bab6f --- /dev/null +++ b/doc/forum/Reverse_index_key_to_list_of_file_paths.mdwn @@ -0,0 +1,8 @@ +I understand from [here](https://git-annex.branchable.com/forum/Import_existing_files/#comment-29ece0290fa1314ca48caf8f435570d2) that there is no reverse index from a key to list of file paths pointing to that key (i.e. pointing to the value). + +`find . -lname '*'` would be an extremely slow operation on a big repo as it would go through the whole repo. And this is probably a common operation I frequently want to do. + +What if I would want to build one? How would I make sure that potential moves/renames will update the index? + +I understand from [here](https://git-annex.branchable.com/git-annex-metadata/) that you can attach meta information to a key (via `git annex metadata`). This sounds as it would be useful to contain such reverse information, right? +