Triggers can run BEFORE the action is taken or AFTER the action is taken.
Can we implement is bigquery.
Solved! Go to Solution.
Cloud Functions or Cloud Run: You can set up Google Cloud Functions or Cloud Run to act as triggers that respond to certain events in BigQuery, such as the completion of an insert or update. This can be done by:
Scheduled Queries: For cases where you don't need real-time triggers but want periodic checks on data, you can use scheduled queries to process or modify data at regular intervals.
Dataflow for Real-time Streaming: If you are working with streaming data, Google Cloud Dataflow can process real-time changes, and you can add logic to process rows as they are ingested into BigQuery.
Manual Logic in Queries: You can manually handle logic such as "before insert" or "after insert" by structuring your queries to first validate data before inserting, or running updates after an insert.
Hi @NishinThattil,
In addition to @ms4446 , you can also refer to the following documentation:
I hope the above information is helpful.
Cloud Functions or Cloud Run: You can set up Google Cloud Functions or Cloud Run to act as triggers that respond to certain events in BigQuery, such as the completion of an insert or update. This can be done by:
Scheduled Queries: For cases where you don't need real-time triggers but want periodic checks on data, you can use scheduled queries to process or modify data at regular intervals.
Dataflow for Real-time Streaming: If you are working with streaming data, Google Cloud Dataflow can process real-time changes, and you can add logic to process rows as they are ingested into BigQuery.
Manual Logic in Queries: You can manually handle logic such as "before insert" or "after insert" by structuring your queries to first validate data before inserting, or running updates after an insert.
Hi @NishinThattil,
In addition to @ms4446 , you can also refer to the following documentation:
I hope the above information is helpful.