Re: Binary Release of IoTDB

[Jialin Qiao]

Hi,

I think structure 3 is better than 1 and 2.

However, what makes the bin folder a mess is some tools script.

Could we move walcheck and sync related scripts from "server" to a folder named 
"tools", also csv import/export scripts from client to "tools"?

Besides, it's better to combine "run-client.bat" with "start-client.bat".

Best
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -原始邮件-
> 发件人: "RUI, LEI" <1010953...@qq.com>
> 发送时间: 2019-07-18 11:24:50 (星期四)
> 收件人: dev 
> 抄送: 
> 主题: 回复： Binary Release of IoTDB
> 
> Hi, I'm here to suggest another structure like this :)
> 
> 
> (Structure 3):
> .
> ├── LICENSE
> ├── NOTICE
> ├── changes.txt
> │
> ├── bin
> │   ├── client
> │   │   ├── export-csv.bat
> │   │   ├── export-csv.sh
> │   │   ├── import-csv.bat
> │   │   ├── import-csv.sh
> │   │   ├── run-client.bat
> │   │   ├── start-client.bat
> │   │   └── start-client.sh
> │   └── server
> │├── start-WalChecker.bat
> │├── start-WalChecker.sh
> │├── start-server.bat
> │├── start-server.sh
> │├── start-sync-client.bat
> │├── start-sync-client.sh
> │├── stop-server.bat
> │├── stop-server.sh
> │├── stop-sync-client.bat
> │└── stop-sync-client.sh
> │
> ├── conf
> │   ├── error_info_cn.properties
> │   ├── error_info_en.properties
> │   ├── iotdb-engine.properties
> │   ├── iotdb-env.bat
> │   ├── iotdb-env.sh
> │   ├── iotdb-sync-client.properties
> │   ├── logback.xml
> │   └── tsfile-format.properties
> │
> ├──  lib
> │   ├── client
> │   │   └── *.jar
> │   ├── server
> │   │   └── *.jar
> 
> │   └── common
> │   └── *.jar
> 
> │
> ├── licenses
> │   └── LICENCES
> │
> └── grafana-connector
>  ├── bin
>  │   ├── start-grafana-connector.bat
>  │   └── start-grafana-connector.sh
>  └── iotdb-grafana-0.8.0-SNAPSHOT.war
>  
> 
> 
> 
> 
> -- 原始邮件 --
> 发件人: "Justin Mclean";
> 发送时间: 2019年7月18日(星期四) 上午10:38
> 收件人: "dev";
> 
> 主题: Re: Binary Release of IoTDB
> 
> 
> 
> Hi,
> There should be no need to vote on something like this try to reach
> consensus by discussion.
> Thanks.
> Justin
> 
> On Thu, 18 Jul 2019, 12:35 Xiangdong Huang,  wrote:
> 
> > Hi,
> >
> > any other opinion?
> >
> > We need to make a decision asap
> >
> > Because there is some divergence, do we need a vote?
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Jialin Qiao  于2019年7月17日周三 下午3:39写道：
> >
> > > Hi,
> > >
> > > I prefer the first structure that assembles all scripts in the "bin"
> > > folder and all jars in the "lib" folder.
> > >
> > > Suppose I am a user, I would expect that the structure is as clear and
> > > simple as possible.
> > >
> > > Thanks,
> > > --
> > > Jialin Qiao
> > > School of Software, Tsinghua University
> > >
> > > 乔嘉林
> > > 清华大学 软件学院
> > >
> > > > -原始邮件-
> > > > 发件人: "Xiangdong Huang" 
> > > > 发送时间: 2019-07-17 14:18:10 (星期三)
> > > > 收件人: dev@iotdb.apache.org
> > > > 抄送:
> > > > 主题: Re: Binary Release of IoTDB
> > > >
> > > > Hi,
> > > >
> > > > Though I also think the second structure is more clear, many databases
> > > > projects use the structure 1... e.g, Cassandra.
> > > >
> > > > When using structure 2, there are some jars both in the client/lib/ and
> > > the
> > > > server/lib/, which will enlarge the binary file.
> > > >
> > > > Do we need to extract them out and put them into another folder?
> > > Something
> > > > like:
> > > > .
> > > > ├── client
> > > > │   └── lib
> > > > ├── common
> > > > │   └── lib
> > > > └── server
> > > > └── lib
> > > >
> > > > Best,
> > > > ---
> > > > Xiangdong Huang
> > > > School of Software, Tsinghua University
> > > >
> > > >  黄向东
> > > > 清华大学 软件学院
> > > >
> > > >
> > > > Julian Feinauer  于2019年7月16日周二
> > 下午11:27写道：
> > > >
> > > > > Hi,
> > > > >
> > > > > I would prefer structure 2 and I really like it.
> > > > > And we should add a readme.txt with short usage instructions.
> > > > >
> > > > > Julian
> > > > >
> > > > > Am 16.07.19, 13:58 schrieb "Xiangdong Huang" :
> > > > >
> > > > > Hi,
> > > > >
> > > > > I think the structure of the binaries can be:
> > > > >
> > > > > (Structure 1):
> > > > > .
> > > > > ├── LICENSE
> > > > > ├── NOTICE
> > > > > ├── bin
> > > > > │   ├── export-csv.bat
> > > > > │   ├── export-csv.sh
> > > > > │   ├── import-csv.bat
> > > > > │   ├── import-csv.sh
> > > > > │   ├── run-client.bat
> > > > > │   ├── start-WalChecker.bat
> > > > > │   ├── start-WalChecker.sh
> > > > > │   ├── start-client.bat
> > > > > │   ├── start-client.sh
> > > > > │   ├── start-grafana-connector.bat
> > > > > │   ├── start-grafana-connector.sh
> > > > > │   ├── start-server.bat
> > > > > │   ├── start-server.sh
> > > > > │   ├── start-sync-client.bat
> > > > > 

