From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: Threading/searching problem
Date: Fri, 3 Aug 2018 19:20:56 +0000 [thread overview]
Message-ID: <20180803192056.5swqcf67bsdxbpg6@dcvr> (raw)
In-Reply-To: <20180803182647.GA28438@chatter>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hi, all:
>
> Something I came over today that seems to be wonky. I was trying to find
> this message:
>
> https://lore.kernel.org/lkml/CA+55aFz5EWE9OTbzDoMfsY2ez04Qv9eg0KQhwKfyJY0vFvoD3g@mail.gmail.com/
>
> It's from Linus about WireGuard, so I searched for it:
>
> https://lore.kernel.org/lkml/?q=torvalds+wireguard
OK, WireGuard is in the body, there...
> And it doesn't show up, which is really odd. I see some of the other search
> strings also not show up:
>
> https://lore.kernel.org/lkml/?q=DL_FLAG_AUTOREMOVE_SUPPLIER
>
> it's in today's message:
> https://lore.kernel.org/lkml/53f9f939dbce11e1c96986ff41f29dd6e41b9220.camel@nxp.com/
Likewise, DL_FLAG_AUTOREMOVE_SUPPLIER only appears in the body.
> I'm wondering if it's related to incremental index fixes, but the cover
> letter mentions deleted messages, which we haven't been doing.
Since you're on mda, I think it's related to the mda + message body
indexing fixes I posted:
https://public-inbox.org/meta/20180729093441.5250-1-e@80x24.org/
I think it takes about 3-4 hours to reindex my local LKML
archives on my fastest SSD (way longer on a slower SSD),
so it might only take around 2 hours onthe machine used for lore.
> There's also an issue of threading which has been irking some people on
> LKML. If you look at this message again:
>
> https://lore.kernel.org/lkml/CA+55aFz5EWE9OTbzDoMfsY2ez04Qv9eg0KQhwKfyJY0vFvoD3g@mail.gmail.com/
>
> You will notice that PI tries to build a subject-based thread all the way
> back to 2008 and gives up somewhere in 2015. This makes it impossible to
> navigate that message thread.
Oops. We'll have to tweak the ordering for giant threads to
favor newer messages. Gotta run for a bit but should be done
today.
> Any help would be greatly appreciated. If anyone wants a copy of Xapian/git
> I can provide it on request (they are large!).
I've got my own; but it might be worth looking into supporting
remote indices a feature of Xapian.
next prev parent reply other threads:[~2018-08-03 19:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 18:26 Threading/searching problem Konstantin Ryabitsev
2018-08-03 19:20 ` Eric Wong [this message]
2018-08-03 19:38 ` Konstantin Ryabitsev
2018-08-05 6:04 ` [PATCH] view: distinguish strict and loose thread matches Eric Wong
2018-08-05 8:19 ` [RFC] overidx: preserve `tid' column on re-indexing Eric Wong
2018-08-05 21:41 ` Eric Wong
2018-08-06 20:05 ` [PATCH] view: distinguish strict and loose thread matches Konstantin Ryabitsev
2018-08-06 20:10 ` Konstantin Ryabitsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180803192056.5swqcf67bsdxbpg6@dcvr \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).