-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove record_batch! macro once upstream updates #13037
Comments
take |
I will keep an eye on the update and do the required change if it is okay. |
Sounds great! It will probably take a while as we have to wait for the upstream to make a release, and then DF to update to that release version. |
Should this be done? I saw this #12846. I can delete create_array and record_batch macros to make it use the same as in arrow. Also they are also not identical:
|
I recommend:
|
Will do as recommended. Thanks @alamb |
I've took another look into this and tried to change it but the issue is that macro in arrow only accepts array literals such as:
As far as I've tried, achieving the same is not possible with macro in arrow crate in the same way. That's why I think we can update the macro in arrow to the same in datafusion and then deprecate it here. But since I'm not Rust expert not sure on this. Arrow: https://github.com/apache/arrow-rs/blob/c4dbf0d8af6ca5a19b8b2ea777da3c276807fc5e/arrow-array/src/record_batch.rs#L153-L174 datafusion/datafusion/common/src/test_util.rs Lines 338 to 357 in bfabd48
cc @timsaucer @alamb |
Thanks for looking at this @buraksenn I thought we more or less ported the macro from DataFusion to Arrow so the different is surprising, but I haven't had a chance to look into it in detail. |
Is your feature request related to a problem or challenge?
Follow on to apache/arrow-rs#6588
Once arrow-rs releases and we update datafusion, we can remove the record_batch! macro.
Describe the solution you'd like
Remove and use upstream method instead.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: