You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/11/11 03:36:00 UTC

[jira] [Updated] (HDDS-4443) Recon: Using Mysql database throws exception and fails startup

     [ https://issues.apache.org/jira/browse/HDDS-4443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HDDS-4443:
---------------------------------
    Labels: pull-request-available  (was: )

> Recon: Using Mysql database throws exception and fails startup
> --------------------------------------------------------------
>
>                 Key: HDDS-4443
>                 URL: https://issues.apache.org/jira/browse/HDDS-4443
>             Project: Hadoop Distributed Data Store
>          Issue Type: Task
>          Components: Ozone Recon
>    Affects Versions: 1.0.0
>            Reporter: Vivek Ratnavel Subramanian
>            Assignee: Vivek Ratnavel Subramanian
>            Priority: Major
>              Labels: pull-request-available
>
> Recon uses Derby as its SQL database by default. Switching it to Mariadb/Mysql throws an exception `Specified key was too long; max key length is 767 bytes`
> Fix this issue by reducing the primary key length from VARCHAR(768) to VARCHAR(766) in ReconTaskSchemaDefinition.java. Also change the autocommit config to default to true since data is not persisted in MySql tables even after insert queries are executed with autocommit flag set to false by default.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org