[jira] [Commented] (CRUNCH-456) Plan nodes with long names lead to invalid dot files

["Josh Wills (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CRUNCH-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086361#comment-14086361 ] 

Josh Wills commented on CRUNCH-456:
-----------------------------------

+1

> Plan nodes with long names lead to invalid dot files
> ----------------------------------------------------
>
>                 Key: CRUNCH-456
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-456
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Gabriel Reid
>            Assignee: Gabriel Reid
>         Attachments: CRUNCH-456.patch
>
>
> When a node in a job plan has a very long name (for example, a job that is reading from hundreds of different paths as a single input), an invalid dot file can be created. 
> Based on simple testing with the dot command (version 2.32 on Mac OS X), it seems that the node name limit in a dot file is 3000 characters. However, even this length of node name leads to basically unreadable dot files, so there should be some kind of abbreviation done on long node names before writing out job plan dot files.



--
This message was sent by Atlassian JIRA
(v6.2#6252)