I'm indexing the properties of content on the Everything Server from the client side and using FastSort, but I think the index isn't updating properly or it's very slow. The progress bar that usually appears during indexing isn't showing, so it seems to be idle. Is there a way to trigger a property update for updated files?
I suspected that might be the case, but after waiting a little while, it was reflected correctly, so there was no problem. Thank you.
Indexing the properties of content isn't updating properly or it's very slow
-
levinar_yh
- Posts: 7
- Joined: Fri Apr 10, 2026 10:02 pm
-
void
- Developer
- Posts: 20194
- Joined: Fri Oct 16, 2009 11:31 pm
Re: Indexing the properties of content isn't updating properly or it's very slow
Moved from Everything Server and Properties Search
Search for files with no content and force a property reindex:
Search for files with no content and force a property reindex:
- In Everything, search for:
!content: size: - Select all results. (Ctrl + A)
- Press Ctrl + F5.
-
therube
- Posts: 5804
- Joined: Thu Sep 03, 2009 6:48 pm
Re: Indexing the properties of content isn't updating properly or it's very slow
So eliminates 0-byte files.
I suppose you do that for efficiency reasons?
And if so, is there that much of an efficiency difference?
(And I suppose there would be more of a difference in particular as you're traversing a network.)
size:I suppose you do that for efficiency reasons?
And if so, is there that much of an efficiency difference?
(And I suppose there would be more of a difference in particular as you're traversing a network.)
-
void
- Developer
- Posts: 20194
- Joined: Fri Oct 16, 2009 11:31 pm
Re: Indexing the properties of content isn't updating properly or it's very slow
Yes, you can use just:I suppose you do that for efficiency reasons?
!content:But files with no size will naturally return no content.
Not really, indexing content from a file with no size will be quick.And if so, is there that much of an efficiency difference?