fe93f594f5
Adding int_core__accommodation Includes both: - Main information of the accommodation, mostly coming from stg_core__accommodation and int_core__country. - Listing lifecycle computation, based on the created bookings from stg_core__bookings. It's just the current state, no history. Some considerations: - I opted to use stg_core__bookings and not int_core__bookings. Main reason is in case at some point we want to add listing-based information to the booking table, it would avoid cyclic references. - I opted to keep all the logic of 1) accommodation info and 2) lifecycle in the same model. This could be easily split into: lifecycle first that reads uniquely from staging and then the int_core__accommodation that could read from the staging version to retrieve accommodation attributes + the lifecycle one. Up to you I'd suggest to review first the documentation in schema since it explains the logic applied. Notion page linked to this task: https://www.notion.so/knowyourguest-superhog/Listing-lifecycle-4dc0311b21ca44f8859969e419872ebd Related work items: #17312 |
||
|---|---|---|
| .. | ||
| intermediate | ||
| reporting | ||
| staging | ||
| doc_blocks.md | ||