You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Arvind Prabhakar (JIRA)" <ji...@apache.org> on 2011/07/08 20:05:16 UTC
[jira] [Created] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
-----------------------------------------------------------------------------------------------------------------
Key: INFRA-3764
URL: https://issues.apache.org/jira/browse/INFRA-3764
Project: Infrastructure
Issue Type: Wish
Security Level: public (Regular issues)
Components: JIRA
Reporter: Arvind Prabhakar
The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062174#comment-13062174 ]
Gavin commented on INFRA-3764:
------------------------------
Please provide a project export from the Cloudera instance. We can't do a thing otherwise.
And next time, please mention this BEFORE we create your Jira space !! , people have started created issues on your new Jira instance, and they will get blown away by the import so make your people are aware of this.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Arvind Prabhakar (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arvind Prabhakar closed INFRA-3764.
-----------------------------------
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Assignee: Mark Thomas
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068215#comment-13068215 ]
Mark Thomas commented on INFRA-3764:
------------------------------------
I took a look and the REST API is publicly available (e.g. https://issues.cloudera.org/rest/api/2.0.alpha1/issue/FLUME-708). I suspect other APIs are also available (SOAP, XML-RPC). A lot of the 'manual' export/import could be automated and the full information is available. That would be a lot more work than just doing an export/sanitise/import though.
The data available via the REST API may also help convince the lawyers all you want to do is generate a copy of the information that is already publicly available in a form that is easy for Cloudera to create and the ASF to ingest.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Tony Stevenson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062873#comment-13062873 ]
Tony Stevenson commented on INFRA-3764:
---------------------------------------
As per Sqoop, please put them in your ~ on people, and secure them.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated INFRA-3764:
----------------------------------
Attachment: import-flume-from-cloudera.org.txt
Insructions for adding custom fields to a fresh jira. Many of these are likely already in apache jira.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Thomas reassigned INFRA-3764:
----------------------------------
Assignee: Mark Thomas
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Assignee: Mark Thomas
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072253#comment-13072253 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
The file flume-scurbbed.110728.zip is now sitting in my home directory (~jmhsieh) at people.o.a with 600 perms and is ready for an import attempt. User login id's should be modified before import because there will be clashes. As an example, my id is jon in that db (which is likely taken in apache's jira), but is jmhsieh in apache jira. Rough instructions for custom fields (of which many are already present on apache) are attached to this issue.
Please let me know if there are any problems/questions! Thanks!
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078285#comment-13078285 ]
Mark Thomas commented on INFRA-3764:
------------------------------------
Thanks for the mapping. I have re-processed the import with those mappings applied.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Assignee: Mark Thomas
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064502#comment-13064502 ]
Gavin commented on INFRA-3764:
------------------------------
I should have time to do this tomorrow if the export is ready, any chance of that or can I get an update as to when the likely time it will be available.
Thanks
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Thomas resolved INFRA-3764.
--------------------------------
Resolution: Fixed
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Assignee: Mark Thomas
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072690#comment-13072690 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
All files required for import should be now in place and we should be good to go.
FLUME-attachments.tgz is now sitting in my people.apache.org home dir (~jmhsieh) with 600 perms. I've successfully done a test import with the xml file found in flume-scrubbed.110728.zip with attachments in a fresh instance of JIRA. One addition required for import to fresh jira instance is enabling attachments.
There will be a warning about some attachments being missing. These files are actually missing from the cloudera.org version as well.
Please let me know if there are any problems/questions. Thanks!
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069554#comment-13069554 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
Preliminary check with cloudera policy folks came back saying that import/export exposing login ids and display names but scrubbing emails/passwords (Option 1) is feasible. There are however still some concerns bought up if we pursue this approach (some of which may get answered as we get our hands on an xml export):
* How are watchers and notifications handled? Is this just lost?
* As project admins, would we be able to map cloudera.org users from their cloudera.org jira login id to an apache jira login id? If not, could we get support from asfinfra to do this?
* Can you suggest some other projects that had a jira export/import happen? It would be nice if we could chat with them to see if there are other ramifications to consider.
On a more technical front, here are some notes from a chat with cloudera.org jira guru:
* I'll be getting an xml export and can look into scrubbing email/passwords, keeping handles/usernames.
* Having holes in the jira numbers does not cause problems. These should likely just present a "no perms" or "no issue present" message.
* Hacking DB directly (not via import/export mechanisms) is voodoo and should be avoided at all costs.
* Bumping jira number should be technically feasible by importing a modified xml export that starts from a higher number. As an example, if asfinfra imported a Flume jira export that only contains a FLUME-1000 issue, new issues would start at FLUME-1001. Our admin previously merged two different jiras by editing two exports and importing them to create a new single jira.
Finally, as a heads up, SQOOP and FLUME may choose to go different technical routes with this transition.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062201#comment-13062201 ]
Arvind Prabhakar commented on INFRA-3764:
-----------------------------------------
Gavin - thanks for your help with this. I will work on getting an export from Cloudera instance.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064819#comment-13064819 ]
Gavin commented on INFRA-3764:
------------------------------
Sure, no problem.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078649#comment-13078649 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
Tested jira and added issue and attachment here. https://issues.apache.org/jira/browse/FLUME-718.
Looks good to me. Thanks!
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Assignee: Mark Thomas
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069354#comment-13069354 ]
Arvind Prabhakar commented on INFRA-3764:
-----------------------------------------
Mark, Gavin -
Can you please confirm if option #3 is possible to implement? If adding fake issues is not acceptable, would it be possible to configure JIRA so that the starting issue number begins at a specified high value?
Thanks!
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072264#comment-13072264 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
Just realizes that this should hold off until I make the attachments for import available.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated INFRA-3764:
----------------------------------
Attachment: (was: import-flume-from-cloudera.org.txt)
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067848#comment-13067848 ]
Patrick Hunt commented on INFRA-3764:
-------------------------------------
Hi Gavin, thanks for all your help getting through this issue. I had a question related to your comment:
bq. I do not like the idea of you creating nearly 1000 duplicate issues with only comments pointing to the old issue tracker location and I strongly prefer you do not do that
how would you feel if new JIRAs were created that replicated the current state of the old JIRA (with matching numbers), but didn't contain a link back? I believe the concern Arvind highlighted is one of exposing user data, so rather than doing a fully export/import we would copy just the description from the old to the new jira (replicate component, state, etc...). There are ~278 open jiras in flume, so most of the issues would be marked as closed. Would that work for you?
If not, any suggestions how to resolve this. I believe the main concern of the Flume/Sqoop communities is that there be no confusion over what "FLUME-124" refers to.
Regards.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069731#comment-13069731 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
This link was mentioned in IRC as a pointer on how to "bump" the jira number to a higher value.
http://forums.atlassian.com/thread.jspa?messageID=257230742�
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076270#comment-13076270 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
Mark,
The jira import looks pretty good. I've looked up most of the "Disabled Import users" who have issues assigned to them (about 15), and mapped as many as I could to apache jira ids. Let me know if it is easier to take care of these with a re-import or if if this should be done from jira admin point of view (with a new issue).
I've placed a file with user mappings in my people.a.o home dir -- flume-user-mapping. It is csv formatted to basically look like this:
{quote}
flume_jon, jmhsieh
flume_esammer, esammer
{quote}
Thanks,
Jon.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Assignee: Mark Thomas
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064997#comment-13064997 ]
Gavin commented on INFRA-3764:
------------------------------
I dont understand the concerns of personal details of users.
A dump of the Cloudera Jira can be sent directly to me , to root@apache.org or placed in your home directory on people in a directory with 600 permissions.
Once the project has been imported , that dump will get destroyed, and the only users that get imported are only users assocaited with the projects being imported, with the rest of the users being ignored.
Another trick to providing me a dump with ONLY the project in question, is to create a copy of the current Cloudera jira instance, and delete all projects in the COPY except the Flume and Sqoop Jira projects, then export that COPY and let me have that (again securely), that way I only get details to do with those 2 projects and nothing else.
If I or other root admins at the ASF are not to be trusted with either export then fine, not much I can do about that. In which case your only option is to start again here and refer to your old issue tracker location
as you see fit in documentation. I do not like the idea of you creating nearly 1000 duplicate issues with only comments pointing to the old issue tracker location and I strongly prefer you do not do that, instead just create the appropriate documentation on your website making users/devs aware. Any genuine new issues that need to refer to old issues are fine, but do not create issues purely to link to the old location.
Let me know if I can get an export of the Cloudera Jira, an export of a copy of a reduced Jira instance containing just the projects, or neither, in which case I can close this issue as nothing for me to do.
Let me know please what you decide.
Thanks
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated INFRA-3764:
----------------------------------
Attachment: import-flume-from-cloudera.org.txt
Rough Instructions for creating custom fields required to import FLUME project into a fresh instance of JIRA.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065627#comment-13065627 ]
Arvind Prabhakar commented on INFRA-3764:
-----------------------------------------
Gavin, thanks for your response and suggestion. I can assure you that the issue is not regarding trusting the admins of ASF. Instead its more around the fact that we do not have explicit permissions for various users who will likely have their information shared. Cloudera must do due diligence in ensuring that no end-user agreements or laws are violated due to this move. Hence the delay.
That said, we are actively trying to find the right solution.
One question though: is it possible to tweak the ASF JIRA projects for Sqoop and Flume so that they start out from a higher issue number?
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Mark Thomas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13075962#comment-13075962 ]
Mark Thomas commented on INFRA-3764:
------------------------------------
Import complete. Flume is still read only. Once you indicate that all is OK, it can be made read/write.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Assignee: Mark Thomas
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Hsieh updated INFRA-3764:
----------------------------------
Comment: was deleted
(was: Insructions for adding custom fields to a fresh jira. Many of these are likely already in apache jira.)
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068115#comment-13068115 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
A group of us (medthomas, gmcdonald, _hen, jmhsieh, abayer, esammer) had a chat this afternoon in #asfinfra about options for porting jira information from cloudera.org to apache.org.
There seem to be a few main concerns:
* Preserving the name and description of particular issues.
* Preserving attribution and comment history of particular issues.
* Ambiguous issue names (FLUME-xxx on one jira vs the other) that will cause confusion in user communities and public histories.
* Restrictions from Cloudera's side about privacy and personally identifying information.
* ASF policy about link direction, jira history, attribution, and "issue wholeness".
We enumerated 4 options:
Option 1: Direct jira import from cloudera.org to apache.org with anonymized emails / passwords.
* Cloudera exports jira db
* Cloudera anonymizes emails and passwords (and publically exposed user names?)
* asfinfra imports using JIRA import/export mechanism.
* cloudera.org jira goes read-only afterwards, with open issues being closed with link pointing to Apache JIRA
+ Both JIRA's would be called FLUME/SQOOP, all history and comments preserved.
Option 2: New Apache jira with new name to avoid name clash.
* Create new jira called FLUME2/SQOOP2 or something like that to avoid naming clash/change pain.
* Export summary and description of existing open issues, and get them imported as new issues in the FLUME2/SQOOP2 jira.
* cloudera.org jira goes read-only afterwards, with open issues being closed with link pointing to Apache JIRA
Option 3: Bump apache jira number up artificially to avoid name clash.
* Check to see if ASF ok with artificially inflating jira number
* If ok, add remove issues until we get to a number like 1000.
* Export summary and description of existing open issues, and get them imported as new issues in the apache.org FLUME/SQOOP jira.
* cloudera.org jira goes read-only afterwards, with open issues being closed with link pointing to Apache JIRA
Option 4: "manually" port description to be consistent with cloudera.org jira.
* Manually copy summary and description from cloudera.org jira issues to corresponding apache.org jira. This is done so that the old jira issues numbers correspond to the numbers in both jiras.
* Backlink apache.org jira to point to cloudera.org jira.
* cloudera.org jira goes read-only afterwards, with open issues being closed with link pointing to Apache JIRA. All new comments and progress would happen on apache.org jira.
----
Option 1 seems to be the technically preferred option. It requires the least work by all parties but also faces the most difficult privacy/legal concerns from the Cloudera side.
Option 2 and Option 3 seem acceptable, IMO, Option 3 is preferred from podling-side but is not clear acceptable from the ASF policy side.
Option 4 would be sufficient and more ideal than option 2 or 3 but would also likely require the most effort on the cloudera side. It is also unacceptable by ASF from a policy stance.
* Whole issues should live in apache, so "backpointer" from apache.org jira to cloduera.org jira not ok without the summary, description, comments, and attribution. Note however, forward pointer from cloudera.org to apache.org is acceptable.
* This constraint essentially forces us back to Option 1.
Speaking for the folks in the Podling, we'd be willing to do "busy work" necessary port issues manually or inflate jira numbers.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064920#comment-13064920 ]
Arvind Prabhakar commented on INFRA-3764:
-----------------------------------------
Gavin, thanks for waiting. It turns out that there is really no way for us to do an export of Cloudera JIRA without including personal details of the users. Therefore we don't think the export and restore is a viable solution.
Instead we have the following proposal:
- Cloudera will keep the existing Sqoop and Flume JIRA projects available for forseeable future, but will turn them into read-only mode.
- We will create issues for these two projects on ASF JIRA where each issue would have a single comment that provides a link to the Cloudera JIRA.
As of this moment there are 234 issues for the Sqoop project and 704 issues for Flume project in Cloudera JIRA.
Your thoughts?
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064771#comment-13064771 ]
Arvind Prabhakar commented on INFRA-3764:
-----------------------------------------
Gavin, we are working through some issues regarding the export. I will post an update on where we are at by the end of the day today on this.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062284#comment-13062284 ]
Arvind Prabhakar commented on INFRA-3764:
-----------------------------------------
The export of Cloudera JIRA will be available on July 12, 2011. Please let me know if it is OK to attach it to this JIRA or is there another preferred means to deliver the export. Thanks.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Jonathan Hsieh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072129#comment-13072129 ]
Jonathan Hsieh commented on INFRA-3764:
---------------------------------------
Please let me know how or where I should put the scrubbed cloudera.org jira xml file.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069428#comment-13069428 ]
Sebb commented on INFRA-3764:
-----------------------------
To follow up from markt:
The JIRA GUI is also publicly available, for example:
https://issues.cloudera.org/browse/FLUME-708
This also clearly exposes the display names and login ids...
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-3764) Migrate JIRA project from
https://issues.cloudera.org/browse/FLUME to
https://issues.apache.org/jira/browse/FLUME
Posted by "Arvind Prabhakar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072134#comment-13072134 ]
Arvind Prabhakar commented on INFRA-3764:
-----------------------------------------
As per Tony's comment on INFRA-3763, the scrubbed export should be placed in your home directory securely, with 700 or more restricted permissions.
> Migrate JIRA project from https://issues.cloudera.org/browse/FLUME to https://issues.apache.org/jira/browse/FLUME
> -----------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-3764
> URL: https://issues.apache.org/jira/browse/INFRA-3764
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Arvind Prabhakar
> Attachments: import-flume-from-cloudera.org.txt
>
>
> The incubating Flume project was previously hosted by Cloudera and the issue tracking system was JIRA located at https://issues.cloudera.org/browse/FLUME. We would like to get the information in Cloudera hosted JIRA to be migrated to the ASF JIRA.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira