infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-1972) Cayenne attachment field lost during migration
Date Thu, 02 Apr 2009 14:05:13 GMT

    [ https://issues.apache.org/jira/browse/INFRA-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695009#action_12695009
] 

Henri Yandell commented on INFRA-1972:
--------------------------------------

Grep needs to get a bit smarter as these are ids that get changed on migration.

So....

In old database:

Get entityId from propertyentry for a property_key of apache.assignedcopyright. This is the
id for the fileattachment table.
Get the issueid from the fileattachment table. Work out the pkey.
Record pkey, and fileattachment name, filesize, author, created, mimetype (or whatever subset
is enough to guarantee a match... maybe just created and author).

In new database:

Translate the recorded pkey to its issueid.
Identify the correct fileattachment id by matching on the attachment info recorded.
Generate SQL insert statement into propertyentry for each attachment id.

Then:

Shutdown JIRA.
Run script.
Start JIRA.

Do in test first.

> Cayenne attachment field lost during migration
> ----------------------------------------------
>
>                 Key: INFRA-1972
>                 URL: https://issues.apache.org/jira/browse/INFRA-1972
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: JIRA
>            Reporter: Henri Yandell
>            Priority: Blocker
>
> From Andrus on infra@ list:
> Regarding Cayenne Jira migration to Apache. Just noticed a small glitch: the attachment
flag "grant license to Apache ... " hasn't been migrated for the old attachments. E.g.:
> https://issues.apache.org/jira/browse/CAY-1164
> ErrorsInJCayenneTextPane.txt was attached after the migration, so it has the Apache feather;
the rest of the patches were attached before, so they don't. While a minor thing, this may
potentially have legal implications for the project I guess.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message