[
https://issues.apache.org/jira/browse/KUDU-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368659#comment-16368659
]
Andre Araujo commented on KUDU-2300:
------------------------------------
Thanks, [~danburkert] and [~granthenke]. I see that now. I hadn't noticed that
there was a "...1Z" on the lower bound.
This issue can be closed.
> Partition schema doesn't show correct type of bounds for range partitions
> -------------------------------------------------------------------------
>
> Key: KUDU-2300
> URL: https://issues.apache.org/jira/browse/KUDU-2300
> Project: Kudu
> Issue Type: Bug
> Components: master
> Affects Versions: 1.5.0
> Reporter: Andre Araujo
> Priority: Major
>
> 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:
> {code:java}
> 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
> ){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
