forked from flyteorg/flyteidl
/
model_event_task_execution_event.go
36 lines (33 loc) · 1.95 KB
/
model_event_task_execution_event.go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
/*
* flyteidl/service/admin.proto
*
* No description provided (generated by Swagger Codegen https://github.com/swagger-api/swagger-codegen)
*
* API version: version not set
* Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)
*/
package flyteadmin
import (
"time"
)
// Plugin specific execution event information. For tasks like Python, Hive, Spark, DynamicJob.
type EventTaskExecutionEvent struct {
// ID of the task. In combination with the retryAttempt this will indicate the task execution uniquely for a given parent node execution.
TaskId *CoreIdentifier `json:"task_id,omitempty"`
ParentNodeExecutionId *CoreNodeExecutionIdentifier `json:"parent_node_execution_id,omitempty"`
RetryAttempt int64 `json:"retry_attempt,omitempty"`
Phase *CoreTaskExecutionPhase `json:"phase,omitempty"`
ProducerId string `json:"producer_id,omitempty"`
Logs []CoreTaskLog `json:"logs,omitempty"`
// This timestamp represents when the original event occurred, it is generated by the executor of the task.
OccurredAt time.Time `json:"occurred_at,omitempty"`
// URI of the input file, it encodes all the information including Cloud source provider. ie., s3://...
InputUri string `json:"input_uri,omitempty"`
// URI to the output of the execution, it will be in a format that encodes all the information including Cloud source provider. ie., s3://...
OutputUri string `json:"output_uri,omitempty"`
Error_ *CoreExecutionError `json:"error,omitempty"`
// Custom data that the task plugin sends back. This is extensible to allow various plugins in the system.
CustomInfo *ProtobufStruct `json:"custom_info,omitempty"`
// Some phases, like RUNNING, can send multiple events with changed metadata (new logs, additional custom_info, etc) that should be recorded regardless of the lack of phase change. The version field should be incremented when metadata changes across the duration of an individual phase.
PhaseVersion int64 `json:"phase_version,omitempty"`
}