[
https://issues.apache.org/jira/browse/IMPALA-11609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Csaba Ringhofer updated IMPALA-11609:
-------------------------------------
Description:
https://github.com/apache/impala/blob/master/testdata/workloads/functional-planner/queries/PlannerTest/resource-requirements.test
grew very large ( > 6000 lines) and can fail due to several reasons, for
example changes in file size.
The idea is to split it to several parts, for example based on the file format.
The changes that creep in with dependencies are often file format specific, and
knowing which file format's test broke is often the first step in diagnosing
the issue.
Another benefit would be much easier fixing of tests locally. as the current
test needs a ~complete dataload, while it would be nicer to only need data load
for the file format whose tests broke.
was:
https://github.com/apache/impala/blob/master/testdata/workloads/functional-planner/queries/PlannerTest/resource-requirements.test
grew very large ( > 6000 lines) and can fail due several reasons, for example
changes in file size.
The idea is to split it to several parts, for example based on the file format.
The changes that creep in with dependencies are often file format specific, and
knowing which file format's test broke is often the first step in diagnosing
the issue.
Another benefit would be much easier fixing of tests locally. as the current
test needs a ~complete dataload, while it would be nicer to only need data load
for the file format whose tests broke.
> Split up resource-requirements.test
> -----------------------------------
>
> Key: IMPALA-11609
> URL: https://issues.apache.org/jira/browse/IMPALA-11609
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Reporter: Csaba Ringhofer
> Priority: Minor
> Labels: ramp-up
>
> https://github.com/apache/impala/blob/master/testdata/workloads/functional-planner/queries/PlannerTest/resource-requirements.test
> grew very large ( > 6000 lines) and can fail due to several reasons, for
> example changes in file size.
> The idea is to split it to several parts, for example based on the file
> format. The changes that creep in with dependencies are often file format
> specific, and knowing which file format's test broke is often the first step
> in diagnosing the issue.
> Another benefit would be much easier fixing of tests locally. as the current
> test needs a ~complete dataload, while it would be nicer to only need data
> load for the file format whose tests broke.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
