Migrate Parquet Jira issues to GitHub
- Langage dominant
- Java
- Étoiles
- 3.1k
- Forks
- 1.6k
- Merge moyen
- 3 j 12 h
- PR mergées (30 j)
- 33
Description
Parquet community [discussed](https://lists.apache.org/thread/sc9zoxd3pd10odtgbrsh5qh7szhl2lhg) and decided ([parquet-\*,](https://lists.apache.org/thread/cxhkft17vx24x1znnvo47hbh6lpqdnrx) [parquet-cpp](https://lists.apache.org/thread/w6r0fwj42wvpm5yflwxhtm2ss3z2hrl3)) to migrate issue tracking from ASF Jira to issue tracker to GitHub issue trackers of individual Apache Parquet repositories with the following component mapping:
```java
jira/parquet-avro --> github/parquet-java
jira/parquet-cascading --> github/parquet-java
jira/parquet-cli --> github/parquet-java
jira/parquet-cpp --> github/arrow
jira/parquet-format --> github//parquet-format
jira/parquet-hadoop --> github//parquet-java
jira/parquet-mr --> github/parquet-java
jira/parquet-pig --> github/parquet-java
jira/parquet-protobuf --> github/parquet-java
jira/parquet-site --> github/parquet-site
jira/parquet-testing --> github/parquet-testing
jira/parquet-thrift --> github/parquet-java
```
Approximate migration script that will be applied was used for Apache Arrow migration and can be found [here](https://github.com/rok/arrow-migration/blob/main/move_jira_issues_to_github.ipynb). For more details on decisions that were made there in migration design see [Arrow migration issue](https://github.com/apache/arrow/issues/14542).
**Reporter**: [Rok Mihevc](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rok)
**Note**: *This issue was originally created as [PARQUET-2502](https://issues.apache.org/jira/browse/PARQUET-2502). Please see the [migration documentation](https://issues.apache.org/jira/browse/PARQUET-2502) for further details.*
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Commencez par le script de migration move_jira_issues_to_github.ipynb référencé et par l’issue de migration Arrow afin de comprendre la conception établie. Vérifiez les correspondances de composants Jira-to-GitHub indiquées, puis vérifiez que les issues sont migrées vers les dépôts et trackers individuels Apache Parquet décrits.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- github, java, jupyter-notebook
- Domaine
- developer-experience, tooling
- Type d'issue
- Refactorisation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 25/100