Re: akonadi indexing agent configuration (was: Re: How to disable mail indexing with Akonadi search)

Am Donnerstag, 11. Februar 2016, 11:49:02 CET schrieb Martin Steigerwald:
> Am Montag, 8. Februar 2016, 16:52:48 CET schrieb Daniel Vrátil:
> > > And its set there already: initialIndexingDone=true
> > > 
> > > So I don´t get why it reindexes all the stuff again.
> > > 
> > > 61     KConfig
> > > config(Akonadi::ServerManager::addNamespace(QStringLiteral("baloorc")));
> > > 62     KConfigGroup group = config.group("Akonadi");
> > > 
> > > Okay, I at least found where it initializes a complete sync:
> > > 
> > > 130 void Scheduler::scheduleCompleteSync()
> > > 
> > > But I bet the changes to access maildir items without storing them into
> > > DB
> > > initially need to be done in maildir resource, not in indexing. But I
> > > can
> > > at
> > > least check whether it respects the "do not index" this folder setting.
> > > I
> > > told it to leave my biggest folders alone, yet still it hogs down my
> > > system
> > > like crazy.
> > 
> > I'd like it to be generic, so it first needs to be implemented to the
> > client libraries (and ofc supported inside the server), then adapt
> > maildir to use the new API/mechanism/whatever we introduce.
> 
> Sounds like something more complex. Do you see anything "junior" in there I
> maybe can help you with?
> 
> > > I looked a bit in the akonadi-search repo, file scheduler.cpp. And I
> > > think
> > > I may have a chance with
> > > 
> > > 71     //Trigger a full sync initially
> > > 72     if (!group.readEntry("initialIndexingDone", false)) {
> > > 73         qCDebug(AKONADI_INDEXER_AGENT_LOG) << "initial indexing";
> > > 74         QMetaObject::invokeMethod(this, "scheduleCompleteSync",
> > > Qt::QueuedConnection);
> > > 75     }
> > > 
> > > setting initialIndexDone to true in some config file. Hmmm, still
> > > baloorc!?
> > 
> > Historical reasons :) That's the last piece I did not migrate yet
> > somewhere
> > into Akonadi. Another junior task :)
> 
> I think about picking up with this one first as a junior task.
> 
> Where would a good place for this be? In agent configuration Sandro pointed
> out (.config/akonadi/agent_config_akonadi_indexing_agent)? I bet thats
> handled by Akonadi itself and the agent can access it somehow?

Hmmm, nope, other agents have resource configs in different files like

~/.config/akonadi_imap_resource_0rc

(formerly in ~/.kde/share/config)

So the configuration seems to be split somehow for whatever reason. Seems the 
agent config is just to tell Akonadi which agents exist.

> I´d like to add three basic options to enable/disable
> 
> - mail indexing
> - contact indexing
> - note indexing
> 
> well, as one does usually not have many contacts or notes maybe just the
> mail indexing option would be enough.
> 
> I´d also like to check whether Akonadi search respects the setting whether a
> folder should be indexed or not. I have the impression that it doesn´t. It
> would be very helpful if I can just tell it to leave the huge LKML folders
> and some other folders alone for now.
> 
> I´d just create a branch to make these changes and then learn to stuff it
> into a review request with Phabricator once I got something workable? (My
> last review requests have been with Reviewboard still). Or maybe make two
> changes
> 
> 1) Migrate the initialIndexing option
> 
> 2) Then add mail indexing option
-- 
Martin
_______________________________________________
KDE PIM users mailing list
Subscription management: https://mail.kde.org/mailman/listinfo/kdepim-users