You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/05/17 06:20:13 UTC
[jira] [Commented] (EAGLE-273) Issue with creating MySql tables ,
only 14 were created out of 24, reason being varchar(30000) for multiple
columns lead to exceeding the maximum row size of 65,535 bytes.
[ https://issues.apache.org/jira/browse/EAGLE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286114#comment-15286114 ]
ASF GitHub Bot commented on EAGLE-273:
--------------------------------------
Github user qingwen220 commented on the pull request:
https://github.com/apache/incubator-eagle/pull/158#issuecomment-219629301
LGTM
> Issue with creating MySql tables , only 14 were created out of 24, reason being varchar(30000) for multiple columns lead to exceeding the maximum row size of 65,535 bytes.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EAGLE-273
> URL: https://issues.apache.org/jira/browse/EAGLE-273
> Project: Eagle
> Issue Type: Bug
> Affects Versions: v0.3.0
> Reporter: Hao Chen
> Assignee: Hao Chen
> Fix For: v0.4.0
>
>
> h2. Problem
> Issue with creating MySql tables , only 14 were created out of 24, reason being varchar(30000) for multiple columns lead to exceeding the maximum row size of 65,535 bytes. I can look into this and fix it. Workaround is to create the tables manually after changing the DDL.
> h2. Root Cause & Problem
> The problem is cause the limitation of maximum row size in mysql innodb engine, so need to keep the column size relatively small, but it will cause it can't store large field, it's a little tricky, so may have following possible solutions:
> * Solution One: Fix mysql innodb size to resolve the limitation.
> * Solution Two: Keep the field relatively small to avoid exceeding maximum row size and make sure creating table successfully, and modify field size according to actual usage (Which is the approach we take for this problem)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)