[
https://issues.apache.org/jira/browse/GOBBLIN-1458?focusedWorklogId=610988&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-610988
]
ASF GitHub Bot logged work on GOBBLIN-1458:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Jun/21 22:38
Start Date: 14/Jun/21 22:38
Worklog Time Spent: 10m
Work Description: jack-moseley commented on a change in pull request
#3297:
URL: https://github.com/apache/gobblin/pull/3297#discussion_r651323024
##########
File path:
gobblin-restli/gobblin-flow-config-service/gobblin-flow-config-service-api/src/main/idl/org.apache.gobblin.service.flowconfigsV2.restspec.json
##########
@@ -79,7 +79,12 @@
} ]
} ],
"entity" : {
- "path" : "/flowconfigsV2/{id}"
+ "path" : "/flowconfigsV2/{id}",
+ "actions" : [ {
+ "name" : "triggerExecution",
Review comment:
Is it? I can think of a couple LI tools that use "trigger" to describe
an API action, and for example Azkaban uses "trigger" when referring to flows
launched through data landing or kafka events:
https://azkaban.readthedocs.io/en/latest/eventTrigger.html
To me, trigger seems like a good way to describe launching a flow that
exists through a one-time request instead of due to the schedule or because the
flowConfig was just sent.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 610988)
Time Spent: 2h (was: 1h 50m)
> Add endpoint to trigger a flow in GaaS
> --------------------------------------
>
> Key: GOBBLIN-1458
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1458
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Jack Moseley
> Priority: Major
> Time Spent: 2h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
