Greetings!
We encountered unexpected behavior. The data type DateTime64 allows milliseconds, but Pillar rounds it to seconds.
For example input data:
created_1 = "2023-11-30T13:45:00.500000Z"
created_2 = "2023-11-30T13:45:00.750000Z"
created_3 = "2023-11-30T13:45:00.850000Z"
created_4 = "2023-11-30T13:45:01.200000Z"
In ClickHouse it saved like:
| uid |
created_at |
| t1 |
2023-11-30 13:45:00.000 |
| t2 |
2023-11-30 13:45:00.000 |
| t3 |
2023-11-30 13:45:00.000 |
| t4 |
2023-11-30 13:45:01.000 |
There are may be a reason for this behavior. Can you explain why it works this way?
We have problem to build pagination based on date when we insert more than 1 records per second.
Greetings!
We encountered unexpected behavior. The data type DateTime64 allows milliseconds, but Pillar rounds it to seconds.
For example input data:
In ClickHouse it saved like:
There are may be a reason for this behavior. Can you explain why it works this way?
We have problem to build pagination based on date when we insert more than 1 records per second.