[
https://issues.apache.org/jira/browse/TEZ-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214553#comment-14214553
]
Prakash Ramachandran commented on TEZ-1781:
-------------------------------------------
- {code:title=app.js} dag.get('vertices').findBy('vertexName',
vertexName).additionalInputs {code} might be not defined. for ex Summation
vertex in wordcount ex does not have additionalInputs
- {code:title=dag_vertices.js} inputId: row.get('inputs.content.0.id') {code},
will be undefined, so the link may become invalid (second link)
- {code:title=TimelineRestAdapter.js}var userPayload =
JSON.parse(data.userPayloadAsText){code} userPayloadAsText may be undefined if
tez.runtime.convert.user-payload.to.history-text is false. causing parse error
- router.js - should App.TezAppConfigsRoute be still present?
can you also test once with tez.runtime.convert.user-payload.to.history-text
set to false.
> Configurations view ~ New design
> --------------------------------
>
> Key: TEZ-1781
> URL: https://issues.apache.org/jira/browse/TEZ-1781
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Sreenath Somarajapuram
> Assignee: Sreenath Somarajapuram
> Attachments: TEZ-1781.1.patch
>
>
> 1. Display all configurations without pagination.
> 2. Move configurations from dag to vertex.
> 3. Configurations of a vertex will be available inside the inputs tab.
> 4. Move configurations diaplay to a generic code.
> 5. Input/configuration link in vertices table: Like points to inputs table of
> the respective vertex in case of multiple vertex inputs, and directly to the
> configurations view when the vertex have just one input.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
