Does anyone know why I get this error Query ```CREATE TABLE

Question

Does anyone know why I get this error Query ```CREATE TABLE my table value float symbol symbol index timestamp TIMESTAMP timestamp timestamp PARTITION BY DAY WITH maxUncommittedRows=10000 commitLag=1000us ``` Error ``` unrecognized commitLag after WITH``` I am using QDB 6 7 AFAI this same query used to work on 6 5 x versions

Jaromir Hamala · Answer

~hi see the release notes <https github com questdb questdb releases tag 6 6>~ edit Imre s reply is nicer slightly smiling face

Imre · Answer

hi < Newskooler> commit lag is automatically managed by QuestDB since 6 6 1 The DB will adjust commit lag dynamically by looking at past ingestion patterns Since this is managed now automatically we removed this keyword

Imre · Answer

Newskooler · Answer

oh yes that s nice

Newskooler · Answer

so is there an option to still set it up manually

Imre · Answer

you can set a max lag but generally not recommended

Imre · Answer

```CREATE TABLE my table value float symbol symbol index timestamp TIMESTAMP timestamp timestamp PARTITION BY DAY WITH maxUncommittedRows=10000 o3MaxLag=1000us ```

Imre · Answer

this will limit the database not to use bigger lag than that even if that would result in better ingestion performance

Imre · Answer

on the other side this can help to make ingested data visible for queries faster

Newskooler · Answer

okay and when upgrading QDB from old instance to new instance what happens to the already set commit lag on previous tables

Imre · Answer

it is used as o3MaxLag to stay backwards compatible basically it makes sure that there is no additional delay introduced the max lag set dynamically will not go above the original setting

Imre · Answer

for new tables we do not recommend setting it just let QuestDB manage it

Newskooler · Answer

Thanks In that case how do we remove it limit such that old tables are set up as per QDB s recommendation

Imre · Answer

you could try without setting it and see if it works for you

Imre · Answer

if there is no ~heavy ingestion~ O3 QuestDB will set a small value on its own and if there is a ~high rate ingestion~ lot of O3 it will increase it

Imre · Answer

previously the lag you set was constant

Imre · Answer

in practice there is always a max value ```long o3MaxLag = getLong properties env PropertyKey CAIRO COMMIT LAG 10 Dates MINUTE MILLIS ``` just set high 10 minutes

Imre · Answer

you could set the same

Imre · Answer

in practice the lag would never reach this value

Newskooler · Answer

I understand Thanks a lot for this detailed explainer < Imre> I appreciate it

Imre · Answer

no worries