Skip to content

Commit

Permalink
chore(service): remove op-end traces data (#293)
Browse files Browse the repository at this point in the history
Because

- we don't need to return the trace data for op-end operator, since it
is identical to the trigger response

This commit

- remove op-end traces data
  • Loading branch information
donch1989 committed Nov 9, 2023
1 parent 5d256fd commit ed68178
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions pkg/utils/utils.go
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,11 @@ func GenerateTraces(comps []*datamodel.Component, memory []map[string]interface{
if comps[compIdx].DefinitionName == "operator-definitions/op-start" {
continue
}
// we don't need to return traces data of op-end since the response already contain it
if comps[compIdx].DefinitionName == "operator-definitions/op-end" {
continue
}

for dataIdx := 0; dataIdx < batchSize; dataIdx++ {
if _, ok := memory[dataIdx][comps[compIdx].Id].(map[string]interface{})["input"]; ok {
data, err := json.Marshal(memory[dataIdx][comps[compIdx].Id].(map[string]interface{})["input"])
Expand Down

0 comments on commit ed68178

Please sign in to comment.