infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (INFRA-16058) lists.a.o: id generation changed on around Sep 2 2017
Date Mon, 19 Feb 2018 02:03:00 GMT


Sebb commented on INFRA-16058:

It's both an internal ID (used for the ES database) and is also used as part of the Permalink
(i.e. public).
[That design choice is not ideal as the two usages have different requirements]

The behaviour of lists.a.o changed in Sep 2017 so it no longer follows the PM code.

Permalinks need to be permanent, so once published should never change.

As it stands, if lists.a.o should be unavailable for any length of time, Infra would not be
able to recreate the archives with the same Permalinks for all messages.

This issue has been discussed previously, but this is a new manifestation of the problem,
so needs documenting.

> lists.a.o: id generation changed on around Sep 2 2017
> -----------------------------------------------------
>                 Key: INFRA-16058
>                 URL:
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>            Priority: Major
> The id generation algorithm started producing different ids some time around Sep 2nd
> Before this time, mboxes downloaded from minotaur generate the same ids as lists.a.o
when loaded into a test database using the current trunk software.
> After this time, all the ids are different, although they have the same syntax.
> I have checked jmeter-dev/user and commons-dev/user, but I first noticed the problem
when trying to fix:
> When the freemarker-dev mbox for Feb 2018 was loaded into a test database I was unable
to find the test mail initially as it had a different id.
> It's a bit concerning that the generated ids should change.
> Was it a deliberate algorithm change (if so why was the syntax not changed) or was it
an unexpected side effect of some other software change?

This message was sent by Atlassian JIRA

View raw message