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

GH-45354: [GLib] Fix garrow_record_batch_validate() definied location #45355

Merged
merged 1 commit into from
Jan 27, 2025

Conversation

hiroyuki-sato
Copy link
Contributor

@hiroyuki-sato hiroyuki-sato commented Jan 27, 2025

Rationale for this change

#45353 implemented garrow_record_batch_validate() method. But it was the incorrect location.
We need to move the code location to use it as a C API.

What changes are included in this PR?

Move the garrow_record_batch_validate() location between G_BEGIN_DECLS and G_END_DECLS.

Are these changes tested?

Yes.

Are there any user-facing changes?

Yes.

@hiroyuki-sato hiroyuki-sato requested a review from kou as a code owner January 27, 2025 04:46
Copy link

⚠️ GitHub issue #45354 has been automatically assigned in GitHub to PR creator.

@kou kou changed the title GH-45354: [GLib] Move garrow_record_batch_validate place GH-45354: [GLib] Fix garrow_record_batch_validate() definied location Jan 27, 2025
Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

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

+1

@kou kou merged commit 4408e2b into apache:main Jan 27, 2025
11 of 12 checks passed
@kou kou removed the awaiting review Awaiting review label Jan 27, 2025
@github-actions github-actions bot added the awaiting merge Awaiting merge label Jan 27, 2025
@hiroyuki-sato hiroyuki-sato deleted the topic/fix-record-batch-location branch January 27, 2025 06:06
Copy link

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 4408e2b.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 13 possible false positives for unstable benchmarks that are known to sometimes produce them.

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.

2 participants