CREATE TABLE on QuestDB Startup
I am running QuestDB on a container, with this definition
CREATE TABLE on QuestDB Startup
I am running QuestDB on a container, with this definition
QuestDB replication on schedule rather than real-time?
Is there any way to schedule updates on replicas instead of them happening automatically?
QuestDB optimizing for out of order data
Would it be possible to configure O3 for the following example script ?
It is generating random data being sent every 5 seconds. In a first case, if the timestamp are chosen randomly over the last 4 seconds, the disk usage is very low. In a second case, by change the 4 to a 6 on line 23, I generate the timestamp randomly over the last 6 seconds, therefore with an overlap between batches. In this case, the disk usage is high (~1Mo/s). Even a small overlap is causing the problem.
Query for list of tables modified in the last X hours
I would like to get in a query the list of tables that had modifications (or which have entries appended) in the last X hours, without iteratively querying each table (because there are 1000s of tables). Is there a way to achieve that?
Tables are with TIMESTAMP, partitioned by day.
QuestDB creating multiple partitions for a single month
I have a QuestDB instance where I created a table partitioned by month. I imported some data and I can see all the partitions for the previous months, but when I now ingest live/real-time data, it is creating multiple partition within the current month.
QuestDB creating multiple partitions for a single month
I have a QuestDB instance where I created a table partitioned by month. I imported some data and I can see all the partitions for the previous months, but when I now ingest live/real-time data, it is creating multiple partition within the current month.
QuestDB creating multiple partitions for a single month
I have a QuestDB instance where I created a table partitioned by month. I imported some data and I can see all the partitions for the previous months, but when I now ingest live/real-time data, it is creating multiple partition within the current month.
QuestDB creating multiple partitions for a single month
I have a QuestDB instance where I created a table partitioned by month. I imported some data and I can see all the partitions for the previous months, but when I now ingest live/real-time data, it is creating multiple partition within the current month.
Alter column order in QuestDB table
I have a table we created with a specific column order, with the timestamp as the last column, but now I would prefer to change it and move the timestamp to the first place. What would be the best way to do this? I checked the ALTER TABLE docs and couldn’t find a solution.