Hi, +1 for BigEndian, not changing
Thanks, -- Zesong Sun School of Software, Tsinghua University 孙泽嵩 清华大学 软件学院 > -----原始邮件----- > 发件人: "Yuan Tian" <[email protected]> > 发送时间: 2021-09-29 15:32:14 (星期三) > 收件人: dev <[email protected]> > 抄送: > 主题: Re: Endianess. > > Hi, > > I also prefer not to change the current mode. > > BigEndian +1 > > ----------------------- > Yuan Tian > > On Wed, Sep 29, 2021 at 8:39 AM Xiangdong Huang <[email protected]> wrote: > > > Hi, > > > > So we will keep BigEndian, right? > > > > Best, > > ----------------------------------- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > Julian Feinauer <[email protected]> 于2021年9月28日周二 下午6:47写道： > > > > > > Big +1 for fixed Endianness! > > > > > > I think a C implementation would also be beneficial for something like a > > sqlite interface (see my thread here > > https://lists.apache.org/thread.html/rd4d0296e0fef9c1c822f605f641d829047e0932429499a5e05667b8e%40%3Cdev.iotdb.apache.org%3E) > > as it could be wrapped to whatever language we like basically (again > > sqlite...). > > > > > > Best > > > Julian > > > > > > Von: Giorgio Zoppi <[email protected]> > > > Datum: Montag, 27. September 2021 um 13:06 > > > An: dev <[email protected]> > > > Betreff: Re: Endianess. > > > Hello IOTDBers, > > > Chris I agree with you, everything shall be Network Byte Order( > > > https://www.ibm.com/docs/en/zos/2.4.0?topic=hosts-network-byte-order) by > > > the first writing. Thank you. I will look at your C code for review, > > > The first stage is to support natively TsFile. At this moment we've just > > > unmolded code however looking at Apache Arrow codebase is useful for the > > > progress. After the ts file we'll look together at a server, my idea is > > to > > > have in the long term a lower latency product that scales better than > > Java > > > ones (iotdb-native). But for the moment it's just a dream, so baby steps > > > and hard work as usual. > > > Thank you! > > > > > > Best Regards, > > > Giorgio. > > </[email protected]></[email protected]></[email protected]></[email protected]></[email protected]></[email protected]>
