Rneaming a folder prompts all of its content's properties to be reindexed

Discussion related to "Everything" 1.5.
santilli
Posts: 32
Joined: Tue Apr 30, 2024 7:05 am

Rneaming a folder prompts all of its content's properties to be reindexed

Post by santilli »

I have some properties flagged to be indexed on selected folders, but if a folder within that selected path range is renamed, all of the files inside that folder are reindexed. The files are not modified, so to me this behavior seems undesired. As I rename folders, I have hundreds and hundreds of GBs being reindexed when none of those files were changed.

If this is a deliberate decision, or a limitation, please let me know.

On this note about reindexing properties without need, I have suggested in the past if it would be possible to keep indexed properties stored in the database for a period of time, so that when files are deleted and restored it doesn't have to go through all properties again. I may have suggested this in the past but I don't remember.
void
Developer
Posts: 20194
Joined: Fri Oct 16, 2009 11:31 pm

Re: Rneaming a folder prompts all of its content's properties to be reindexed

Post by void »

Thanks for the feedback santilli,

Everything will keep the properties for files in a folder when the folder is renamed or moved.
However, the properties are invalidated.

Everything must regather these properties to apply inclusion and exclusion filters.
I will look into improving this in a future version for 'content' properties where there's no full-path inclusion/exclusion filters.

Everything will not keep properties of deleted items.
santilli
Posts: 32
Joined: Tue Apr 30, 2024 7:05 am

Re: Rneaming a folder prompts all of its content's properties to be reindexed

Post by santilli »

void wrote: Thu Aug 06, 2026 5:47 am Thanks for the feedback santilli,

Everything will keep the properties for files in a folder when the folder is renamed or moved.
However, the properties are invalidated.

Everything must regather these properties to apply inclusion and exclusion filters.
I will look into improving this in a future version for 'content' properties where there's no full-path inclusion/exclusion filters.

Everything will not keep properties of deleted items.
thanks for the reply, i have decided to ditch all content properties, it's not worth it on my use case. since i handle mostly video files, and i am already gathering size and length, instead of relying on md5 or sha-256 to find duplicates now i simply run

Code: Select all

dupe:size;length
and although i'm aware this is not 100% reliable due to false positives, they are rare enough.

now this also solves my issue with restored files, as metadata properties are virtually instantaneous.