Re: Losing privileges on Travis

> Well, things are getting a little better. I can restart a build now, but I > can't still restart a single job. > > > Tian Jiang > > > On 10/21/2019 13:20，Xiangdong Huang wrote： > Hi, > > Ah? I think still have the privilege.. > > Best, > -

Losing privileges on Travis

Hi, I just found I have lost some privileges on Travis, that is, I cannot restart any builds or jobs. Does anyone encounter the same problem or have the solution? Thanks, Tian Jiang

Re: consider introduce error code in client-side

Well, I prefer to define new Exception classes over ugly error codes, which better utilize OOP. Tian Jiang > 在 2019年8月13日，下午4:00，Xiangdong Huang 写道： > > Hi, > > When using IoTDB-JDBC to operate data, I realize that it is not convenient > without error codes > > The typical

Re: [jira] [Created] (IOTDB-161) ERROR code is needed.

Well, I prefer to define new Exception classes over ugly error codes, which better utilize OOP. Tian Jiang > 在 2019年8月13日，下午3:45，xiangdong Huang (JIRA) 写道： > > xiangdong Huang created IOTDB-161: > - > > Summary: ERROR code is needed. >

Re: Binary Release of IoTDB

Hi, Structure 4 looks cool, I shall stand for it. (I am not forced to say that.) Tian Jiang > 在 2019年7月19日，下午2:40，Julian Feinauer 写道： > > Hi, > > I like it but perhaps would rename bin to sbin or scripts. > But also fine with that. > > I think it's excellent that the community adopts more

Re: Binary Release of IoTDB

Hi, I prefer the second. I will feel frustrated when I open the bin folder only to find everything is crowded in it. With the names of the scripts largely alike, searching for a specific one may take more time. And I really don't think some duplicated library matters. We are in 2010s, tens of

Re: About the design and development of merge.

Hi, The Merge is functional on branch dev_merge and the related PR is on https://github.com/apache/incubator-iotdb/pull/258 . If you feel interested, feel free to give any advices or comments. Thanks Tian Jiang

Re: What Is a Good Git Workflow?

I prefer not to squash, too. In my opinion, commit logs give reasons of everything you have done (even when you just fixed a typo) so it does not make sense to delete any of them. If someone wants a straight-forward conclusion of this branch or PR, I would suggest the committer(s) conclude it

Re: About the design and development of merge.

unseq file may consists > of many devices and measurements)? Do we need to make some marks on an unseq > file if only the data of a part of devices are merged? > > Best. > --- > Xiangdong Huang > School of Software, Tsinghua University > >

About the design and development of merge.

Greetings, Although the new storage engine is on-line, some old functionalities are lost, for example, merge. As you may have known, current storage engine consists of two kind of data files, sequential files and unsequential files. A data point of a specified timestamp, say, t0, may occur

Re: About prepared statement

normal statement costed 54035ms, which is a significant improvement. > 在 2019年6月25日，下午10:58，江天 写道： > > I have created an issue IOTDB-122 > <https://issues.apache.org/jira/browse/IOTDB-122>, you may find it on > https://issues.apache.org/jira/projects/IOTDB/issues/IOT

Re: About prepared statement

在 2019年6月25日，下午9:17，江天 写道： > > Follow the preceding mail, > > People of interest are welcomed to join this thread, discuss about this new > feature and give advice. If no one has opposite opinion, I would like to set > off to develop this feature. > > Best regards, >

Re: About prepared statement

Follow the preceding mail, People of interest are welcomed to join this thread, discuss about this new feature and give advice. If no one has opposite opinion, I would like to set off to develop this feature. Best regards, Tian Jiang > 在 2019年6月25日，下午8:41，江天 写道： > > Hi, > &g

Having trouble testing recovery after abnormal exits.

Hi, Now that the Write Ahead Log(WAL) is back on feet again, we are having difficulties testing it in an integrated context. Of course we can test it by hand, but automated solutions are always better. However, we lack experience of testing recovering a system after crashes and Junit framework

Re: Out-of-Memory Analysis- reformat for reading

Good summary, I would like to make some minor supplements. 1. I think the data of one series can be discarded as soon as its corresponding Chunk is generated, so you do not need to bother redesigning it, a simple optimization may do the trick. 2. Yeah, as long as you can estimate how much

Re: [External] Re: Commit tsfile-go

Yes, I think the main differences will be: 1. The header of a ChunkGroup(called RowGroup previously) is moved to the tail of the data and becomes a footer. 2. As a consequence of 1., there is a marker before each ChunkHeader and ChunkGroupFooter, and there is also a marker before the index at

Re: How to prevent GitBox from sending too many commit notifications

I like the idea of being highly transparent, but we hope to know some tricks of doing this. Do we have to paste the code in the mails or just tell someone what problem which line in which file has? Both of these seem tiring. > 在 2019年1月25日，上午1:08，Justin Mclean 写道： > > Hi, > >> No matter what

How to prevent GitBox from sending too many commit notifications

Hello I am driven crazy because every time someone commits to incubating-IoTDB, I receive a mail from GitBox. This is just too annoying. Could someone please tell me how to disable GitBox’s sending commit notifications, or make it send to comm...@iotdb.apache.org instead of

How to prevent GitBox from sending too many commit notifications

Hello. I am driven crazy because every time someone commits to incubating-IoTDB, I receive a mail from GitBox. This is just too annoying. Could someone please tell me how to disable GitBox’s sending commit notifications, or make it send to comm...@iotdb.apache.org