Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARROW-17055: [Java][FlightRPC] Don't duplicate generated Protobuf classes between flight-core and flight-sql #13596

Conversation

KBambrick1
Copy link
Contributor

flight-core and flight-sql jars delivering same class names.

It seems that the classes generated by Flight.proto gets generated in both flight-sql and flight-core jars. Since these classes get generated in flight-core, and flight-sql is dependent on flight-core, can the generation of Flight.java and FlightServiceGrpc.java be removed from flight-sql and instead rely on it to be pulled directly from flight-core.

@github-actions
Copy link

@github-actions
Copy link

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

Copy link
Member

@lidavidm lidavidm left a comment

Choose a reason for hiding this comment

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

Interesting, so it seems the Flight SQL protobufs are actually generated in the core Flight project. That's probably OK, though technically we may want to separate them.

@lidavidm
Copy link
Member

@github-actions crossbow submit java-jars

@github-actions
Copy link

Revision: aca9bc2

Submitted crossbow builds: ursacomputing/crossbow @ actions-856d89d413

Task Status
java-jars Github Actions

@lidavidm lidavidm changed the title ARROW-17055: [Java][FlightRPC] flight-core and flight-sql jars delive… ARROW-17055: [Java][FlightRPC] Don't duplicate generated Protobuf classes between flight-core and flight-sql Jul 13, 2022
@lidavidm lidavidm merged commit 1fd3593 into apache:master Jul 13, 2022
@lidavidm
Copy link
Member

Thank you @KBambrick1!

@ursabot
Copy link

ursabot commented Jul 14, 2022

Benchmark runs are scheduled for baseline = 0855046 and contender = 1fd3593. 1fd3593 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️0.48% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.0% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.07% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 1fd35939 ec2-t3-xlarge-us-east-2
[Finished] 1fd35939 test-mac-arm
[Failed] 1fd35939 ursa-i9-9960x
[Finished] 1fd35939 ursa-thinkcentre-m75q
[Finished] 08550465 ec2-t3-xlarge-us-east-2
[Failed] 08550465 test-mac-arm
[Failed] 08550465 ursa-i9-9960x
[Finished] 08550465 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

Sign up for free to 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.

None yet

3 participants