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

Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/04/27 16:09:13 UTC

[jira] [Closed] (FLINK-3835) JSON execution plan not helpful to debug plans with KeySelectors

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

Fabian Hueske closed FLINK-3835.
--------------------------------
    Resolution: Fixed

Fixed for 1.0.3 with 4a34f6f7342c3f40991a4d9e56f17811bad15d62 
Fixed for 1.1.0 with 80b09eaefe8f000f79f017ba822a631b8c29b5be 

> JSON execution plan not helpful to debug plans with KeySelectors
> ----------------------------------------------------------------
>
>                 Key: FLINK-3835
>                 URL: https://issues.apache.org/jira/browse/FLINK-3835
>             Project: Flink
>          Issue Type: Bug
>          Components: Optimizer
>    Affects Versions: 1.1.0, 1.0.2
>            Reporter: Fabian Hueske
>            Assignee: Fabian Hueske
>             Fix For: 1.1.0, 1.0.3
>
>
> The JSON execution plans are not helpful when debugging plans that include join operators with key selectors. For joins with hash join strategy, the driver strategy shows: {{"Hybrid Hash (build: Key Extractor)"}} where {{(build: Key Extractor)}} shall help to identify the build side of the join. However, if both inputs use KeySelectors, the build side cannot be identified.
> I propose to add the operator id to the build side information. The same issue applied for cross driver strategies.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)