Actually that is not true. The vertexId is just based on the order in which the vertices are created and added to a DAG. This need not be topological. To get a correct topology, one would need to do a full pass over the whole DAG.
— HItesh On Dec 22, 2014, at 5:59 PM, Jeff Zhang <[email protected]> wrote: > Hi Prakash, > > Regarding the vertex order, can we do the sorting on the client side ? > VertexId is in the topological order, we can sort vertex by its id. > > > > On Sat, Dec 20, 2014 at 1:27 AM, Prakash Ramachandran < > [email protected]> wrote: > >> Thanks Jeff for the feedback, my reply inline. >> >> On 12/19/14 1:22 PM, Jianfeng (Jeff) Zhang wrote: >> >>> Hi Folks, >>> >>> I tried the tez-ui, and found couple of issues. There might already be >>> jiras to track these. Just list here in case we have no jira for that. My >>> OS is mac, and use firefox. >>> >>> 1. The app link to yarn web ui is not correct. The correct link should >>> be >>> http://localhost:8088/cluster/app/application_1418638652536_0011, but >>> actually it is >>> http://localhost:8088/cluster/app/tez_tez_application_1418638652536_0011 >>> >> >> will be fixed for 0.6.0 >> >> >>> 2. On the vertex tab, I think vertices should be sorted by its >>> topological >>> order. VertexId may already be in that kind of order, need to double >>> check. >>> >> >> agree with ordering, i thought it was in topological order too. another >> reason why it is this way is >> that currently yarn timeline server REST api does not allow a sorting >> order. >> >> >>> 3. Start_time & Finish_time are only in the level of minute, would it be >>> better in seconds ? >>> >> >> will be adding in TEZ-1870 >> >> >>> 4. The Status dropdown list in the tab of vertex & taskattempt tab always >>> been "ALL" even I change it. >>> >> >> created a jira TEZ-1875. >> >>> >>> 5. I think it would be more appropriate to allow fuzzy matching, at >>> least >>> for the DAG name textbox. I found Counters has fuzzy matching feature, >>> but >>> others don't have. >>> >> >> again this is a restriction posed by the current yarn rest api. for >> counters it does it on >> the client side. >> >>> >>> 6. Can we add vertex_name on the tab of task & taskattempt ? IMO It would >>> make more sense to allow user to search on vertex_name, because it is >>> user-facing, while vertexId is an Id which is generated by Tez internally, >>> user don't know which vertex that vertexId refer to. >>> >> agree that it would be useful - will plan for the 0.6.1 release. tez-1795 >> tracks this. >> >> >>> >>> Best Regards, >>> Jeff Zhang >>> >>> >> >> -- >> CONFIDENTIALITY NOTICE >> NOTICE: This message is intended for the use of the individual or entity >> to which it is addressed and may contain information that is confidential, >> privileged and exempt from disclosure under applicable law. If the reader >> of this message is not the intended recipient, you are hereby notified that >> any printing, copying, dissemination, distribution, disclosure or >> forwarding of this communication is strictly prohibited. If you have >> received this communication in error, please contact the sender immediately >> and delete it from your system. Thank You. >> > > > > -- > Best Regards > > Jeff Zhang
