[jira] [Resolved] (IMPALA-4395) Write a test for IMPALA-4223

["Tim Armstrong (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Armstrong resolved IMPALA-4395.
-----------------------------------
    Resolution: Later

> Write a test for IMPALA-4223
> ----------------------------
>
>                 Key: IMPALA-4395
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4395
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.8.0
>            Reporter: Lars Volker
>            Priority: Major
>
> IMPALA-4223 still needs a test. The Jira contains steps to repro the issue and [this change|https://gerrit.cloudera.org/4828] contains directions on how to test this:
> {quote}We can try to do this in a custom cluster test. It needs to follow the steps outlined here: IMPALA-4223
> They require changes to the system limits to allow for larger cached files, and to the data nodes to increase the file cache as well, so they might be rather disruptive. Once these are changed we can write a custom cluster test to download, truncate, and upload files and run queries over them, checking that the correct log messages appear.
> Should we break this out into several Jiras / changes? The limits should be change in impala-setup, too. The datanode settings change will be required to integrate this into fuzz testing, too.{quote}
> Once IMPALA-4394 has been addressed we might want to look at this one and decide whether we still want to implement explicit tests, too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)