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

[C++] Return more specific invalid Status in Take kernel #21774

Closed
asfimport opened this issue May 13, 2019 · 6 comments
Closed

[C++] Return more specific invalid Status in Take kernel #21774

asfimport opened this issue May 13, 2019 · 6 comments

Comments

@asfimport
Copy link
Collaborator

asfimport commented May 13, 2019

Currently the Take kernel returns generic Invalid Status for certain cases, that could use more specific error:

Reporter: Joris Van den Bossche / @jorisvandenbossche
Assignee: Ben Kietzman / @bkietz

Related issues:

PRs and other links:

Note: This issue was originally created as ARROW-5311. Please see the migration documentation for further details.

@asfimport
Copy link
Collaborator Author

Antoine Pitrou / @pitrou:
I think we could probably add a Status::IndexError on the C++ side to designate out-of-bounds conditions (when detected :-)). @wesm @xhochy what do you think?

@asfimport
Copy link
Collaborator Author

Wes McKinney / @wesm:
Seems OK to me, interested in other opinions

@asfimport
Copy link
Collaborator Author

Ben Kietzman / @bkietz:
Alternatively: we could just use KeyError

@asfimport
Copy link
Collaborator Author

Joris Van den Bossche / @jorisvandenbossche:
With IndexError, we could match typical behaviour on the python side (out of bound indices give IndexError in Python), but of course this is specific to Python, so that should not necessarily drive a change on the C++ side.

@asfimport
Copy link
Collaborator Author

Antoine Pitrou / @pitrou:
KeyError is more for column or field names etc.

@asfimport
Copy link
Collaborator Author

Antoine Pitrou / @pitrou:
Issue resolved by pull request 4317
#4317

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants