crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Reid (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CRUNCH-456) Plan nodes with long names lead to invalid dot files
Date Tue, 05 Aug 2014 15:32:12 GMT

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

Gabriel Reid resolved CRUNCH-456.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.11.0
                   0.8.4

Pushed to master and 0.8 branches

> 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
>             Fix For: 0.8.4, 0.11.0
>
>         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)

Mime
View raw message