回复： Binary Release of IoTDB

[RUI, LEI]

Hi, I'm here to suggest another structure like this :)


(Structure 3):
.
├── LICENSE
├── NOTICE
├── changes.txt
│
├── bin
│   ├── client
│   │   ├── export-csv.bat
│   │   ├── export-csv.sh
│   │   ├── import-csv.bat
│   │   ├── import-csv.sh
│   │   ├── run-client.bat
│   │   ├── start-client.bat
│   │   └── start-client.sh
│   └── server
│├── start-WalChecker.bat
│├── start-WalChecker.sh
│├── start-server.bat
│├── start-server.sh
│├── start-sync-client.bat
│├── start-sync-client.sh
│├── stop-server.bat
│├── stop-server.sh
│├── stop-sync-client.bat
│└── stop-sync-client.sh
│
├── conf
│   ├── error_info_cn.properties
│   ├── error_info_en.properties
│   ├── iotdb-engine.properties
│   ├── iotdb-env.bat
│   ├── iotdb-env.sh
│   ├── iotdb-sync-client.properties
│   ├── logback.xml
│   └── tsfile-format.properties
│
├──  lib
│   ├── client
│   │   └── *.jar
│   ├── server
│   │   └── *.jar

│   └── common
│   └── *.jar

│
├── licenses
│   └── LICENCES
│
└── grafana-connector
 ├── bin
 │   ├── start-grafana-connector.bat
 │   └── start-grafana-connector.sh
 └── iotdb-grafana-0.8.0-SNAPSHOT.war
 




-- 原始邮件 --
发件人: "Justin Mclean";
发送时间: 2019年7月18日(星期四) 上午10:38
收件人: "dev";

主题: Re: Binary Release of IoTDB



Hi,
There should be no need to vote on something like this try to reach
consensus by discussion.
Thanks.
Justin

On Thu, 18 Jul 2019, 12:35 Xiangdong Huang,  wrote:

