[
https://issues.apache.org/jira/browse/AMBARI-6099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029236#comment-14029236
]
Jonathan Hurley commented on AMBARI-6099:
-----------------------------------------
[~shivanigupta] - BUG-18772 was a blocker and we needed to have it resolved
quickly. I normally would have just made the switch to SMALLINT to be
consistent, but we've already released 1.6.0. That means that our upgrade code
would need to handle scenarios where restart_required was both a boolean and a
SMALLINT.
It didn't seem wise to make that code part of a rushed fix, so I opened up this
Jira to track...
> Change restart_required from BOOLEAN to SMALLINT
> ------------------------------------------------
>
> Key: AMBARI-6099
> URL: https://issues.apache.org/jira/browse/AMBARI-6099
> Project: Ambari
> Issue Type: Task
> Affects Versions: 1.6.0
> Reporter: Jonathan Hurley
> Priority: Minor
>
> We avoid the use of the "boolean" data type in our databases since many
> vendors do not support it and sometimes the behavior can be unpredictable in
> JPA.
> BUG-18772 addresses and issue where the Postgres upgrade to schema 1.6.0 was
> failing because Postgres can not convert a SMALLINT to a boolean.
> We should aim to be consistent in our approach to databases, and that means
> that we should continue to treat 0/1 fields like restart_required as a
> SMALLINT in Postgres, even though newer version of that database do support
> BOOLEAN fields.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
