fix: silver_events 클러스터 순서 event_name 우선

[RimSM]

이벤트 타입 필터가 잦은 쿼리 패턴에 맞춰 cluster_by를 [event_name, user_pseudo_id]로. 다음 full-refresh 때 적용.

Summary by CodeRabbit

• Performance
  • Improved event data organization to support more efficient querying and retrieval.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: e2bd6207-dcac-4c3a-a4b2-ea1d596e502e

📥 Commits

Reviewing files that changed from the base of the PR and between 11e6372 and 040950d.

📒 Files selected for processing (1)

• dbt/models/silver/silver_events.sql

---

📝 Walkthrough

Walkthrough

The incremental silver_events model retains insert_overwrite partitioning by event_dt and changes its clustering order to event_name, then user_pseudo_id.

Changes

Silver events clustering

Layer / File(s)	Summary
Update clustering configuration dbt/models/silver/silver_events.sql	The clustering columns are reordered from user_pseudo_id, event_name to event_name, user_pseudo_id.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• BCSDLab/KOIN_DATA#20: Introduces or configures the same silver_events incremental model.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/silver-events-cluster-order

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}