You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request: It would be very useful for the response to return the associated job log id.
Programmatically matching up job logs with its associated crawler or scheduler requires a bit of parsing, as the crawler id is mixed in under scriptData on the job log:
{ "scriptData": "return container.getComponent(\"crawlJob\").logLevel(\"info\").sessionId(\"AWDhczHBC-pNKvFYBZJo\").webConfigIds([\"AWDhczHBC-pNKvFYBZJo\"] as String[]).fileConfigIds([] as String[]).dataConfigIds([] as String[]).jobExecutor(executor).execute();", }
The text was updated successfully, but these errors were encountered:
When I start a job through the admin api:
http://site.com/api/admin/scheduler/<ID>/start
I get the following response:
{ "response": { "version": "11.4", "status": 0 } }
Feature request: It would be very useful for the response to return the associated job log id.
Programmatically matching up job logs with its associated crawler or scheduler requires a bit of parsing, as the crawler id is mixed in under scriptData on the job log:
{ "scriptData": "return container.getComponent(\"crawlJob\").logLevel(\"info\").sessionId(\"AWDhczHBC-pNKvFYBZJo\").webConfigIds([\"AWDhczHBC-pNKvFYBZJo\"] as String[]).fileConfigIds([] as String[]).dataConfigIds([] as String[]).jobExecutor(executor).execute();", }
The text was updated successfully, but these errors were encountered: