Flaky table refresh behaviour
See original GitHub issueCrateDB version
4.7.0 (also with older versions
CrateDB setup information
single node / multi node
Steps to Reproduce
It is not possible to 100% recreate this every time
CREATE TABLE
INSERT
some date- wait a few seconds
SELECT
on table
CREATE TABLE testtable (
obj OBJECT(IGNORED)
);
wait a few seconds
INSERT INTO testtable (obj) VALUES ({a=1,b=2}),({c=1,b=2}),({a=1,c=2});
wait a few seconds
SELECT * FROM testtable limit 100;
-- SELECT OK, 0 records returned (0.388 seconds)
I would expect that query to take longer, because a refresh needs to be triggered, however it then should return also the recent data. Typically I would not expect data older than 1 second to be missing from a SELECT
run query again right after
SELECT * FROM testtable limit 100;
-- SELECT OK, 3 records returned (0.002 seconds)
Expected Result
SELECT
takes a bit longer, because refresh needs to be run, before returning results- All data is returned
Actual Result
SELECT
takes a bit longer, because refresh needs to be run, before returning results- No data is returned
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Annoying refresh behaviour of table - Oracle Communities
We came across a behaviour of joined View Objects that bothers us. This happens with the versions 11.1.2.2.0 and 11.1.2.3.0.
Read more >How to avoid dropping data or tables when reloading a table
SLT Refresh Behavior How do I drop data of the tables without deleting the tables directly through? How to drop only data from...
Read more >Data flow single table refresh - Microsoft Power BI Community
In this scenario I'd have two Dataflows, one with the Fact table and one with the Dimension tables. Then set a different refresh...
Read more >Db2 SQL - REFRESH TABLE - IBM
The REFRESH TABLE statement refreshes the data in a materialized query table. The statement deletes all rows in the materialized query table, executes...
Read more >Cardamom pancakes, pistachio galettes, salmon toasts
Great to set on the table for everyone to pick at while they are busy getting ... Hot smoked salmon is the dry,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Setting the refresh interval on the table has been a stable workaround so far. Thanks!
Seems like this is a (somewhat flaky) way to reproduce this issue
Both row counts should be 2 in this case Tested on a 3 node cluster
If the initial (45s) timeout is shorter (e.g. 5s), then both SELECTs return 2
test script: