Migrate Flight and FlightSql Proto Gen

Open
#89 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
git, go

Research direction

Start with format/Flight.proto and format/FlightSql.proto, especially the go_package declaration in Flight.proto. Trace the existing code-generation setup in arrow-go, then evaluate whether git submodules or buf can provide the definitions. Done means the Flight and FlightSql generated code is ported and builds without direct references to apache/arrow proto files.

Written by the indexing model from the issue text.

Description

Flight and FlightSql definitions are still in apache/arrow.

The go_package name will need to be updated to match this repo, and the actual codegen will need to be ported as well. We will no longer be able to use a direct reference to the .proto files, so we may need to use git submodules or a tool like buf in order to build the needed files.

Dominant language
Assembly
Stars
406
Forks
146
Avg merge
2d 8h
Merged PRs (30d)
93

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/arrow-go

All issues in apache/arrow-go

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.