Open A-Gray-Cat opened 1 day ago
Could you help quick check the oldest time_dt
ingested in MV data? Just wonder if any time zone issue here.
@dai-chen Yes. The MV was created around 12:09PM PDT, and the oldest time_dt
value in the MV is 2024-10-17 13:07:31
in UTC I would assume.
What is the bug? When I was creating an auto-refresh materialized view, the statement I used included a where clause that looks for all the logs in the past '1' day. However, I noticed that each refresh didn't ingest logs all the way back within the specified timeframe, and only partial logs were ingested.
How can one reproduce the bug? Steps to reproduce the behavior:
Create a materialized view and set auto_refresh=false using the same statement:
And run
REFRESH testing_manual_mv
Run the following SQL query against both MVs you just created, and compare the earliest timestamp:
You can also check the difference of number of documents that are ingested in both MVs.
What is the expected behavior? The auto-refresh MV should ingest all the logs within the specified timeframe
What is your host/environment?
Do you have any screenshots? If applicable, add screenshots to help explain your problem.
Do you have any additional context? Add any other context about the problem.