> Hi,
>
> any other opinion?
>
> We need to make a decision asap
>
> Because there is some divergence, do we need a vote?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Jialin Qiao  于2019年7月17日周三 下午3:39写道：
>
> > Hi,
> >
> > I prefer the first structure that assembles all scripts in the "bin"
> > folder and all jars in the "lib" folder.
> >
> > Suppose I am a user, I would expect that the structure is as clear and
> > simple as possible.
> >
> > Thanks,
> > --
> > Jialin Qiao
> > School of Software, Tsinghua University
> >
> > 乔嘉林
> > 清华大学 软件学院
> >
> > > -原始邮件-
> > > 发件人: "Xiangdong Huang" 
> > > 发送时间: 2019-07-17 14:18:10 (星期三)
> > > 收件人: dev@iotdb.apache.org
> > > 抄送:
> > > 主题: Re: Binary Release of IoTDB
> > >
> > > Hi,
> > >
> > > Though I also think the second structure is more clear, many databases
> > > projects use the structure 1... e.g, Cassandra.
> > >
> > > When using structure 2, there are some jars both in the client/lib/ and
> > the
> > > server/lib/, which will enlarge the binary file.
> > >
> > > Do we need to extract them out and put them into another folder?
> > Something
> > > like:
> > > .
> > > ├── client
> > > │   └── lib
> > > ├── common
> > > │   └── lib
> > > └── server
> > > └── lib
> > >
> > > Best,
> > > ---
> > > Xiangdong Huang
> > > School of Software, Tsinghua University
> > >
> > >  黄向东
> > > 清华大学 软件学院
> > >
> > >
> > > Julian Feinauer  于2019年7月16日周二
> 下午11:27写道：
> > >
> > > > Hi,
> > > >
> > > > I would prefer structure 2 and I really like it.
> > > > And we should add a readme.txt with short usage instructions.
> > > >
> > > > Julian
> > > >
> > > > Am 16.07.19, 13:58 schrieb "Xiangdong Huang" :
> > > >
> > > > Hi,
> > > >
> > > > I think the structure of the binaries can be:
> > > >
> > > > (Structure 1):
> > > > .
> > > > ├── LICENSE
> > > > ├── NOTICE
> > > > ├── bin
> > > > │   ├── export-csv.bat
> > > > │   ├── export-csv.sh
> > > > │   ├── import-csv.bat
> > > > │   ├── import-csv.sh
> > > > │   ├── run-client.bat
> > > > │   ├── start-WalChecker.bat
> > > > │   ├── start-WalChecker.sh
> > > > │   ├── start-client.bat
> > > > │   ├── start-client.sh
> > > > │   ├── start-grafana-connector.bat
> > > > │   ├── start-grafana-connector.sh
> > > > │   ├── start-server.bat
> > > > │   ├── start-server.sh
> > > > │   ├── start-sync-client.bat
> > > > │   ├── start-sync-client.sh
> > > > │   ├── stop-server.bat
> > > > │   ├── stop-server.sh
> > > > │   ├── stop-sync-client.bat
> > > > │   └── stop-sync-client.sh
> > > > ├── changes.txt
> > > > ├── conf
> > > > │   ├── error_info_cn.properties
> > > > │   ├── error_info_en.properties
> > > > │   ├── iotdb-engine.properties
> > > > │   ├── iotdb-env.bat
> > > > │   ├── iotdb-env.sh
> > > > │   ├── iotdb-sync-client.properties
> > > > │   ├── logback.xml
> > > > │   └── tsfile-format.properties
> > > > ├── lib
> > > > │   └── *.jar
> > > > └── licenses
> > > > └── LICENCES
> > > >
> > > > (Structure 2):
> > > > .
> > > > ├── LICENSE
> > > > ├── NOTICE
> > > > ├── changes.txt
> > > > ├── client
> > > > │   ├── bin
> > > > │   │   ├── export-csv.bat
> > > > │   │   ├── export-csv.sh
> > > > │   │   

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 MBs do not count.

I also think we can use a customizable download link to provide multiple choice 
for the users so they may choose which extension binaries they want.

Thanks

Tian Jiang

Re: Binary Release of IoTDB

[Xiangdong Huang]

Hi,

any other opinion?

We need to make a decision asap

Because there is some divergence, do we need a vote?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Jialin Qiao  于2019年7月17日周三 下午3:39写道：

