Where I can find history of ended scheduled jobs in JasperServer? I have access to postre repository, but I can't find it.
I found only table jireportjob where I can find current jobs.
Related
Currently using GCP BigQuery UI for scheduled queries, everything is manually done.
Wondering if there's a way to automatically deploy to GCP using a config JSON that contains the scheduled query's parameters and scheduled times through github actions?
So far, this is one option I've found that makes it more "automated":
- store query in a file on Cloud Storage. When invoking Cloud Function, you read the file content and you perform a bigQuery job on it.
- have to update the file content to update the query
- con: read file from storage, then call BQ: 2 api calls and query file to manage
Currently using DBT in other repos to automate and make this process quicker: https://docs.getdbt.com/docs/introduction
Would prefer the github actions version though, just haven't found a good docu yet :)
We are using Azure Data Factory V2 with a tumbling trigger - works great. However, in exploring cadence options in our dev environment a tumbling window was set up with a 15 second interval. This racked up a good few thousand entries in the pipeline runs activity history. I cant seem to find a way to purge or delete these failed runs - how can I clean up the history? Ideally, when I delete a trigger it would be helpful to have an option to remove all the history associated with that trigger. Is there any way of accomplishing this or similar?
I have created dataproc cluster and processed dataproc jobs. When I select jobs tab, It didn't list the created jobs even when I select all regions.
There was a recently identified bug where jobs fail to list if you have no jobs in the older "global"region; this is fixed in code but the fix will take some time to get released everywhere, possibly up to middle of next week or so.
In the meantime, if you run any job in the "global" region and don't delete it, you should be able to see all of your jobs in other regions as well.
Once the fix is rolled out, this workaround will no longer be necessary.
I know Stop-AzureAutomationJob will stop the job. But how can you delete the job altogether? ie. I don't want it to show up in the list of jobs for that runbook.
This is currently not supported. Jobs cannot be deleted.
My requirement is:
Workflow should run daily at 2pm. Workflow has been scheduled to run at 2pm
We have lookup on master tables. Records with IDs that are not present in the master tables will get rejected.
These new IDs have to be loaded into the master tables manually and then the workflow has to be re-run.
Daily the same thing happens.
My question is -
Is it possible to schedule a workflow to run twice every day(one for the first run, the other to run after the master table is updated)?
If No, can I manually start a scheduled workflow? Will it make the workflow unscheduled?
Please, Can any one help me with this?
Informatica's scheduler is a weak spot. I guess using two copies of the same workflow with different schedules would be the easiest solution.
Got a solution for my problem.
Once a workflow is scheduled, even if a particular session has to be re-run manually, whole workflow has be run from the workflow manager.
If that particular session is run manually, scheduling will be gone.
So always run the workflow instead of a session, so that scheduling will remain.