impala-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bharath Vissapragada <>
Subject Jira move to apache - Inputs required
Date Tue, 06 Sep 2016 01:27:42 GMT
Hello folks and mentors,

As a part of Impala's transition to ASF I'm working
<> on moving the existing
jira infra from to As a part of this move,
we need to map the content from existing jira instance to the one in
apache. This requires mapping the user names between these instances.
Recently I've sent out a form
for the users to submit this mapping. I only received responses from ~30
people so far.

Running some analysis on the current jira dump, we have the following stats.

(1) A total of ~750  users
(2) Out of these ~750 users, ~40 users have no kind of activity in the
jira. This activity includes creating/assignees/watching/commenting on the
(3) Out of the remaining ~750 users, ~250 people are just watchers for
jiras and do not have any other kind of activity.

Excluding just watchers, we have ~500 registered users with any kind of
real activity on the jira. Excluding the ~30 users who filled the above
form, we have ~470 people with some kind of activity which will lost in the
transition if no user mapping is provided.  Unfortunately this list is too
big to list to do any kind of manual verification and adding the entries
myself after verifying their apache ids.

Do you have any inputs on what can be done with these un-mapped users? We
have the following options

(a)  Create a dummy user and attribute all the content from these unmapped
users activity to it.

(b) Create a new jira id for these unmapped users. Lets stay if the user id
is john, we create john_impala (or something similar) by appending a random
string so that we don't map the content incorrectly to a user with similar
name on the apache jira.

I'm inclined towards (b) as it saves the user activity somewhere and can be
recovered by the users by providing the email id and resetting the password
if they are really interested in it. However it is unclear if they can
export it and import into their existing apache account if required and
hence not really sure if it will be of any use.

Mentors or committers or fellow devs, do you have any preferences on what
can be done in this case?

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