[
https://issues.apache.org/jira/browse/TEZ-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252074#comment-14252074
]
Prakash Ramachandran commented on TEZ-1864:
-------------------------------------------
the App.ready callback is guaranteed to fire only after advancereadyness is
called. so anything that requires async loading of config can be moved to
App.ready and advancereadyness called only when the data is available.
> Remove initializer
> ------------------
>
> Key: TEZ-1864
> URL: https://issues.apache.org/jira/browse/TEZ-1864
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Sreenath Somarajapuram
> Assignee: Sreenath Somarajapuram
> Fix For: 0.6.0
>
> Attachments: TEZ-1864.1.patch
>
>
> Initializer was added to control app init when not in stand alone mode. But
> turnout this part doesn't work as described in the documents (Initializer
> chaining cannot be paused by deferReadiness) hence removing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
