apache / apache/parquet-java

Migrate Parquet Jira issues to GitHub

Open
#1,703 0 comments 0 reactions 0 assignees View on GitHub
Component: Parquet Priority: Major Type: task
Dominant language
Java
Stars
3.1k
Forks
1.6k
Avg merge
3d 12h
Merged PRs (30d)
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.*

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the referenced move_jira_issues_to_github.ipynb migration script and the Arrow migration issue to understand the established design. Check the listed Jira-to-GitHub component mappings, then verify that issues are migrated to the individual Apache Parquet repositories and trackers described.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, java, jupyter-notebook
Domain
developer-experience, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.