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

Improve FieldNotFound errors #4084

Merged
merged 1 commit into from
Nov 2, 2022
Merged

Conversation

andygrove
Copy link
Member

@andygrove andygrove commented Nov 2, 2022

Which issue does this PR close?

Closes #4083

Rationale for this change

It is confusing to get an error saying that field 't1.c0' does not exist but then states that field 't1.c0' is available. This happens when the qualifier is part of the field name and not in the qualifier field.

Before

No field named 't1.c0'. Valid fields are 't1.c0', ...

After

No field named 't1.c0'. Valid fields are 't1'.'c0', ...

What changes are included in this PR?

Change error message formating to put quotes around qualifier and name rather than around the qualified name, so 'foo'.'bar' rather than 'foo.bar'.

Are there any user-facing changes?

@andygrove andygrove added the api change Changes the API exposed to users of the crate label Nov 2, 2022
@github-actions github-actions bot added core Core datafusion crate logical-expr Logical plan and expressions sql labels Nov 2, 2022
Copy link
Contributor

@alamb alamb left a comment

Choose a reason for hiding this comment

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

Thanks @andygrove -- this looks like a great improvement

// lookup with unqualified name "t1.c0"
let err = schema.index_of_column_by_name(None, "t1.c0").err().unwrap();
assert_eq!(
"Schema error: No field named 't1.c0'. Valid fields are 't1'.'c0', 't1'.'c1'.",
Copy link
Contributor

Choose a reason for hiding this comment

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

looks a lot better to me 👍

@andygrove andygrove merged commit 8cd6129 into apache:master Nov 2, 2022
@andygrove andygrove deleted the better-fnf-error branch November 2, 2022 17:25
@ursabot
Copy link

ursabot commented Nov 2, 2022

Benchmark runs are scheduled for baseline = 1a5f6ab and contender = 8cd6129. 8cd6129 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-datafusion-commits is not supported on ec2-t3-xlarge-us-east-2] ec2-t3-xlarge-us-east-2
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on test-mac-arm] test-mac-arm
[Skipped ⚠️ Benchmarking of arrow-datafusion-commits is not supported on ursa-i9-9960x] ursa-i9-9960x
[Skipped ⚠️ Benchmarking of arrow-datafusion-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

Dandandan pushed a commit to yuuch/arrow-datafusion that referenced this pull request Nov 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api change Changes the API exposed to users of the crate core Core datafusion crate logical-expr Logical plan and expressions sql
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FieldNotFound when field is available
3 participants