Hi Stefano,
I implemented the overlap according to Calcite's implementation. Maybe
they changed the behavior in the mean time. I agree we should try to
stay in sync with Calcite. What do other DB vendors do? Feel free to
open an issue about this.
Regards,
Timo
Am 30.05.17 um 14:24 schrieb
Hi all,
I am playing around with the table API, and I have a doubt about temporal
operator overlaps. In particular, a test in the
scalarFunctionsTest.testOverlaps checks for false the following intervals:
testAllApis(
temporalOverlaps("2011-03-10 05:02:02".toTimestamp, 0.second,
"2
