Replies: 1 comment
-
Hi, this issue is addressed by #784, it should be out in the next release! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I found this issue while playing with the solution provided in this SO post: Pandera validate get all valid rows
I'm using 0.9.0 at the time of this post and have added some data to the example and found 2 interesting things
This outputs:
I'm surprised to find that exc.data is the same as the original dataframe. I would've expected it to be the erroneous dataframe. This is more of a curiosity and not an issue since we can easily generate an error_df using the exc.failure_cases["index"]
error_df was capped to 10 rows even though there are other rows that didn't satisfy the check criteria of being between 1 and 2. Note the values 10 and 20 in the original dataframe. It appears that the location of these data points is the culprit for inclusion in the final filtered_df. Is there a way to retrieve the filtered_df and error_df so that they return the following rows?
Beta Was this translation helpful? Give feedback.
All reactions