> Hi,
>
> I prefer the first structure that assembles all scripts in the "bin"
> folder and all jars in the "lib" folder.
>
> Suppose I am a user, I would expect that the structure is as clear and
> simple as possible.
>
> Thanks,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> > -原始邮件-
> > 发件人: "Xiangdong Huang" 
> > 发送时间: 2019-07-17 14:18:10 (星期三)
> > 收件人: dev@iotdb.apache.org
> > 抄送:
> > 主题: Re: Binary Release of IoTDB
> >
> > Hi,
> >
> > Though I also think the second structure is more clear, many databases
> > projects use the structure 1... e.g, Cassandra.
> >
> > When using structure 2, there are some jars both in the client/lib/ and
> the
> > server/lib/, which will enlarge the binary file.
> >
> > Do we need to extract them out and put them into another folder?
> Something
> > like:
> > .
> > ├── client
> > │   └── lib
> > ├── common
> > │   └── lib
> > └── server
> > └── lib
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Julian Feinauer  于2019年7月16日周二 下午11:27写道：
> >
> > > Hi,
> > >
> > > I would prefer structure 2 and I really like it.
> > > And we should add a readme.txt with short usage instructions.
> > >
> > > Julian
> > >
> > > Am 16.07.19, 13:58 schrieb "Xiangdong Huang" :
> > >
> > > Hi,
> > >
> > > I think the structure of the binaries can be:
> > >
> > > (Structure 1):
> > > .
> > > ├── LICENSE
> > > ├── NOTICE
> > > ├── bin
> > > │   ├── export-csv.bat
> > > │   ├── export-csv.sh
> > > │   ├── import-csv.bat
> > > │   ├── import-csv.sh
> > > │   ├── run-client.bat
> > > │   ├── start-WalChecker.bat
> > > │   ├── start-WalChecker.sh
> > > │   ├── start-client.bat
> > > │   ├── start-client.sh
> > > │   ├── start-grafana-connector.bat
> > > │   ├── start-grafana-connector.sh
> > > │   ├── start-server.bat
> > > │   ├── start-server.sh
> > > │   ├── start-sync-client.bat
> > > │   ├── start-sync-client.sh
> > > │   ├── stop-server.bat
> > > │   ├── stop-server.sh
> > > │   ├── stop-sync-client.bat
> > > │   └── stop-sync-client.sh
> > > ├── changes.txt
> > > ├── conf
> > > │   ├── error_info_cn.properties
> > > │   ├── error_info_en.properties
> > > │   ├── iotdb-engine.properties
> > > │   ├── iotdb-env.bat
> > > │   ├── iotdb-env.sh
> > > │   ├── iotdb-sync-client.properties
> > > │   ├── logback.xml
> > > │   └── tsfile-format.properties
> > > ├── lib
> > > │   └── *.jar
> > > └── licenses
> > > └── LICENCES
> > >
> > > (Structure 2):
> > > .
> > > ├── LICENSE
> > > ├── NOTICE
> > > ├── changes.txt
> > > ├── client
> > > │   ├── bin
> > > │   │   ├── export-csv.bat
> > > │   │   ├── export-csv.sh
> > > │   │   ├── import-csv.bat
> > > │   │   ├── import-csv.sh
> > > │   │   ├── run-client.bat
> > > │   │   ├── start-client.bat
> > > │   │   └── start-client.sh
> > > │   └── lib
> > > │   └──  *.jar
> > > ├── grafana-connector
> > > │   ├── bin
> > > │   │   ├── start-grafana-connector.bat
> > > │   │   └── start-grafana-connector.sh
> > > │   └── iotdb-grafana-0.8.0-SNAPSHOT.war
> > > ├── licenses
> > > │   └── LICENCES
> > > └── server
> > > ├── bin
> > > │   ├── start-WalChecker.bat
> > > │   ├── start-WalChecker.sh
> > > │   ├── start-server.bat
> > > │   ├── start-server.sh
> > > │   ├── start-sync-client.bat
> > > │   ├── start-sync-client.sh
> > > │   ├── stop-server.bat
> > > │   ├── stop-server.sh
> > > │   ├── stop-sync-client.bat
> > > │   └── stop-sync-client.sh
> > > ├── conf
> > > │   ├── error_info_cn.properties
> > > │   ├── error_info_en.properties
> > > │   ├── iotdb-engine.properties
> > > │   ├── iotdb-env.bat
> > > │   ├── iotdb-env.sh
> > > │   ├── iotdb-sync-client.properties
> > > │   ├── logback.xml
> > > │   └── tsfile-format.properties
> > > └── lib
> > > └──  *.jar
> > >
> > > In structure 1, CLI and server scripts  are in the same folder, so
> > > does the
> > > libs. In structure 2, CLI and server module are seperated.
> > >
> > > The first one has smaller size because the two modules have some
> > > duplicated
> > > libs.
> > >
> > > Best,
> > > ---
> > > Xiangdong Huang
> > > School of Software, Tsinghua University
> > >
> > >  黄向东

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

[BUILD-FAILURE]: Job 'IoTDB-Pipeline/master [master] [135]'

[Apache Jenkins Server]

BUILD-FAILURE: Job 'IoTDB-Pipeline/master [master] [135]':

Check console output at "https://builds.apache.org/job/IoTDB-Pipeline/job/master/135/;>IoTDB-Pipeline/master
 [master] [135]"

Re: [BUILD-FAILURE]: Job 'IoTDB-Pipeline/master [master] [134]'

[Xiangdong Huang]

The failure reason is “stderr: fatal: unable to access '
https://github.com/apache/incubator-iotdb.git/': Could not resolve host:
github.com”

This is the second time The malfunction occurs...

Apache Jenkins Server 于2019年7月18日 周四上午7:36写道：

> BUILD-FAILURE: Job 'IoTDB-Pipeline/master [master] [134]':
>
> Check console output at "https://builds.apache.org/job/IoTDB-Pipeline/job/master/134/;>IoTDB-Pipeline/master
> [master] [134]"

-- 
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院

[BUILD-FAILURE]: Job 'IoTDB-Pipeline/master [master] [134]'

[Apache Jenkins Server]

