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

early type checks in RowConverter #3080

Merged
merged 4 commits into from Nov 10, 2022

Conversation

crepererum
Copy link
Contributor

Which issue does this PR close?

Closes #3077.

Rationale for this change

  1. There should be an easy way to check if a row format supports a certain type before conversion. This can be useful for DataFusion, where certain decisions are made during planning time.
  2. Improve RowConverter API by implementing "if you can create it, you can also feed data into it (modulo overflows)".

What changes are included in this PR?

  • RowConverter::supports_fields to check if fields are supported by row format
  • RowConverter::new can now fail
  • Small clean (remove unnecessary match arm)

Are there any user-facing changes?

BREAKING CHANGE: RowConverter::new can now fail

Decimal types are already handled by `downcast_primitive`.
Check supported row format types when creating the converter instead of
during conversion. Also add an additional method
`RowConverter::supports_fields` to check types w/o relying on an error.

Closes apache#3077.
@github-actions github-actions bot added the arrow Changes to the arrow crate label Nov 10, 2022
/// Check if the given fields are supported by the row format.
pub fn supports_fields(fields: &[SortField]) -> bool {
for f in fields {
let data_type = &f.data_type;
Copy link
Contributor

Choose a reason for hiding this comment

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

I think this can be simplified to something like

match data_type {
    DataType::Dictionary(_, v) => !DataType::is_nested(v.as_ref()),
    _ => !DataType::is_nested(data_type),
}

Copy link
Contributor

Choose a reason for hiding this comment

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

#3083 will make this even simpler

@tustvold tustvold added the api-change Changes to the arrow API label Nov 10, 2022
@tustvold
Copy link
Contributor

I took the liberty of simplifying this so it can make the arrow release

@tustvold tustvold merged commit 8d364fe into apache:master Nov 10, 2022
@ursabot
Copy link

ursabot commented Nov 10, 2022

Benchmark runs are scheduled for baseline = ed20bf1 and contender = 8d364fe. 8d364fe is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-rs-commits is not supported on ursa-thinkcentre-m75q] ursa-thinkcentre-m75q
Buildkite builds:
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
Labels
api-change Changes to the arrow API arrow Changes to the arrow crate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Row Format: API to check if datatypes are supported
3 participants