Perhaps you can disable index creation in the database initialization. See the following documentation to know details: https://predictionio.apache.org/system/anotherdatastore/
But INDEX option seems disabled in default according to the documentation. Did you enable this option? 2018年9月20日(木) 13:40 박명신 <duve...@braincolla.com>: > > Thanks Mr Takejoe. > > This is probably because of my encodings limitation for varchar index but > MySQL. > > I had similar exceptions when I made varchar(255) column and giving index > with this encoding. > > > > 2018년 9월 20일 (목) 오후 12:40, Naoki Takezoe <take...@gmail.com>님이 작성: >> >> Ah, MySQL can't create index for large colums (> 768 bytes). I'll take a >> look which column is that to find workaround and to know how we can fix this >> problem in the future version of PredictionIO. >> >> 2018年9月20日(木) 11:45 박명신 <duve...@braincolla.com>: >>> >>> Hi there! >>> >>> I'm using PredictionIO with MySQL as a storage. >>> >>> and my MySQL encoding set is utf-8mb4 so its keep returning >>> SQLSyntaxErrorException when I making an app. (especially when pio making >>> index for the table) >>> >>> >>> after I got exception, >>> >>> my DB and table is created also when I repeat 'pio app new ' order, pio >>> returns that app is already exists. >>> >>> and able to delete that app. >>> >>> if I can't change my DB encoding, how should I deal with this? >>> -- Naoki Takezoe
