issues  

Messages by Thread

• [jira] [Created] (TEZ-1164) Only events for tasks should be buffered in Initializing state Bikas Saha (JIRA)
• [jira] [Updated] (TEZ-1148) Exception thrown when old MapRunnable implementation is specified for a MapProcessor vertex Mariappan Asokan (JIRA)
  • [jira] [Updated] (TEZ-1148) Exception thrown when old MapRunnable implementation is specified for a MapProcessor vertex Mariappan Asokan (JIRA)
  • [jira] [Updated] (TEZ-1148) Exception thrown when old MapRunnable implementation is specified for a MapProcessor vertex Hitesh Shah (JIRA)
• [jira] [Created] (TEZ-1163) Tez Auto Reducer-parallelism throws Divide-by-Zero Gopal V (JIRA)
• [jira] [Created] (TEZ-1162) Tez leaks CodecPool buffers Gopal V (JIRA)
• [jira] [Updated] (TEZ-1161) Minor fix to Simple History Logs, to allow mining by MR tasks Gopal V (JIRA)
  • [jira] [Updated] (TEZ-1161) Minor fix to Simple History Logs, to allow mining by MR tasks Gopal V (JIRA)
  • [jira] [Updated] (TEZ-1161) Minor fix to Simple History Logs, to allow mining by MR tasks Gopal V (JIRA)
• [jira] [Created] (TEZ-1161) Minor fix to Simple History Logs, to allow mining by MR tasks Gopal V (JIRA)
• [jira] [Updated] (TEZ-1019) Re-factor routing of events to use common code path for normal and recovery flow. Bikas Saha (JIRA)
• [jira] [Created] (TEZ-1160) Allow users to set non-tez configs on client side Ramya Sunil (JIRA)
• [jira] [Assigned] (TEZ-1148) Exception thrown when old MapRunnable implementation is specified for a MapProcessor vertex Mariappan Asokan (JIRA)
• [jira] [Commented] (TEZ-1065) DAGStatus.getVertexStatus and other vertex related API's should maintain vertex order Bikas Saha (JIRA)
• [jira] [Comment Edited] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Comment Edited] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
• [jira] [Resolved] (TEZ-1159) Fix handling of corrupt or empty files in recovery data Hitesh Shah (JIRA)
• [jira] [Updated] (TEZ-1159) Fix handling of corrupt or empty files in recovery data Hitesh Shah (JIRA)
  • [jira] [Updated] (TEZ-1159) Fix handling of corrupt or empty files in recovery data Hitesh Shah (JIRA)
  • [jira] [Updated] (TEZ-1159) Fix handling of corrupt or empty files in recovery data Siddharth Seth (JIRA)
  • [jira] [Updated] (TEZ-1159) Fix handling of corrupt or empty files in recovery data Siddharth Seth (JIRA)
• [jira] [Created] (TEZ-1159) Fix handling of corrupt or empty files in recovery data Hitesh Shah (JIRA)
• [jira] [Resolved] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING and Vertex.INITED state Bikas Saha (JIRA)
• [jira] [Commented] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING and Vertex.INITED state Hitesh Shah (JIRA)
• [jira] [Updated] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING and Vertex.INITED state Bikas Saha (JIRA)
• [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Siddharth Seth (JIRA)
• [jira] [Updated] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) Vertex should stay in initializing state until custom vertex manager sets the parallelism Bikas Saha (JIRA)
• [jira] [Reopened] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING state Bikas Saha (JIRA)
• [jira] [Comment Edited] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Rajesh Balamohan (JIRA)
  • [jira] [Comment Edited] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Gopal V (JIRA)
