Skip to content

ARROW-9631: [Rust] flight should depend on arrow, not the other way around - #7892

Closed
andygrove wants to merge 4 commits into
apache:masterfrom
andygrove:ARROW-9631
Closed

ARROW-9631: [Rust] flight should depend on arrow, not the other way around#7892
andygrove wants to merge 4 commits into
apache:masterfrom
andygrove:ARROW-9631

Conversation

@andygrove

@andygroveandygrove commented Aug 3, 2020

Copy link
Copy Markdown
Member

The core arrow crate had a dependency on the arrow-flight crate, which doesn't make sense. Arrow should have minimal dependencies and should not depend on protocols or servers. Flight should depend on Arrow instead.

I also changed the name of lib from flight to arrow_flight to match the Cargo manifest. I did this because I ran into compilation issues but I think this is worth changing anyway since there is already a flight crate on crates.io (unrelated to Arrow). I can try and roll back this change though if there are objections.

@vertexclique

Copy link
Copy Markdown
Contributor

Before merging this, please take a look at mine: #7894
I simplified a bit of what happens when feature gates are enabled.

@github-actions

Copy link
Copy Markdown

@andygrove
andygrove marked this pull request as ready for review August 4, 2020 01:35
@andygrove

Copy link
Copy Markdown
MemberAuthor

@vertexclique I would prefer to have this PR only change the dependency between arrow and flight. This is quite a large change in itself. We can create follow-on PRs to make changes to feature gates.

@andygrove
andygrove requested a review from sunchaoAugust 4, 2020 01:42
@nevi-me

Copy link
Copy Markdown
Contributor

@vertexclique I would prefer to have this PR only change the dependency between arrow and flight. This is quite a large change in itself. We can create follow-on PRs to make changes to feature gates.

or rebase the feature-gating PR against this one when it's merged ...

@nevi-menevi-me left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Andy

@vertexclique

vertexclique commented Aug 4, 2020

Copy link
Copy Markdown
Contributor

@nevi-me@andygrove
ok so yeah what I can do moving forward is:

  1. create a ticket and rebase master on top.
  2. Finalize ARROW-9608: [Rust] Leaner feature gating for arrow in parquet #7873 to make parquet also use the raw arrow.

Sounds good?

kszucs pushed a commit to kszucs/arrow that referenced this pull request Aug 17, 2020
…round
The core `arrow` crate had a dependency on the `arrow-flight` crate, which doesn't make sense. Arrow should have minimal dependencies and should not depend on protocols or servers. Flight should depend on Arrow instead.
I also changed the name of lib from `flight` to `arrow_flight` to match the Cargo manifest. I did this because I ran into compilation issues but I think this is worth changing anyway since there is already a `flight` crate on crates.io (unrelated to Arrow). I can try and roll back this change though if there are objections.
Closesapache#7892 from andygrove/ARROW-9631
Authored-by: Andy Grove <andygrove@nvidia.com>
Signed-off-by: Andy Grove <andygrove73@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@andygrove@vertexclique@nevi-me