[PHOENIX-6823] calling Joda-based round() function on temporal PK field causes division by zero error

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.0, 5.1.2
• Fix Version/s: 5.2.0, 5.1.3
• Component/s: core
• Release Note: Fixed division by zero errors, and incorrect results when using round(), ceiling(), floor() functions in the where clause on date/time fields that are part of the primary key.
• Assignee: Istvan Toth
• Reporter: Istvan Toth
• Created: 28/Oct/22 12:46
• Updated: 29/Nov/22 20:14
• Resolved: 29/Nov/22 20:10

Description

 

0: jdbc:phoenix:> create table bubu (df date primary key);
No rows affected (0.689 seconds)
0: jdbc:phoenix:> select * from bubu where round(df,'YEAR',1)=DATE '2022-01-01 00:00:00';
java.lang.ArithmeticException: / by zero
    at org.apache.phoenix.expression.function.RoundDateExpression$1.getKeyRange(RoundDateExpression.java:272)
...

This is caused by getKeyRange not being updated when the Joda-based time units were added.

Also, the keyrange pushdown logic is just wrong, even for the non-joda cases.

Issue Links

• is caused by: PHOENIX-2433 support additional time units (like week/month/year) in Trunc() round() and Ceil()
• is related to: PHOENIX-5066 The TimeZone is incorrectly used during writing or reading data
• relates to: PHOENIX-6822 Multiplier for Temporal round/floor/ceiling functions is not implemented and/or poorly defined
• links to: GitHub Pull Request #1530
• links to: GitHub Pull Request #1537