control-service: GraphQL executions query

[mivanov1988]

Extended the GraphQL schema (resources/schema.graphqls) by adding
an additional query called executions. It will allow us to filter
and sort executions by the following fields: status, startTime, endTime.

Sample request:

{{ baseUrl }}/data-jobs/for-team/no-team-specified/jobs?query={
  executions(filter: {
		endTime_gte: "2021-10-19T10:14:47Z",
		status_in: ["failed", "cancelled"]
             },
	     order: {property: "endTime", sort: DESC}) {
    content {
          id
          startTime
          endTime
          status
          jobName
    }
  }
}

Еvaluated an advanced filtering approach, but it seems to be out of scope
of this issue. It will take more implementation time since we should
introduce a new query engine.

{{ baseUrl }}/data-jobs/for-team/no-team-specified/jobs?query={
  executions(filter: [
		{op: gte, property: "endTime", value: "2021-10-19T10:14:47Z"},
		{op: in, property: "status", values: ["failed", "cancelled"]}
	     ],
             order: {property: "status", sort: DESC}) {
    content {
          id
          startTime
          endTime
          status
          jobName
    }
  }
}

Testing: unit tests

Signed-off-by: Miroslav Ivanov [email protected]

[antoniivanov]

Еvaluated an advanced filtering approach, but it seems to be out of scope

I was just looking at how dgraph and hasura handle that problem. Even if it's out of scope for now (with which I agree). Do you think it's worth going in that direction?

[mivanov1988]

Еvaluated an advanced filtering approach, but it seems to be out of scope

I was just looking at how dgraph and hasura handle that problem. Even if it's out of scope for now (with which I agree). Do you think it's worth going in that direction?

Yes, I think that's the way to go. I really like the where clause approach. I have played with the ontotext tutorial it is pretty good.