hi:
UTF-8 coding has met most of the requirements. I think you should consider why it leads to: index column size too large Instead of focusing on changing the encoding of the database Normally, the database index should not be large -------------------------------------- BoYi ZhangE-mail : [email protected] On 09/29/2020 20:02，CalvinKirs<[email protected]> wrote： I think we don’t need utf8-mb4 Best wishes！ CalvinKirs On 09/29/2020 16:09，[email protected]<[email protected]> wrote： Hi folks, Welcome to discuss.I introduce the background and what should we discuss first,If here is something didn't described clearly,please feel free to tell me. Backgound Thougth dolphinscheduler uses the postgresql,but provided the mysql construct sql to make it easier to use mysql. The table of quartz used the charset `utf8mb4` and the other tables used the charset `utf8`. Here is a pr[1] suggest to use utf8.For the reason [2] below. What should we discuss? What should we discussed is that `Which charset should we choose in mysql`? Welcome everyone discuss,of course you can give other resolve method. 1.https://github.com/apache/incubator-dolphinscheduler/pull/3689 2.When executing MySQL table creation statement, it will report that the index length is not enough. this will happen: Index column size too large. The maximum column size is 767 bytes. Thanks, Gang Li DolphinScheduler(Incubator) PPMC Gang Li 李岗 [email protected]
