You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@griffin.apache.org by "zhengqiang.tan (Jira)" <ji...@apache.org> on 2020/11/19 12:24:00 UTC
[jira] [Created] (GRIFFIN-353) Griffin Service init innodb mysql
Specified key was too long
zhengqiang.tan created GRIFFIN-353:
--------------------------------------
Summary: Griffin Service init innodb mysql Specified key was too long
Key: GRIFFIN-353
URL: https://issues.apache.org/jira/browse/GRIFFIN-353
Project: Griffin
Issue Type: Improvement
Reporter: zhengqiang.tan
where I init mysql table as import the sql script: Init_quartz_mysql_innodb.sql
CREATE TABLE QRTZ_JOB_DETAILS(
SCHED_NAME VARCHAR(120) NOT NULL,
JOB_NAME VARCHAR(200) NOT NULL,
JOB_GROUP VARCHAR(200) NOT NULL,
DESCRIPTION VARCHAR(250) NULL,
JOB_CLASS_NAME VARCHAR(250) NOT NULL,
IS_DURABLE VARCHAR(1) NOT NULL,
IS_NONCONCURRENT VARCHAR(1) NOT NULL,
IS_UPDATE_DATA VARCHAR(1) NOT NULL,
REQUESTS_RECOVERY VARCHAR(1) NOT NULL,
JOB_DATA BLOB NULL,
PRIMARY KEY (SCHED_NAME,JOB_NAME,JOB_GROUP))
ENGINE=InnoDB;
----Error message: {color:#de350b}Specified key was too long; max key length is 767 bytes
{color}----Mysql Version
select version(); --5.6.16
I'm really confused by the Griffin metadata table is it necessary to set the value of the joint primary key that big? like JOB_NAME VARCHAR(200) ??
--
This message was sent by Atlassian Jira
(v8.3.4#803005)