Skip to content

chore: Refine the error message for List to non List cast#9757

Merged
Jefffrey merged 1 commit into
apache:mainfrom
comphead:chore
Apr 19, 2026
Merged

chore: Refine the error message for List to non List cast#9757
Jefffrey merged 1 commit into
apache:mainfrom
comphead:chore

Conversation

@comphead

Copy link
Copy Markdown
Contributor

Which issue does this PR close?

  • Closes #NNN.

Rationale for this change

Originally came from apache/datafusion-comet#3954

Getting the error message which hides the CAST target data_type

  Cause: org.apache.comet.CometNativeException: External error: Arrow error: Cast error: Cannot cast list to non-list data types

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

@github-actions github-actions Bot added the arrow Changes to the arrow crate label Apr 17, 2026
@Jefffrey Jefffrey merged commit f0dd1c2 into apache:main Apr 19, 2026
26 checks passed
Rich-T-kid pushed a commit to Rich-T-kid/arrow-rs that referenced this pull request Jun 2, 2026
# Which issue does this PR close?

<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases.
You can link an issue to this PR using the GitHub syntax.
-->

- Closes #NNN.

# Rationale for this change

Originally came from
apache/datafusion-comet#3954

Getting the error message which hides the CAST target `data_type`
```
  Cause: org.apache.comet.CometNativeException: External error: Arrow error: Cast error: Cannot cast list to non-list data types
```


<!--
Why are you proposing this change? If this is already explained clearly
in the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand
your changes and offer better suggestions for fixes.
-->

# What changes are included in this PR?

<!--
There is no need to duplicate the description in the issue here but it
is sometimes worth providing a summary of the individual changes in this
PR.
-->

# Are these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

# Are there any user-facing changes?

<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.

If there are any breaking changes to public APIs, please call them out.
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

arrow Changes to the arrow crate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants