+4It would very helpful to have a way of triggering a hosted extractor run. I have an extractor that we only want to run once a day when in production but we are trying to build it out and test it. It is very slow development when we have to wait a minimum of 5 minutes for the schedule to trigger.
If hosted extractors get a trigger feature then I see nothing stopping it from being used in workflows.
We’re looking at this for hosted extractors in the context of the upcoming integrations feature, and in the context of workflows. ATM, the thinking is to add a way for the workflows capability to be informed by the hosted extractors that it’s “time to go”.
One of the challenges are the “continuous flow of data” extractors - MQTT or Kafka for instance - where there’s no clear “I’m done” state.
The hosted extractors are designed to “run contenously”. I hear the desire to have a way to trigger them, but for 2025, this is beyond the scope of work the team can commit to. I will be parking this idea until further notice.
+4Could there be a better way to trigger the Hosted Extractor if it fails? Right now I have to change the interval of the job and pause/unpause it for it to trigger again. This is tedious when I’m troubleshooting.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
