chore(data-warehouse): Adjusted temporal and sql settings for long running tasks

[Gilbert09]

Problem

• We have a long-running snowflake job that keeps getting activity timeouts on the import data step

Changes

• Updates the activity heartbeat time out from 2mins to 5mins
  • Kept the heartbeater beating every 10 secs (I think something may be stopping it from beating?!)
• Increased the start_to_close_timeout from 5 hours to 12 hours
• Increased the SQL chunk size from 1,000 to 5,000 rows
• Moved the import_data heartbeater to the root of the activity and not just wrapping the DLT pipeline run

[EDsCODE]

assuming the tab indent changes are correct

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ DeltaError: Delta protocol violation: Generic action error: filed to get tombstones posthog.temporal.data_imports.pipelines.pipelin... View Issue
• ‼️ PipelineStepFailed: Pipeline execution failed at stage normalize when processing package 1727291771.1948323 with exce... posthog.temporal.data_imports.pipelines.pipelin... View Issue
• ‼️ PipelineStepFailed: Pipeline execution failed at stage load when processing package 1727291608.795646 with exception: posthog.temporal.data_imports.pipelines.pipelin... View Issue
• ‼️ PipelineStepFailed: Pipeline execution failed at stage load when processing package 1727288871.7664406 with exception: posthog.temporal.data_imports.pipelines.pipelin... View Issue
• ‼️ Exception: DLT type 'binary' is not a supported column type posthog.warehouse.data_load.validate_schema in ... View Issue

_{Did you find this useful? React with a 👍 or 👎}