Let me explain.
Consider the scenario where you haven't added file length (duration) to the index. When you include "length:" in your search query, Everything searches for files with that specific length. However, if you have configured length to be indexed, the search behaves differently. It won't search for length within folders you've excluded from the index. This same thing happens for file contents indexing.
What I'd expect is that files that you have included in the index would appear instantly in search results, but Everything would continue searching through files not included in the index, similar to how it functions when you haven't set up a property index at all.
The same thing happens with columns. I have set a column "length" which would normally be populated slowly as Everything reads the files properties. But when I have set up for length to be included in the index and then I do a search in a folder that I haven't included in the index, the "length" column stays empty.
While I'm not sure if this is intended, I don't think this is how it should work. The point of indexing is for the search to be faster for specific properties in specific locations, not to prevent Everything from searching for those properties in other locations.
You don't have to have explicitly excluded a location for this behavior to appear. It also appears if you add an external hard drive that isn't part of the index.
Consider the scenario where you haven't added file length (duration) to the index. When you include "length:" in your search query, Everything searches for files with that specific length. However, if you have configured length to be indexed, the search behaves differently. It won't search for length within folders you've excluded from the index. This same thing happens for file contents indexing.
What I'd expect is that files that you have included in the index would appear instantly in search results, but Everything would continue searching through files not included in the index, similar to how it functions when you haven't set up a property index at all.
The same thing happens with columns. I have set a column "length" which would normally be populated slowly as Everything reads the files properties. But when I have set up for length to be included in the index and then I do a search in a folder that I haven't included in the index, the "length" column stays empty.
While I'm not sure if this is intended, I don't think this is how it should work. The point of indexing is for the search to be faster for specific properties in specific locations, not to prevent Everything from searching for those properties in other locations.
You don't have to have explicitly excluded a location for this behavior to appear. It also appears if you add an external hard drive that isn't part of the index.
Statistics: Posted by atiovalo — Sun Sep 01, 2024 1:39 am