https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #3 from David Kredba <kre...@kredba.cz> --- My system uses OpenRC. I started the indexing on KF 5.110, during the compilation it was paused. I am definitely not going to try to really use it (but I would like to!) if I will be told that after each KF5/6 upgrade touching Baloo it will need re-indexing. That would be terrible waste of energy and time. It should be programed the way that it will make needed internal changes of existing index file after each incompatible upgrade of Baloo internals. I am having plenty of literature in pdf and epub formats but was wrongly thinking it maybe a right size but from the output of the 'balooctl indexSize' command it may really suggest it went crazy again: File Size: 67,41 GiB Used: 2,95 GiB PostingDB: 3,47 GiB 117.860 % PositionDB: 1,76 GiB 59.766 % DocTerms: 1,51 GiB 51.211 % DocFilenameTerms: 48,49 MiB 1.606 % DocXattrTerms: 4,00 KiB 0.000 % IdTree: 9,99 MiB 0.331 % IdFileName: 52,75 MiB 1.747 % DocTime: 28,57 MiB 0.946 % DocData: 49,64 MiB 1.645 % ContentIndexingDB: 4,21 MiB 0.140 % FailedIdsDB: 0 B 0.000 % MTimeDB: 13,07 MiB 0.433 % I will try to reduce its size using the command 'mdb_copy -n -c index index.new'. Yes, it does it in 40 pcs batches. Thank you. -- You are receiving this mail because: You are watching all bug changes.
