[
https://issues.apache.org/jira/browse/ARROW-18187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vibhatha Lakmal Abeykoon updated ARROW-18187:
---------------------------------------------
Description:
ARROW-18025 is a work in progress to expose Backpressure handling to Python
API. While working on options, found out that the python program doesn't exit
or return an error when invalid backpressure options are passed when the output
is not a RecordBatchReader or the PyTest raise is used to validate expected
errors.
In addition to this, if the `output_type` is set to `Table`, the observations
is the same.
Seems like this is out of scope of the ARROW-18025 effort and creating this
ticket to tackle the problem.
Way to reproduce,
Create a test case with invalid Backpressure options and set `output_type=Table`
Edited:
Make sure to remove the Python validation logic (backpressure validation) in
`_substrait.pyx`.
was:
ARROW-18025 is a work in progress to expose Backpressure handling to Python
API. While working on options, found out that the python program doesn't exit
or return an error when invalid backpressure options are passed when the output
is not a RecordBatchReader or the PyTest raise is used to validate expected
errors.
In addition to this, if the `output_type` is set to `Table`, the observations
is the same.
Seems like this is out of scope of the ARROW-18025 effort and creating this
ticket to tackle the problem.
Way to reproduce,
Create a test case with invalid Backpressure options and set `output_type=Table`
> [C++][Python] Substrait plan execution with invalid backpressure options
> causes erroneous exit.
> -----------------------------------------------------------------------------------------------
>
> Key: ARROW-18187
> URL: https://issues.apache.org/jira/browse/ARROW-18187
> Project: Apache Arrow
> Issue Type: Bug
> Reporter: Vibhatha Lakmal Abeykoon
> Assignee: Vibhatha Lakmal Abeykoon
> Priority: Major
>
> ARROW-18025 is a work in progress to expose Backpressure handling to Python
> API. While working on options, found out that the python program doesn't exit
> or return an error when invalid backpressure options are passed when the
> output is not a RecordBatchReader or the PyTest raise is used to validate
> expected errors.
> In addition to this, if the `output_type` is set to `Table`, the observations
> is the same.
> Seems like this is out of scope of the ARROW-18025 effort and creating this
> ticket to tackle the problem.
> Way to reproduce,
> Create a test case with invalid Backpressure options and set
> `output_type=Table`
> Edited:
> Make sure to remove the Python validation logic (backpressure validation) in
> `_substrait.pyx`.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
