impala-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Apple <jbap...@cloudera.com>
Subject Fwd: Impala JIRA is moving to apache.org
Date Mon, 06 Mar 2017 16:29:54 GMT
As part of Impala's move to use ASF infrastructure, Impala JIRA will be
moving from <https://issues.cloudera.org/issues/?jql=project%20%3D%20Impala>
to <https://issues.apache.org/jira/issues/?jql=project%20%3D%20Impala>. The
planned move date is March 13. On that date, the cloudera.org Impala JIRAs
will be read-only for a few hours. If the move is successful, links like <
https://issues.cloudera.org/browse/IMPALA-3221> will redirect to <
https://issues.apache.org/jira/browse/IMPALA-3221>, just like <
https://issues.cloudera.org/browse/KUDU-22> redirects to <
https://issues.apache.org/jira/browse/KUDU-22>. We hope to get this done by
the end of the day on March 13.

If you want all of your notifications to continue, you need to set up an
issues.apache.org/jira account with the same email address as your
issues.cloudera.org account.

If you choose not to do so, the transfer procedure will create a username
for you like banana_impala_e4fa, assuming your issues.cloudera.org username
is "banana". The "e4fa" is a string of four pseudorandom hex characters
depending on the username. You should be able to claim that username by
using the "forgot my password" form when you try and sign-in with that name
on issues.apache.org/jira on March 14; it should email you a password reset
link.

There is a possibility the migration will fail; in that case it will be
rolled back, hopefully before writes on <
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Impala> open,
and this procedure will be tried again at a later date.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message