You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "bharath v (JIRA)" <ji...@apache.org> on 2019/02/10 20:55:00 UTC

[jira] [Resolved] (IMPALA-7346) Capture locality data for debug

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

bharath v resolved IMPALA-7346.
-------------------------------
    Resolution: Duplicate

IMPALA-5872 already addresses this. Jeszy, please reopen if you think otherwise. 

> Capture locality data for debug
> -------------------------------
>
>                 Key: IMPALA-7346
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7346
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: Impala 2.12.0
>            Reporter: Balazs Jeszenszky
>            Priority: Major
>
> With IMPALA-5872, it will be possible to capture and recreate query-specific details when things break.
> Currently there's no way to include data locality information in such test cases. For example, if the original issue was reported from a 150 node cluster, a reproduction on a 4 node test cluster is not guaranteed to be accurate.
> Having the ability to 'pin' a plan (and just export that along with metadata) is not a complete solution (it doesn't enable testing the planner itself).
> A way to do this could be to to dump locality data to tblproperties.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)