You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sandor Molnar (JIRA)" <ji...@apache.org> on 2018/12/05 13:04:00 UTC
[jira] [Created] (AMBARI-25001) Ambari Upgrade from 2.6.2.2 to
2.7.1.0 fails in Schema upgrade phase due to long certificate
Sandor Molnar created AMBARI-25001:
--------------------------------------
Summary: Ambari Upgrade from 2.6.2.2 to 2.7.1.0 fails in Schema upgrade phase due to long certificate
Key: AMBARI-25001
URL: https://issues.apache.org/jira/browse/AMBARI-25001
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.7.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 2.8.0
During the upgrade process to AMBARI 2.7.0 the upgrade operation is failing on Schema upgrade phase due to the following error:
{code:java}
Internal Exception: java.sql.BatchUpdateException: Batch entry 2 INSERT INTO ambari_configuration (property_name, category_name, property_value) VALUES ('ambari.sso.provider.certificate','sso-configuration',<LONG CERTIFICATE VALUE>') was aborted: ERROR: value too long for type character varying(2048)
{code}
Ambari is having the following DDL for {{ambari_configuration}}:
{code:java}
CREATE TABLE ambari_configuration (
category_name VARCHAR(100) NOT NULL,
property_name VARCHAR(100) NOT NULL,
property_value VARCHAR(2048),
CONSTRAINT PK_ambari_configuration PRIMARY KEY (category_name, property_name));
{code}
{{property_value}} is set to maximum of 2048 bytes/chars which is obviously not enough in some cases.
Checking the currently supported DBs we may set this column to 4000 (except for Postgres where the recommended type is {{text}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)