dor-bernstein
dor-bernstein
@Tmonster I actually didn't had the chance to test it, we will upgrade to duckdb 1.3.0 soon and update
resvoled in 1.3.0
I had the same issue in a couple of places, one of them was because I had this predicate in a where clause: time_col > '2025-06-12 06:28:09.141000' AND time_col =CURRENT_TIMESTAMP...
Nope, I'm talking about the differences between runnig the query on iceberg_scan and running it on a regular duckdb table. I just did CREATE OR REPLACE table AS (SELECT *...
@Tishj ok sounds good, lmk
@Tishj it is the final result, I confirmed that. We are not setting the calendar but we do explicitly set the timezone. Also, why would I get a different result...
@Tishj what would you need for a reproducible example?
@Tish Hey I was able to reproduce the issue. I created the table with spark with this statement: ```python CREATE TABLE IF NOT EXISTS rest.`test_namespace`.test_filter(`id` string, `fetch_insertion_time` timestamp) USING iceberg...
should we move the issue to core duckdb? not sure what is the process
seems like this issue still persists in 1.3.2