[KUDU-2300] Partition schema doesn't show correct type of bounds for range partitions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 1.5.0
• Component/s: master
• Assignee: Unassigned
• Reporter: Andre Araujo
• Created: 15/Feb/18 17:13
• Updated: 18/Feb/18 20:03
• Resolved: 18/Feb/18 20:03

Description

The Partition Schema section of the master Web UI always show the range partition with an EXCLUSIVE upper bound and an INCLUSIVE lower bounce, regardless of what the actual bounds' types are.

For example, the partition below was created with two INCLUSIVE bounds, but the upper bound is shown incorrectly:

HASH (CALLING_NUMBER_INT, CALLED_NUMBER_INT) PARTITIONS 2,
RANGE (PERIOD_START_TIME) (
    PARTITION 2018-02-15T00:00:00.000001Z <= VALUES < 2018-02-16T00:00:00.000000Z
)