Thursday, January 4, 2018
Windows Search Windows 7 IS Broken indexer quits parsing after 39k
Windows Search Windows 7 IS Broken indexer quits parsing after 39k
This post has nothing to do with PL/SQL. Its about the Windows 7 search feature called "Windows Search" The bottom line is it stops indexing text files (maybe other types too) at about the 39K mark. This is NOT a problem with my set-up or configuration of Windows Search. I know this because I created a simple text file with a unique 10-digit number on each line. Those numbers which were towards the top of the file, say lines 1 thru 3414 (approximate, I dont recall the exact cut-off point) were properly indexed. I could type in any one of those numbers on the search bar and the proper file name which contained that number would be shown. Numbers towards the bottom of the text file, were NOT indexed. i.e. the Search erroneously found that no file contained that value.
So, you are not going mad, its truly broken. I searched for hours trying to find a solution, maybe a registry parameter, or something, ... but nothing. There was actually a registry parameter, but it was for the old indexer on windows XP. maxTextFilterBytes I finally gave up on trying to find a solution and instead split my files into smaller files.
If anybody finds a solution, please let me know.