BUILD-FAILURE: Job 'IoTDB-Pipeline/master [master] [134]':

Check console output at "https://builds.apache.org/job/IoTDB-Pipeline/job/master/134/;>IoTDB-Pipeline/master
 [master] [134]"

[jira] [Created] (IOTDB-143) Support merge

[Tian Jiang (JIRA)]

Tian Jiang created IOTDB-143:


 Summary: Support merge
 Key: IOTDB-143
 URL: https://issues.apache.org/jira/browse/IOTDB-143
 Project: Apache IoTDB
  Issue Type: New Feature
Reporter: Tian Jiang


Merge (or compaction) is an important feature of LSM or LSM-like systems and 
IoTDB depends on it to put the data in the sequential files and unsequential 
files together and make them ordered and non-duplicated again.

Merged data files provide better locality and potentially higher compression 
rate (for some of the missing values are supplemented). While merging interacts 
with many aspects of IoTDB like ingestion and query, finding an effective 
implementation may be rather difficult.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (IOTDB-142) Change String literal "UTF-8" into StandardCharsets.UTF_8

[JIRA]

朱天赐 created IOTDB-142:
-

 Summary: Change String literal "UTF-8" into StandardCharsets.UTF_8
 Key: IOTDB-142
 URL: https://issues.apache.org/jira/browse/IOTDB-142
 Project: Apache IoTDB
  Issue Type: Improvement
Reporter: 朱天赐


methods and constructors where constant charset String literal is used (like 
"UTF-8") which could be replaced with a predefined Charset object like 
StandardCharsets.UTF_8. This may work a little bit faster because charset 
lookup becomes unnecessary. Also catching UnsupportedEncodingException may 
become unnecessary as well. In this case, the catch block will be removed 
automatically.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Closed] (IOTDB-122) Support prepared insertion