• [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Rekha Joshi (JIRA)
  • [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Hitesh Shah (JIRA)
• [jira] [Updated] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING state Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING state Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING state Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING state Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1143) 1-1 source split event should be handled in Vertex.RUNNING state Bikas Saha (JIRA)
• [jira] [Resolved] (TEZ-1158) Disable multiple AM attempts if recovery is disabled. Hitesh Shah (JIRA)
• [jira] [Commented] (TEZ-1158) Disable multiple AM attempts if recovery is disabled. Hitesh Shah (JIRA)
  • [jira] [Commented] (TEZ-1158) Disable multiple AM attempts if recovery is disabled. Bikas Saha (JIRA)
• [jira] [Updated] (TEZ-1158) Disable multiple AM attempts if recovery is disabled. Hitesh Shah (JIRA)
  • [jira] [Updated] (TEZ-1158) Disable multiple AM attempts if recovery is disabled. Hitesh Shah (JIRA)
  • [jira] [Updated] (TEZ-1158) Disable multiple AM attempts if recovery is disabled. Siddharth Seth (JIRA)
• [jira] [Created] (TEZ-1158) Disable multiple AM attempts if recovery is disabled. Hitesh Shah (JIRA)
• [jira] [Commented] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Siddharth Seth (JIRA)
• [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Rajesh Balamohan (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Rajesh Balamohan (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Gopal V (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Rajesh Balamohan (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Jing Zhao (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Jing Zhao (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Gopal V (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Gopal V (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Rajesh Balamohan (JIRA)
  • [jira] [Commented] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Bikas Saha (JIRA)
• [jira] [Updated] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Rajesh Balamohan (JIRA)
  • [jira] [Updated] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Gopal V (JIRA)
• [jira] [Created] (TEZ-1157) Optimize broadcast :- Tasks pertaining to same job in same machine should not download multiple copies of broadcast data Rajesh Balamohan (JIRA)
• [jira] [Commented] (TEZ-1152) Optimize broadcast join for scalability Rajesh Balamohan (JIRA)
• [jira] [Created] (TEZ-1156) setParallelism in recovery does not send event to downstream vertices Bikas Saha (JIRA)
• [jira] [Comment Edited] (TEZ-1155) there are many ATS exceptions in the logs Hitesh Shah (JIRA)
• [jira] [Updated] (TEZ-1155) there are many ATS exceptions in the logs Sergey Shelukhin (JIRA)
• [jira] [Commented] (TEZ-1155) there are many ATS exceptions in the logs Sergey Shelukhin (JIRA)
  • [jira] [Commented] (TEZ-1155) there are many ATS exceptions in the logs Hitesh Shah (JIRA)
• [jira] [Created] (TEZ-1155) there are many ATS exceptions in the logs Sergey Shelukhin (JIRA)
• [jira] [Resolved] (TEZ-573) Make single dag executions also go through sessions code path Bikas Saha (JIRA)
• [jira] [Resolved] (TEZ-1154) tez-mapreduce-examples should depend on yarn-api Hitesh Shah (JIRA)
• [jira] [Updated] (TEZ-1154) tez-mapreduce-examples should depend on yarn-api Hitesh Shah (JIRA)
  • [jira] [Updated] (TEZ-1154) tez-mapreduce-examples should depend on yarn-api Hitesh Shah (JIRA)
  • [jira] [Updated] (TEZ-1154) tez-mapreduce-examples should depend on yarn-api Hitesh Shah (JIRA)
• [jira] [Created] (TEZ-1154) tez-mapreduce-examples should depend on yarn-api Hitesh Shah (JIRA)
• [jira] [Commented] (TEZ-1153) Allow object caching for more than one vertex Hitesh Shah (JIRA)
  • [jira] [Commented] (TEZ-1153) Allow object caching for more than one vertex Rohini Palaniswamy (JIRA)
• [jira] [Updated] (TEZ-822) map progress report NaN when it is running randomwriter Hitesh Shah (JIRA)
• [jira] [Reopened] (TEZ-822) map progress report NaN when it is running randomwriter Hitesh Shah (JIRA)
• [jira] [Resolved] (TEZ-393) Handle custom partitioners Rohini Palaniswamy (JIRA)
• [jira] [Created] (TEZ-1153) Allow object caching for more than one vertex Rohini Palaniswamy (JIRA)
• [jira] [Created] (TEZ-1152) Optimize broadcast join for scalability Rajesh Balamohan (JIRA)
• [jira] [Commented] (TEZ-494) Investigate: Exception while submitting a dag to a TezSession Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-494) Investigate: Exception while submitting a dag to a TezSession Rekha Joshi (JIRA)
• [jira] [Work started] (TEZ-494) Investigate: Exception while submitting a dag to a TezSession Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-1008) Vertex V_INIT should be sent to downstream vertices only after vertex is initialized Rekha Joshi (JIRA)
• [jira] [Updated] (TEZ-247) Fix warnings due to service not being closed after change in YARN abstract service Rekha Joshi (JIRA)
  • [jira] [Updated] (TEZ-247) Fix warnings due to service not being closed after change in YARN abstract service Rekha Joshi (JIRA)
  • [jira] [Updated] (TEZ-247) Fix warnings due to service not being closed after change in YARN abstract service Hitesh Shah (JIRA)
• [jira] [Updated] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Rekha Joshi (JIRA)
  • [jira] [Updated] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Rekha Joshi (JIRA)
  • [jira] [Updated] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Hitesh Shah (JIRA)
  • [jira] [Updated] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
• [jira] [Work started] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Rekha Joshi (JIRA)
• [jira] [Updated] (TEZ-923) Input and InputInitializer share the same payload Rekha Joshi (JIRA)
  • [jira] [Updated] (TEZ-923) Input and InputInitializer share the same payload Rekha Joshi (JIRA)
  • [jira] [Updated] (TEZ-923) Input and InputInitializer share the same payload Bikas Saha (JIRA)
• [jira] [Work started] (TEZ-923) Input and InputInitializer share the same payload Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Rekha Joshi (JIRA)
  • [jira] [Assigned] (TEZ-1134) InputInitializer and OutputCommitter implicitly use payloads of the input and output Bikas Saha (JIRA)
• [jira] [Work started] (TEZ-1027) orderedwordcount needs to respect tez.staging-dir property Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-225) Tests for DAGClient Rekha Joshi (JIRA)
  • [jira] [Assigned] (TEZ-225) Tests for DAGClient Jeff Zhang (JIRA)
• [jira] [Assigned] (TEZ-923) Input and InputInitializer share the same payload Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-247) Fix warnings due to service not being closed after change in YARN abstract service Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-573) Make single dag executions also go through sessions code path Rekha Joshi (JIRA)
• [jira] [Commented] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Rekha Joshi (JIRA)
  • [jira] [Commented] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Hitesh Shah (JIRA)
  • [jira] [Commented] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Hitesh Shah (JIRA)
  • [jira] [Commented] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Hitesh Shah (JIRA)
• [jira] [Assigned] (TEZ-1037) Replace multiple members in TaskAttemptImpl for container related stuff with a single reference to the container, possible the AMContainer Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Rekha Joshi (JIRA)
• [jira] [Work started] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Rekha Joshi (JIRA)
  • [jira] [Work started] (TEZ-1041) Move VertexLocationHint into org.apache.tez.common from org.apache.tez.dag.api Rekha Joshi (JIRA)
• [jira] [Work started] (TEZ-1065) DAGStatus.getVertexStatus and other vertex related API's should maintain vertex order Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-1065) DAGStatus.getVertexStatus and other vertex related API's should maintain vertex order Rekha Joshi (JIRA)
• [jira] [Resolved] (TEZ-822) map progress report NaN when it is running randomwriter Rekha Joshi (JIRA)
  • [jira] [Resolved] (TEZ-822) map progress report NaN when it is running randomwriter Hitesh Shah (JIRA)
• [jira] [Work started] (TEZ-822) map progress report NaN when it is running randomwriter Rekha Joshi (JIRA)
• [jira] [Assigned] (TEZ-822) map progress report NaN when it is running randomwriter Rekha Joshi (JIRA)
• [jira] [Commented] (TEZ-1143) One-one edge fail when change source edge dynamically Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1143) One-one edge fail when change source edge dynamically Hitesh Shah (JIRA)
• [jira] [Updated] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Bikas Saha (JIRA)
• [jira] [Created] (TEZ-1151) set parallelism on non 1-1 vertex cause exception Daniel Dai (JIRA)
• [jira] [Resolved] (TEZ-1150) Replace String EdgeId with Edge in the Vertex Bikas Saha (JIRA)
• [jira] [Updated] (TEZ-1150) Replace String EdgeId with Edge in the Vertex Bikas Saha (JIRA)
• [jira] [Assigned] (TEZ-1150) Replace String EdgeId with Edge in the Vertex Bikas Saha (JIRA)
• [jira] [Created] (TEZ-1150) Replace String EdgeId with Edge in the Vertex Bikas Saha (JIRA)
• [jira] [Created] (TEZ-1149) Improve DAG, Vertex, Edge internal representation in the api package Bikas Saha (JIRA)
• [jira] [Created] (TEZ-1148) Exception thrown when old MapRunnable implementation is specified for a MapProcessor vertex Mariappan Asokan (JIRA)
• [jira] [Comment Edited] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Comment Edited] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Comment Edited] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
• [jira] [Created] (TEZ-1147) TaskScheduler should handle preemption requests from YARN Siddharth Seth (JIRA)
• [jira] [Created] (TEZ-1146) Tasks running in containers pre-empted by YARN should not be marked as FAILED Siddharth Seth (JIRA)
• [jira] [Commented] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Siddharth Seth (JIRA)
  • [jira] [Commented] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Commented] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Siddharth Seth (JIRA)
• [jira] [Assigned] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
• [jira] [Created] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
• [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
  • [jira] [Updated] (TEZ-1145) Vertices should not start if they have uninitialized custom edges Bikas Saha (JIRA)
• [jira] [Created] (TEZ-1144) Remove implicit assumption that task outputs are on the same node as the one it ran on Bikas Saha (JIRA)
• [jira] [Updated] (TEZ-1143) One-one edge fail when change source edge dynamically Daniel Dai (JIRA)
  • [jira] [Updated] (TEZ-1143) One-one edge fail when change source edge dynamically Bikas Saha (JIRA)

• Earlier messages
• Later messages