-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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-44759: [GLib] Add garrow_record_batch_validate() #45353
Conversation
|
Ah, I forgot to use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
…#45355) ### 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. * GitHub Issue: #45354 Authored-by: Hiroyuki Sato <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit be38880. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 6 possible false positives for unstable benchmarks that are known to sometimes produce them. |
### Rationale for this change [RecordBatch::Validate](https://arrow.apache.org/docs/cpp/api/table.html#_CPPv4NK5arrow11RecordBatch8ValidateEv) available in the C++ API. But, GLib doesn't support that method yet. ### What changes are included in this PR? This PR adds a validation method in the record-batch class. Before this change, the `Validate()` method was used in the `garrow_record_batch_new` implicitly. This PR removes it and adds it as a separate method. Users need to call `garrow_record_batch_validate()` explicitly by themselves. This is a backward incompatible change. ### Are these changes tested? Yes. ### Are there any user-facing changes? Yes. **This PR includes breaking changes to public APIs.** * GitHub Issue: apache#44759 Authored-by: Hiroyuki Sato <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
…cation (apache#45355) ### Rationale for this change apache#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. * GitHub Issue: apache#45354 Authored-by: Hiroyuki Sato <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
Rationale for this change
RecordBatch::Validate available in the C++ API.
But, GLib doesn't support that method yet.
What changes are included in this PR?
This PR adds a validation method in the record-batch class.
Before this change, the
Validate()
method was used in thegarrow_record_batch_new
implicitly.This PR removes it and adds it as a separate method. Users need to call
garrow_record_batch_validate()
explicitly by themselves. This is a backward incompatible change.Are these changes tested?
Yes.
Are there any user-facing changes?
Yes.
This PR includes breaking changes to public APIs.
garrow_record_batch_validate()
#44759