SQUAT indexes?

[+archive.info-cyrus at utdallas.edu]

On Fri, 16 Jan 2004 +archive.info-cyrus at utdallas.edu wrote:

> On Sat, 17 Jan 2004, Craig Ringer wrote:
>
> > Nils Vogels wrote:
> > > Why not just run squatter from master ?
> > >
> > > This works deliciously over here:
> > >
> > > EVENTS {
> > >    ...
> > >  # Let's squat em
> > >  squat_user    cmd="squatter -r -s user" period=1440
> > >    ...
> > > }
> >
> > That indexes all user mailboxes, including the trash etc. I only want to
> > automatically index INBOXES, plus any other mailboxes the user requests.
>
> Could always use the new squat annotation.  That's also... tasty?
>
> localhost> mboxconfig user.amos squat true
>
> Yum, yum.

Actually, I forgot that the squat annotation is inherited:

     -a   Only create indexes for mailboxes which have the shared
          /vendor/cmu/cyrus-imapd/squat annotation set to "true".

          The value of the /vendor/cmu/cyrus-imapd/squat  annota-
          tion is inherited by all children of the given mailbox,
          so an entire  mailbox  tree  can  be  indexed  (or  not
          indexed)  by setting a single annotation on the root of
          that tree with a value of "true" (or  "false").   If  a
          mailbox  does  not have a /vendor/cmu/cyrus-imapd/squat
          annotation set on it (or does not  inherit  one),  then
          the mailbox is not indexed.  In other words, the impli-
          cit value of /vendor/cmu/cyrus-imapd/squat is "false".


Shame because I thought this might be handy to just squat the
inboxes.  So, this loops right back into the discussion of
"squatter -s user.%"  ;-)

I wonder if maybe there could/should be additional annotations,
one for recursive, one for not.  So maybe, to be backwards
compatible, "/squat" would be recursive, but "/squatthis" would
not?

More tasty?

-- 
Amos