You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I always get log of create table md_ets_metadata. Is due to a bad config ?
To Reproduce
Steps to reproduce the behavior: LOG: statement: create table if not exists md_ets_metadata (table_name text primary key, entity_attrs jsonb)
Expected behavior
Should be log only once
Environment (please complete the following information):
OS: Linux
Version lastest
Additional context
I use quantumleap with timescaleDB
The text was updated successfully, but these errors were encountered:
I always get log of create table md_ets_metadata. Is due to a bad config ?
No it's just one (of the many) QuantumLeap warts :-) Because QL creates tables dynamically, it can't know beforehand if the metadata table is already there, so it tries creating it everytime. If the table exists, the DB will do nothing because of the if not exists clause.
Should be log only once
Easier said than done. There's no transactions, no ACID semantics. So how would you handle concurrency? E.g. think of ten QuantumLeap processes executing that statement at about the same time...
Describe the bug
I always get log of create table md_ets_metadata. Is due to a bad config ?
To Reproduce
Steps to reproduce the behavior:
LOG: statement: create table if not exists md_ets_metadata (table_name text primary key, entity_attrs jsonb)
Expected behavior
Should be log only once
Environment (please complete the following information):
Additional context
I use quantumleap with timescaleDB
The text was updated successfully, but these errors were encountered: