Evolutions of file indexing

[Alexander Stippich]

On Samstag, 14. Dezember 2019 10:50:13 CET Nate Graham wrote:
> On 12/14/19 10:24 AM, Matthieu Gallien wrote:
> > Hello,
> >
> > On Friday, December 13, 2019 9:00:15 PM CET Nate Graham wrote:
> >> I think it definitely makes sense to support both, as well as offer an
> >> option to force the use of old fashioned slow indexing if the user has a
> >> need for it. However I think we shouldn't be too eager about this,
> >> because we want the indexing case to work and we don't want people to
> >> just abandon it and always use the slow indexing. I think that it should
> >> be somewhat hidden away in the config window, with a warning attached to
> >> it that it will make indexing slow, and maybe even a request to file
> >> bugs explaining the reason for wanting to use it.
> >
> > Indeed, Elisa should handle most cases automatically and prefer use of
> > fast
> > index cache like Baloo.
> >
> > The configuration dialog could include a "troubleshooting" section that
> > would have the switch to force slow file system indexing with an
> > explanation and a report bug button.
> > That would be a neat idea. Users would be able to workaround problems and
> > we would get bug report to fix the issues.
>
> Yep, that's the sort of thing I had in mind.
>
> Nate
>
> _______________________________________________
> Elisa mailing list
> Elisa at kde.org
> https://mail.kde.org/mailman/listinfo/elisa

Hello everyone,

I agree with everything said so far. This would be a neat feature for Elisa.

I tried to implement a dynamic fallback based on baloo availability in
https://invent.kde.org/kde/elisa/merge_requests/21
but failed since currently the indexers cannot run concurrently. What I found
was that each indexer gets the full list of tracks in the database at startup
and the tracks get deleted when they are not found. This is the case for all
tracks that are indexed by the other indexer.

Best regards,
Alex