[Tian Jiang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IOTDB-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tian Jiang closed IOTDB-122.


> Support prepared insertion
> --
>
> Key: IOTDB-122
> URL: https://issues.apache.org/jira/browse/IOTDB-122
> Project: Apache IoTDB
>  Issue Type: New Feature
>Reporter: Tian Jiang
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> As some have mentioned, sql parser(antlr) may consume about 40% of time in 
> ingestion, especially when small sqls executed sent frequently. Luckily, 
> IoTDB insertion sqls are currently all alike and simple, there are 4 most 
> meaningful parts of such sqls: deviceId, measurements, values and time. For 
> such a simple structure, using tools like antlr may be just too heavy.
> Intuitively, PreparedStatement in Standard JDBC interface can be just used 
> for reliving parsing overhead when sqls are similar. I will describe how 
> PreparedStatement works as follow (this is still left to be implemented):
> 1. The user wants to create a prepared insert statement and called 
> `connection.prepareStatement(“Insert”)`;
> 2. The connection matches the parameter string with some templates, finds out 
> it is an insertion and returns an IoTDBPreparedInsertStatement pStmt.
> 3. The user calls `pStmt.setDevice(“root.device1”); pStmt.setTime(100); 
> pStmt.setMeasurements(measurementArray); pStmt.setValues(valueArray);` to set 
> parameters for next insertion.
> 4. The user calls `pStmt.execute()` to execute an insertion.
> 5. The PreparedInsertStatement creates a TSInsertionReq, puts deviceId, 
> measurements, values and time into this request and sends this request to the 
> server.
> 6. The server receives the request, extracts parameters from the request and 
> executes an insertion directly through database engine and return a 
> TSInsertionResp to the user.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Memory estimation tool

[李天安]

Hi, Jialin:
Actually, I have written an docu to show how to use this tool, and it has been 
submitted to this pr. https://github.com/apache/incubator-iotdb/pull/256 


Best Regards,
—
Tianan Li
School of Software, Tsinghua University

李天安
清华大学 软件学院

> 在 2019年7月17日，下午4:44，Jialin Qiao  写道：
> 
> Hi Tianan,
> 
> Nice work, This is very useful! 
> 
> Could you add an example (command) about how to use this tool?
> 
> Thanks,
> --
> Jialin Qiao
> School of Software, Tsinghua University
> 
> 乔嘉林
> 清华大学 软件学院
> 
>> -原始邮件-
>> 发件人: "李天安" 
>> 发送时间: 2019-07-17 14:57:51 (星期三)
>> 收件人: dev@iotdb.apache.org
>> 抄送: 
>> 主题: Memory estimation tool
>> 
>> Hi, 
>> 
>> 
>> Recently, I participated in the development of the dynamic parameter adapter 
>> module[https://github.com/apache/incubator-iotdb/pull/232], which can 
>> dynamically adjust system parameters according to load conditions. When we 
>> have the above module, I think we can develop a cooler thing: the memory 
>> estimation tool. When users provide the number of storage groups and 
>> timeseries according to the workload, the memory estimation tool can give 
>> the minimum memory for writing to meet the workload.
>> 
>> 
>> I think this tool is very useful and I have started to develop it 
>> [https://github.com/apache/incubator-iotdb/pull/256].
>> 
>> 
>> Anyone interested in this tool can discuss it here together.
>> 
>> 
>> Best Regards,
>> —
>> Tianan Li
>> School of Software, Tsinghua University
>> 
>> 
>> 

Re: Binary Release of IoTDB

[Jialin Qiao]

Hi,

I prefer the first structure that assembles all scripts in the "bin" folder and 
all jars in the "lib" folder. 

Suppose I am a user, I would expect that the structure is as clear and simple 
as possible.

Thanks,
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -原始邮件-
> 发件人: "Xiangdong Huang" 
> 发送时间: 2019-07-17 14:18:10 (星期三)
> 收件人: dev@iotdb.apache.org
> 抄送: 
> 主题: Re: Binary Release of IoTDB
> 
> Hi,
> 
> Though I also think the second structure is more clear, many databases
> projects use the structure 1... e.g, Cassandra.
> 
> When using structure 2, there are some jars both in the client/lib/ and the
> server/lib/, which will enlarge the binary file.
> 
> Do we need to extract them out and put them into another folder? Something
> like:
> .
> ├── client
> │   └── lib
> ├── common
> │   └── lib
> └── server
> └── lib
> 
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
> 
>  黄向东
> 清华大学 软件学院
> 
> 
> Julian Feinauer  于2019年7月16日周二 下午11:27写道：
> 
> > Hi,
> >
> > I would prefer structure 2 and I really like it.
> > And we should add a readme.txt with short usage instructions.
> >
> > Julian
> >
> > Am 16.07.19, 13:58 schrieb "Xiangdong Huang" :
> >
> > Hi,
> >
> > I think the structure of the binaries can be:
> >
> > (Structure 1):
> > .
> > ├── LICENSE
> > ├── NOTICE
> > ├── bin
> > │   ├── export-csv.bat
> > │   ├── export-csv.sh
> > │   ├── import-csv.bat
> > │   ├── import-csv.sh
> > │   ├── run-client.bat
> > │   ├── start-WalChecker.bat
> > │   ├── start-WalChecker.sh
> > │   ├── start-client.bat
> > │   ├── start-client.sh
> > │   ├── start-grafana-connector.bat
> > │   ├── start-grafana-connector.sh
> > │   ├── start-server.bat
> > │   ├── start-server.sh
> > │   ├── start-sync-client.bat
> > │   ├── start-sync-client.sh
> > │   ├── stop-server.bat
> > │   ├── stop-server.sh
> > │   ├── stop-sync-client.bat
> > │   └── stop-sync-client.sh
> > ├── changes.txt
> > ├── conf
> > │   ├── error_info_cn.properties
> > │   ├── error_info_en.properties
> > │   ├── iotdb-engine.properties
> > │   ├── iotdb-env.bat
> > │   ├── iotdb-env.sh
> > │   ├── iotdb-sync-client.properties
> > │   ├── logback.xml
> > │   └── tsfile-format.properties
> > ├── lib
> > │   └── *.jar
> > └── licenses
> > └── LICENCES
> >
> > (Structure 2):
> > .
> > ├── LICENSE
> > ├── NOTICE
> > ├── changes.txt
> > ├── client
> > │   ├── bin
> > │   │   ├── export-csv.bat
> > │   │   ├── export-csv.sh
> > │   │   ├── import-csv.bat
> > │   │   ├── import-csv.sh
> > │   │   ├── run-client.bat
> > │   │   ├── start-client.bat
> > │   │   └── start-client.sh
> > │   └── lib
> > │   └──  *.jar
> > ├── grafana-connector
> > │   ├── bin
> > │   │   ├── start-grafana-connector.bat
> > │   │   └── start-grafana-connector.sh
> > │   └── iotdb-grafana-0.8.0-SNAPSHOT.war
> > ├── licenses
> > │   └── LICENCES
> > └── server
> > ├── bin
> > │   ├── start-WalChecker.bat
> > │   ├── start-WalChecker.sh
> > │   ├── start-server.bat
> > │   ├── start-server.sh
> > │   ├── start-sync-client.bat
> > │   ├── start-sync-client.sh
> > │   ├── stop-server.bat
> > │   ├── stop-server.sh
> > │   ├── stop-sync-client.bat
> > │   └── stop-sync-client.sh
> > ├── conf
> > │   ├── error_info_cn.properties
> > │   ├── error_info_en.properties
> > │   ├── iotdb-engine.properties
> > │   ├── iotdb-env.bat
> > │   ├── iotdb-env.sh
> > │   ├── iotdb-sync-client.properties
> > │   ├── logback.xml
> > │   └── tsfile-format.properties
> > └── lib
> > └──  *.jar
> >
> > In structure 1, CLI and server scripts  are in the same folder, so
> > does the
> > libs. In structure 2, CLI and server module are seperated.
> >
> > The first one has smaller size because the two modules have some
> > duplicated
> > libs.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Christofer Dutz  于2019年7月16日周二 下午7:10写道：
> >
> > > Bash scripts are not portable.
> > > I would strongly advise not to use them and with the assembly
> > plugin, the
> > > binary stuff gets packaged alongside the source bundle during the
> > release
> > > build.
> > >
> > > Chris
> > >
> > > Holen Sie sichOutlook für Android
> > >
> > > 
> > > From: Julian Feinauer 
> > > Sent: Tuesday, July 16, 2019 12:39:51 PM
> > > To: 

[jira] [Created] (IOTDB-141) Memory estimation tool

[litianan (JIRA)]

litianan created IOTDB-141:
--

 Summary: Memory estimation tool
 Key: IOTDB-141
 URL: https://issues.apache.org/jira/browse/IOTDB-141
 Project: Apache IoTDB
  Issue Type: New Feature
Reporter: litianan


Currently, we have a dynamic parameter adapter module, so based on this module, 
it's better to develop a memory estimation tool for users to use. Users provide 
the number of storage groups and the number of timeseries according to their 
workloads, and the tool gives the minimum memory for writing to satisfy the 
load.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Re: Binary Release of IoTDB

[Xiangdong Huang]

Hi,

Though I also think the second structure is more clear, many databases
projects use the structure 1... e.g, Cassandra.

When using structure 2, there are some jars both in the client/lib/ and the
server/lib/, which will enlarge the binary file.

Do we need to extract them out and put them into another folder? Something
like:
.
├── client
│   └── lib
├── common
│   └── lib
└── server
└── lib

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年7月16日周二 下午11:27写道：

> Hi,
>
> I would prefer structure 2 and I really like it.
> And we should add a readme.txt with short usage instructions.
>
> Julian
>
> Am 16.07.19, 13:58 schrieb "Xiangdong Huang" :
>
> Hi,
>
> I think the structure of the binaries can be:
>
> (Structure 1):
> .
> ├── LICENSE
> ├── NOTICE
> ├── bin
> │   ├── export-csv.bat
> │   ├── export-csv.sh
> │   ├── import-csv.bat
> │   ├── import-csv.sh
> │   ├── run-client.bat
> │   ├── start-WalChecker.bat
> │   ├── start-WalChecker.sh
> │   ├── start-client.bat
> │   ├── start-client.sh
> │   ├── start-grafana-connector.bat
> │   ├── start-grafana-connector.sh
> │   ├── start-server.bat
> │   ├── start-server.sh
> │   ├── start-sync-client.bat
> │   ├── start-sync-client.sh
> │   ├── stop-server.bat
> │   ├── stop-server.sh
> │   ├── stop-sync-client.bat
> │   └── stop-sync-client.sh
> ├── changes.txt
> ├── conf
> │   ├── error_info_cn.properties
> │   ├── error_info_en.properties
> │   ├── iotdb-engine.properties
> │   ├── iotdb-env.bat
> │   ├── iotdb-env.sh
> │   ├── iotdb-sync-client.properties
> │   ├── logback.xml
> │   └── tsfile-format.properties
> ├── lib
> │   └── *.jar
> └── licenses
> └── LICENCES
>
> (Structure 2):
> .
> ├── LICENSE
> ├── NOTICE
> ├── changes.txt
> ├── client
> │   ├── bin
> │   │   ├── export-csv.bat
> │   │   ├── export-csv.sh
> │   │   ├── import-csv.bat
> │   │   ├── import-csv.sh
> │   │   ├── run-client.bat
> │   │   ├── start-client.bat
> │   │   └── start-client.sh
> │   └── lib
> │   └──  *.jar
> ├── grafana-connector
> │   ├── bin
> │   │   ├── start-grafana-connector.bat
> │   │   └── start-grafana-connector.sh
> │   └── iotdb-grafana-0.8.0-SNAPSHOT.war
> ├── licenses
> │   └── LICENCES
> └── server
> ├── bin
> │   ├── start-WalChecker.bat
> │   ├── start-WalChecker.sh
> │   ├── start-server.bat
> │   ├── start-server.sh
> │   ├── start-sync-client.bat
> │   ├── start-sync-client.sh
> │   ├── stop-server.bat
> │   ├── stop-server.sh
> │   ├── stop-sync-client.bat
> │   └── stop-sync-client.sh
> ├── conf
> │   ├── error_info_cn.properties
> │   ├── error_info_en.properties
> │   ├── iotdb-engine.properties
> │   ├── iotdb-env.bat
> │   ├── iotdb-env.sh
> │   ├── iotdb-sync-client.properties
> │   ├── logback.xml
> │   └── tsfile-format.properties
> └── lib
> └──  *.jar
>
> In structure 1, CLI and server scripts  are in the same folder, so
> does the
> libs. In structure 2, CLI and server module are seperated.
>
> The first one has smaller size because the two modules have some
> duplicated
> libs.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Christofer Dutz  于2019年7月16日周二 下午7:10写道：
>
> > Bash scripts are not portable.
> > I would strongly advise not to use them and with the assembly
> plugin, the
> > binary stuff gets packaged alongside the source bundle during the
> release
> > build.
> >
> > Chris
> >
> > Holen Sie sichOutlook für Android
> >
> > 
> > From: Julian Feinauer 
> > Sent: Tuesday, July 16, 2019 12:39:51 PM
> > To: dev@iotdb.apache.org
> > Subject: AW: Binary Release of IoTDB
> >
> > Hey Chris,
> >
> > I also thought about that and... Contacting you :P
> > But I thought about a bash script :)
> >
> > Julian
> >
> > Von meinem Mobiltelefon gesendet
> >
> >
> >  Ursprüngliche Nachricht 
> > Betreff: Re: Binary Release of IoTDB
> > Von: Christofer Dutz
> > An: dev@iotdb.apache.org
> > Cc:
> >
> > We could whip up a maven assembly für building that binary
> distribution. I
> > could help with that, if you exactly define how it should look.
> >
> > Chris
> >
> > Holen Sie sichOutlook für Android
> >
> > 
> > 

AW: A task list needed for releasing 0.8

[Julian Feinauer]

Hi,

Yes and I am about to sketch one based on what we use in the plc4x project 
https://plc4x.apache.org/developers/release.html

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: A task list needed for releasing 0.8
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

> - Create a release page on JIRA (Em, and I am not very sure what the page
> is used for. @Julian )

You need a release page on the web site.

Thanks,
Justin

Re: A task list needed for releasing 0.8

[Justin Mclean]

Hi,

> - Create a release page on JIRA (Em, and I am not very sure what the page
> is used for. @Julian )

You need a release page on the web site.

Thanks,
Justin

Re: [BUILD-FAILURE]: Job 'IoTDB Website [null] [54]'

[Xiangdong Huang]

Please ignore this message, and I just want to try whether the Apache
Jenkins has been fixed for `npm install` command. See [1].

[1] https://issues.apache.org/jira/browse/INFRA-18700
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Apache Jenkins Server  于2019年7月17日周三 下午2:06写道：

> BUILD-FAILURE: Job 'IoTDB Website [null] [54]':
>
> Check console output at "https://builds.apache.org/job/IoTDB%20Website/54/;>IoTDB Website [null]
> [54]"

[BUILD-FAILURE]: Job 'IoTDB Website [null] [54]'

[Apache Jenkins Server]

BUILD-FAILURE: Job 'IoTDB Website [null] [54]':

Check console output at "https://builds.apache.org/job/IoTDB%20Website/54/;>IoTDB Website [null] 
[54]"

A task list needed for releasing 0.8

[Xiangdong Huang]

Hi all,

Thanks for Julian's push, now the work for releasing have begun  :D.

I think we have many tasks to finish it, can we maintain a task list for
the releasing? And, once a task is finished, we can scratch it out. (Where
to maintain this list? As an issues? or just in the mailing list?)

Some tasks I can consider are:

- create rel/0.8 branch (done)
- Write release notes (done)

- File structure of the Binary Release (discussing in thread [1])

- Create a release page on JIRA (Em, and I am not very sure what the page
is used for. @Julian )

- (Optional but I think we can do that) Merging PR #249, #247, #251, #252.
All of them are for updating English user manual. (Guys, hurry up for
reviewing them)

- More tasks ...

Reiterate once again: if some PRs are need to be merged in both the rel/0.8
and the master, do not miss any one of them.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院