Hi, +1 , just consider upgrading from 0.10.x. If the old mlog.txt exists, we need to recover from it.
Thanks, -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -----原始邮件----- > 发件人: "[email protected]" <[email protected]> > 发送时间: 2020-09-04 12:19:43 (星期五) > 收件人: dev <[email protected]> > 抄送: > 主题: Re: [jira] [Created] (IOTDB-868) Can not redo mlogs with special > characters like comma > > Hi, > I'd like to solve this problem. > > Here are my idea: we could serialize the plan of meta operation to the > new mlog.bin file, and deserialize from mlog.bin when restart. > Thus we could avoid the comma problem of csv format. > > > > > Thanks. > > Chao Wang > BONC Ltd > > > From: Jialin Qiao (Jira) > Date: 2020-09-04 10:52 > To: notifications > Subject: [jira] [Created] (IOTDB-868) Can not redo mlogs with special > characters like comma > Jialin Qiao created IOTDB-868: > --------------------------------- > > Summary: Can not redo mlogs with special characters like comma > Key: IOTDB-868 > URL: https://issues.apache.org/jira/browse/IOTDB-868 > Project: Apache IoTDB > Issue Type: Bug > Components: Core/Engine > Affects Versions: 0.10.1, 0.9.3, 0.8.2 > Reporter: Jialin Qiao > > > After we import the double-quoted path, users may have any characters in the > path that includes ",". > > If we still record the mlog using csv format, we could not operate correctly > to paths like > > root.changde.e34c49.struct@VALUE%PRESENT_ANGLE,_CUTTING_HEAD] > > The mlog needs to be encoded. > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
