Migrate Parquet Jira issues to GitHub
- Lingua principale
- Java
- Stelle
- 3.1k
- Fork
- 1.6k
- Merge medio
- 3g 12h
- PR unite (30g)
- 33
Descrizione
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.*
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia con lo script di migrazione move_jira_issues_to_github.ipynb indicato e con la issue di migrazione di Arrow per comprendere il design esistente. Controlla le mappature dei componenti Jira-to-GitHub elencate, quindi verifica che le issue vengano migrate nei singoli repository e tracker Apache Parquet descritti.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- github, java, jupyter-notebook
- Ambito
- developer-experience, tooling
- Tipo di issue
- Refactoring
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100