You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Patrick Wendell (JIRA)" <ji...@apache.org> on 2014/03/30 06:33:15 UTC

[jira] [Updated] (INFRA-7518) Fix naming import error from Spark JIRA

     [ https://issues.apache.org/jira/browse/INFRA-7518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Wendell updated INFRA-7518:
-----------------------------------

    Summary: Fix naming import error from Spark JIRA  (was: Fix naming import error from JIRA)

> Fix naming import error from Spark JIRA
> ---------------------------------------
>
>                 Key: INFRA-7518
>                 URL: https://issues.apache.org/jira/browse/INFRA-7518
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: JIRA
>            Reporter: Patrick Wendell
>
> The JIRA importing incorrectly mapped every instance of my account to the account of someone named "Patrick Cogan". I think the issue is that my username in our existing JIRA was the same as his username in the ASF Jira and probably the heuristics in the import tool assume this is a match.
> The comments and work in our Jira represent a log of several years of work, so if it all possible I'd really appreciate if if these could be fixed. I checked around and I don't think this issue affected any of the other major Spark contributors.
> The way to fix this would be writing a SQL query directly against the JIRA database that replaces the user "patrick" with the user "pwendell" in the Spark project.
> I found instances where other projects hit the same issue:
> https://issues.apache.org/jira/browse/INFRA-3292
> In our case this doesn't seem to have affected this many users - but I'll keep an eye out if others are affected.



--
This message was sent by Atlassian JIRA
(v6.2#6252)