chore: remove obsolete scripts and dev artifacts

This commit is contained in:
2026-05-30 14:14:54 -05:00
parent 3aa664324d
commit ee782a9a19
3 changed files with 70 additions and 40 deletions

View File

@@ -39,15 +39,15 @@ jobs:
# source:
# schema: analytics
# table: events
# primary_key: ID_events
# primary_key: id
# from_json:
# - column: $node_id*
# - column: payload
# field: id
# target:
# schema: analytics
# table: events
# - name: analytics_audit_log
# - name: storage_attachments
# source:
# schema: storage
# table: attachments
@@ -75,3 +75,33 @@ jobs:
# base_delay_ms: 1000
# max_delay_ms: 15000
# max_jitter_ms: 500
# - name: analytics_audit_log
# source:
# schema: analytics
# table: audit_log
# primary_key: id
# target:
# schema: analytics
# table: audit_log
# pre_sql:
# - "DROP INDEX IF EXISTS audit_log_created_at_idx"
# - "DROP INDEX IF EXISTS audit_log_user_id_idx"
# post_sql:
# - "CREATE INDEX audit_log_created_at_idx ON analytics.audit_log (created_at)"
# - "CREATE INDEX audit_log_user_id_idx ON analytics.audit_log (user_id)"
# - "ANALYZE analytics.audit_log"
# # Partition slicing: only migrate the slice [2024-01-01, 2024-12-31]
# # in this re-run. is_min_inclusive=false resumes AFTER any failed boundary.
# range:
# min: 1704067200000 # 2024-01-01 UTC, as epoch millis
# max: 1735689599999 # 2024-12-31 UTC, as epoch millis
# is_min_inclusive: false
# is_max_inclusive: true
# partition_calculation_strategy: ESTIMATION # faster than EXACT on large tables
# truncate_method: DELETE # use DELETE instead of TRUNCATE
# batches_per_partition: 8
# retry:
# attempts: 5
# max_failed_partitions: 3
# max_failed_batches_load: 10