Remove database prefixes from ClickHouse table creation scripts

[iuwqyir]

TL;DR

Removed database prefixes from table names in ClickHouse SQL scripts and updated engine type for logs table.

What changed?

• Removed database prefixes (orchestrator., base., and staging.) from all table names in ClickHouse SQL creation scripts.
• Changed the engine for the logs table from SharedReplacingMergeTree to ReplacingMergeTree. Shared is only available in hosted version and will be applied automatically if you create a ReplacingMergeTree

How to test?

1. Execute the updated SQL scripts in a ClickHouse environment.
2. Verify that tables are created without database prefixes.
3. Confirm that the logs table is created with the ReplacingMergeTree engine.
4. Ensure that all other table structures and settings remain unchanged.

Why make this change?

• Removing database prefixes allows for more flexibility in table placement and database organization. We don't want to enforce if these tables are used in one database or several

[iuwqyir]

• Remove database prefixes from ClickHouse table creation scripts #83 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @iuwqyir and the rest of your teammates on Graphite

[AmineAfia]

I though we are putting the orchestrator and staging in the same db as main. but still isolate the chains

[iuwqyir]

I though we are putting the orchestrator and staging in the same db as main. but still isolate the chains

We can, but is there a need? Also since this is currently run manually anyways, anyone can decide the database division they want by changing the database

[AmineAfia]

my question was about the amount of data we are putting in one table, but we talked about that with jake yesterday