GitHub user haoch opened a pull request:
https://github.com/apache/incubator-eagle/pull/157
EAGLE-273 EAGLE-269 Fix exceeding the maximum row size of 65,535 bytes in
mysql and comparisons between LONG_VARCHAR not supported
https://issues.apache.org/jira/browse/EAGLE-273
https://issues.apache.org/jira/browse/EAGLE-269
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)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/haoch/incubator-eagle EAGLE-273
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-eagle/pull/157.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #157
----
commit 920be297ad04d1514a648341935037db1f567db1
Author: Hao Chen <[email protected]>
Date: 2016-04-20T01:59:50Z
EAGLE-273 EAGLE-269 Fix exceeding the maximum row size of 65,535 bytes in
mysql and comparisons between LONG_VARCHAR not supported
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
