[
https://issues.apache.org/jira/browse/TEZ-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625340#comment-14625340
]
Chris K Wensel commented on TEZ-625:
------------------------------------
A quick once over shows we only use "/" in the DAG name.
but one of the challenges all along has been the apparent conflation of ID with
display name.
both DAG and Vertex should have a user/framework supplied ID that can be used
when filtering logs, or by other tools that need to tie complex applications
together. it would be the glue between Cascading and Tez.
and both DAG and Vertex should have a human friendly display name. likely
supplied by the framework end-user to make life a bit easier outside of the
glue above (when looking at a UI).
that said, strong restrictions on the ID would make much sense so that it can
be used for various purposes, i.e. directory name on disk without munging.
but putting a restriction on the display name so the a UI doesn't have to make
it safe is questionable, or should not be held to to same degree. many UI
frameworks are really good at this already. also, the name should't translate
to an url, the ID should (thus stronger restrictions).
we use the slash in the DAG because of this conflation. but also prevent our
users from overriding with meaningful names, across the board, since we need
the glue (we have to guaranteed id uniqueness etc).
I can replace the "/" with a "-" but i think we are missing the real issue.
+1 if you provide a display name
> DAG/Vertex names should be restricted to using [A-Za-z0-9 -_:] and limited to
> a defined character limit
> -------------------------------------------------------------------------------------------------------
>
> Key: TEZ-625
> URL: https://issues.apache.org/jira/browse/TEZ-625
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Hitesh Shah
> Assignee: Saikat
> Labels: newbie
> Attachments: TEZ-625.1.patch, TEZ-625.2.patch, TEZ-625.3.patch,
> TEZ-625.4.patch, TEZ-625.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
