[jira] [Commented] (IOTDB-405) The result of 'SHOW' statements is ugly
[ https://issues.apache.org/jira/browse/IOTDB-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012528#comment-17012528 ] Jialin Qiao commented on IOTDB-405: --- Caching all printed results is feasible, as the performance of the CLI is not so important. > The result of 'SHOW' statements is ugly > --- > > Key: IOTDB-405 > URL: https://issues.apache.org/jira/browse/IOTDB-405 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Priority: Major > Fix For: 0.10.0-SNAPSHOT > > Attachments: Screen Shot 2020-01-07 at 3.21.28 PM.png > > > The header and the row data of result on client didn't have a same column > width. > This issue is only related to 'SHOW' statements. > !Screen Shot 2020-01-07 at 3.21.28 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Maintain user roles of IoTDB Jira
Hi Zhu, added. --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Boris Zhu 于2020年1月10日周五 下午12:59写道： > Hi, > My Jira id is geniuspig, please give me committer permission in jira. > > On Sat, Dec 14, 2019 at 1:04 PM Xiangdong Huang > wrote: > > > Hi all committers, > > > > Thanks @jincheng sun from Flink community, I find the position to > maintain > > users role on jira... > > > > Now the project Lead is Justin and Chris and me are administrator roles. > > > > So, if you are a committer and want to get the permission to assign > issues > > and close issues, please either: (1) tell me your jira user name; or (2) > > make sure you are using Apache id to login the JIRA (jira supports LDAP > > now) and tell me about that. Then I will give you the committer/PMC > roles. > > > > > > I would like to invite our other mentors to give me the user name and > then > > I can grant the permissions, too. > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > >
[jira] [Commented] (IOTDB-405) The result of 'SHOW' statements is ugly
[ https://issues.apache.org/jira/browse/IOTDB-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17012456#comment-17012456 ] Boris Zhu commented on IOTDB-405: - this is because we don’t know the length of time-series, we get results by rows instead of columns. In order to make it look better, we need to cache results. Or do you have another way? > The result of 'SHOW' statements is ugly > --- > > Key: IOTDB-405 > URL: https://issues.apache.org/jira/browse/IOTDB-405 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: Haonan Hou >Priority: Major > Fix For: 0.10.0-SNAPSHOT > > Attachments: Screen Shot 2020-01-07 at 3.21.28 PM.png > > > The header and the row data of result on client didn't have a same column > width. > This issue is only related to 'SHOW' statements. > !Screen Shot 2020-01-07 at 3.21.28 PM.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Maintain user roles of IoTDB Jira
Hi, My Jira id is geniuspig, please give me committer permission in jira. On Sat, Dec 14, 2019 at 1:04 PM Xiangdong Huang wrote: > Hi all committers, > > Thanks @jincheng sun from Flink community, I find the position to maintain > users role on jira... > > Now the project Lead is Justin and Chris and me are administrator roles. > > So, if you are a committer and want to get the permission to assign issues > and close issues, please either: (1) tell me your jira user name; or (2) > make sure you are using Apache id to login the JIRA (jira supports LDAP > now) and tell me about that. Then I will give you the committer/PMC roles. > > > I would like to invite our other mentors to give me the user name and then > I can grant the permissions, too. > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 >
[jira] [Created] (IOTDB-412) Paths are not correctly deduplicated
Tian Jiang created IOTDB-412: Summary: Paths are not correctly deduplicated Key: IOTDB-412 URL: https://issues.apache.org/jira/browse/IOTDB-412 Project: Apache IoTDB Issue Type: Bug Reporter: Tian Jiang Fix For: 0.10.0-SNAPSHOT Attachments: Paths are duplicated in GroupByPlan.docx Please check the attachment for details. I am not sure if other plans have the same problem, those who take over this should have a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
PPMC subscription to private mailing list
Hi, It a requirement for the PPMC to be signed up to the private mailing list. So far these PPMC members are currently not subscribed*: Gaofei Cao Jinrui Zhang Julian Feinauer Kun Liu Rong Kang Shuo Zhang Stefanie Zhao We also have a large number of unknown emails signed up, only PPMC members can be subscribed to this list. • yuct_...@lenovo.com (not recognised) • jimw...@mail.tsinghua.edu.cn (not recognised) • cg...@mails.tsinghua.edu.cn (not recognised) • wang_c...@tsinghua.edu.cn Chen Wang wangchen • jinrui.zh...@microsoft.com (not recognised) • daihui_...@lenovo.com (not recognised) • xyzha...@mails.tsinghua.edu.cn (not recognised) I’ll be giving i a few days and removing all of the above subscriptions. Thanks, Justin * Or are signed up from an unknown email address. To fix this your email address can be added at https://id.apache.org
Re: Please update the apache parent pom to version 22
Hu Jincheng, the information should be available here: https://maven.apache.org/guides/mini/guide-reproducible-builds.html However I would suggest to add another configuration to the build: apache-release com.theoryinpractise reproducible-maven-plugin org.apache.maven.plugins maven-release-plugin clean com.theoryinpractise:reproducible-maven-plugin:apply install com.theoryinpractise:reproducible-maven-plugin:clear deploy With this configuration the project.build.outputTimestamp property is added to the main pom as part of the release process and removed after that. So in general the build would not produce a reproducible build for SNAPSHOT versions, but reproducible builds for RELEASE versions and it wouldn't add additional steps for the release manager. Hope that's enough information for you folks. If not, just ask. Chris Am 09.01.20, 11:04 schrieb "jincheng sun" : +1 to upgrade the version. BTW: add the link [1] which more detail about `Reproducible Builds` that Chris mentioned. Best, Jincheng [1] http://maven.apache.org/pom/asf/ Christofer Dutz 于2020年1月9日周四 下午4:50写道： > Hi all, > > the maven team just released version 22 of the apache parent. > I would strongly suggest you update to this version. Not only because > Apache in general likes projects to release using the latest apache parent. > The main reason I think this is great is that with this you should > automatically be creating reproducible builds when releasing. > > Chris >
Re: [VOTE] Apache IoTDB (incubating) 0.9.1 RC1
Thank you Julian. Regards, Lei Rui On 1/9/2020 18:30，Xiangdong Huang wrote： Hi Julian, Welcome back~. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2020年1月9日周四 下午6:28写道： Hi, sorry for being late to the Party... My vote is +1 (binding, IPMC Vote) I did: - check out from svn - Check README, RELEASE_NOTES - Check Signatures, Hashes and Keys file (first release of Lei Rui) - Run "mvn clean install" on source release Minor Issue: With German Locale it does NOT work as one test fails due to decimal comma vs decimal point. But on US localeit works, so I think its okay - No unexpected binaries - Checked LICENSE and NOTICE Best Julian Am 03.01.20, 04:43 schrieb "Justin Mclean" : Hi, Do you think that when bring up a release VOTE, we need to add the PR of update the website in VOTE thread? The changes of the PR would be similar with No. You should only update the website after the IPMC vote has passes, the file put into the Apache mirrors and you waited 24 hours or so for the release to propagate. Thanks, Justin
Re: [DISCUSS] Add the components definition in JIRA template
Hi, Sure, maybe a bit more... - TsFile : A columnar file format that has flexible schema and data management for time series. - Storage : The storage engine of IoTDB, including writing to memtable (buffer), flushing, system recovery, and memtable management. - Query : The query process in IoTDB, including multiple types of queries, such as raw data query, aggregations, group by time, group by device. - Merge : Compaction of data files, including multiple compaction strategies, such as (1) merging unsequence TsFile with sequence TsFile, (2) merging small sequence TsFiles into a large TsFile. - Sync: Synchronize data files from one IoTDB instance to another. - Authority: Administration of IoTDB, including users, roles and privileges. - WAL : Write-ahead-log. - Client: Rpc between client and server, a command-line interface and client of different languages. - Distribution : The shared-nothing distribution of IoTDB, including raft protocol, data partition, and system information management. - Grafana : The connector for using IoTDB as a data source in Grafana. - Spark-TsFile : A connector that allows users read/write TsFile through SparkSQL (treat TsFile as an external data source for SparkSQL). - Spark-IoTDB : A connector that allows users read/write IoTDB through SparkSQL (treat IoTDB as an external data source for SparkSQL). - Hive-tsfile : A connector that maps TsFile as a table in Hive for the query. - Hadoop-tsfile : A connector that allows users read/write TsFile through MapReduce. - Tools : Other tools for IoTDB, such as watermark, memory estimation, JMX, query history visualization. - Example : Examples of different modules, such as JDBC, Session, TsFile. - WebSite : IoTDB official website. - Doc: documents of IoTDB, docs folder under root directory. - Other: Those do not belong to the above components. jincheng sun 于2020年1月9日周四 下午5:28写道： > Hi, > > @Xiangdong thank you for helping to clarify my original intention. you are > right, I really want to list some components to let users choose which > component the given issue belongs to. > > @Jialin I think approach 4 would be more meaningful for IoTDB. Could you > please add the detailed description for each component, such as, describe > the relationship between `tsfile` and > (`tsfile/hive-tsfile/spark-tsfile/Hadoop-tsfile`), and which changes belong > to `Other` component, etc., which can help us better understand the reasons > for such classification. On the other hand, we will further discuss whether > there is optimization space for this component classification. > > What do you think? > > Best, > Jincheng > > Xiangdong Huang 于2020年1月9日周四 下午4:46写道： > > > > No that is not the Apache Way. No one should be in charge of an area > > > > I think Jincheng's mean is, we can list some components to let users > > choose which component the given issue belongs to. > > > > As for which components should be listed, we need to have a discussion. > > > > > No one should be in charge of an area > > > > Yes everyone can assign an issue to himself/herself. > > > > Best, > > -- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > > > jincheng sun 于2020年1月9日周四 下午4:38写道： > > > > > > No that is not the Apache Way. No one should be in charge of an area. > > > > > > Oh, great thanks for correcting me Justin, maybe it's my language > > > expression problems. I mean some contributors and committers will be > very > > > interested in some components, then spend more time, and be more > familiar > > > with the code. > > > > > > Best, > > > Jincheng > > > > > > > > > Justin Mclean 于2020年1月9日周四 下午4:27写道： > > > > > > > Hi, > > > > > > > > > When our community grows stronger, each\ module may have some > > specific > > > > person in charge. > > > > > > > > No that is not the Apache Way. No one should be in charge of an area. > > > > > > > > Thanks, > > > > Justin > > > > > > -- — Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: [VOTE] Apache IoTDB (incubating) 0.9.1 RC1
Hi Julian, Welcome back~. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2020年1月9日周四 下午6:28写道： > Hi, > > sorry for being late to the Party... > > My vote is +1 (binding, IPMC Vote) > > I did: > - check out from svn > - Check README, RELEASE_NOTES > - Check Signatures, Hashes and Keys file (first release of Lei Rui) > - Run "mvn clean install" on source release > Minor Issue: With German Locale it does NOT work as one test fails due > to decimal comma vs decimal point. But on US localeit works, so I think its > okay > - No unexpected binaries > - Checked LICENSE and NOTICE > > Best > Julian > > Am 03.01.20, 04:43 schrieb "Justin Mclean" : > > Hi, > > > Do you think that when bring up a release VOTE, we need to add the > PR of > > update the website in VOTE thread? The changes of the PR would be > similar > > with > > No. You should only update the website after the IPMC vote has passes, > the file put into the Apache mirrors and you waited 24 hours or so for the > release to propagate. > > Thanks, > Justin > >
Re: [VOTE] Apache IoTDB (incubating) 0.9.1 RC1
Hi, sorry for being late to the Party... My vote is +1 (binding, IPMC Vote) I did: - check out from svn - Check README, RELEASE_NOTES - Check Signatures, Hashes and Keys file (first release of Lei Rui) - Run "mvn clean install" on source release Minor Issue: With German Locale it does NOT work as one test fails due to decimal comma vs decimal point. But on US localeit works, so I think its okay - No unexpected binaries - Checked LICENSE and NOTICE Best Julian Am 03.01.20, 04:43 schrieb "Justin Mclean" : Hi, > Do you think that when bring up a release VOTE, we need to add the PR of > update the website in VOTE thread? The changes of the PR would be similar > with No. You should only update the website after the IPMC vote has passes, the file put into the Apache mirrors and you waited 24 hours or so for the release to propagate. Thanks, Justin
Re: Please update the apache parent pom to version 22
+1 to upgrade the version. BTW: add the link [1] which more detail about `Reproducible Builds` that Chris mentioned. Best, Jincheng [1] http://maven.apache.org/pom/asf/ Christofer Dutz 于2020年1月9日周四 下午4:50写道： > Hi all, > > the maven team just released version 22 of the apache parent. > I would strongly suggest you update to this version. Not only because > Apache in general likes projects to release using the latest apache parent. > The main reason I think this is great is that with this you should > automatically be creating reproducible builds when releasing. > > Chris >
[jira] [Created] (IOTDB-411) Update the apache parent pom to version 22
sunjincheng created IOTDB-411: - Summary: Update the apache parent pom to version 22 Key: IOTDB-411 URL: https://issues.apache.org/jira/browse/IOTDB-411 Project: Apache IoTDB Issue Type: Improvement Reporter: sunjincheng Assignee: sunjincheng Fix For: 0.10.0 I think it's better to update the apache parent pom to version 22. as already mentioned by Chris in [1]. [1][https://lists.apache.org/thread.html/ra28b0ec17a7a971608770533b3525bc86f977666ad806f09a2d3f315%40%3Cdev.iotdb.apache.org%3E] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-409) Chinese and English documents are inconsistent (Chinese documents are incorrect)
[
https://issues.apache.org/jira/browse/IOTDB-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011615#comment-17011615
]
sunjincheng commented on IOTDB-409:
---
Agree with you [~qiaojialin]. I think the relative path used in the doc of
english version is very clear.
> Chinese and English documents are inconsistent (Chinese documents are
> incorrect)
>
>
> Key: IOTDB-409
> URL: https://issues.apache.org/jira/browse/IOTDB-409
> Project: Apache IoTDB
> Issue Type: Improvement
>Reporter: sunjincheng
>Priority: Major
> Attachments: image-2020-01-09-12-12-32-828.png,
> image-2020-01-09-12-13-13-306.png
>
>
> Chinese and English documents are inconsistent (Chinese documents are
> incorrect)， as follows:
> English:
> !image-2020-01-09-12-12-32-828.png|width=420,height=265!
> Chinese:
> !image-2020-01-09-12-13-13-306.png|width=408,height=306!
> In the current Chinese document, the user cannot know the directory
> `IOTDB_HOME` is
> `distribution/target/apache-iotdb-\{version}-SNAPSHOT-incubating-bin/apache-iotdb-{version}-SNAPSHOT-incubating`.
>
> What do you think?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [DISCUSS] Add the components definition in JIRA template
Hi, @Xiangdong thank you for helping to clarify my original intention. you are right, I really want to list some components to let users choose which component the given issue belongs to. @Jialin I think approach 4 would be more meaningful for IoTDB. Could you please add the detailed description for each component, such as, describe the relationship between `tsfile` and (`tsfile/hive-tsfile/spark-tsfile/Hadoop-tsfile`), and which changes belong to `Other` component, etc., which can help us better understand the reasons for such classification. On the other hand, we will further discuss whether there is optimization space for this component classification. What do you think? Best, Jincheng Xiangdong Huang 于2020年1月9日周四 下午4:46写道： > > No that is not the Apache Way. No one should be in charge of an area > > I think Jincheng's mean is, we can list some components to let users > choose which component the given issue belongs to. > > As for which components should be listed, we need to have a discussion. > > > No one should be in charge of an area > > Yes everyone can assign an issue to himself/herself. > > Best, > -- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > jincheng sun 于2020年1月9日周四 下午4:38写道： > > > > No that is not the Apache Way. No one should be in charge of an area. > > > > Oh, great thanks for correcting me Justin, maybe it's my language > > expression problems. I mean some contributors and committers will be very > > interested in some components, then spend more time, and be more familiar > > with the code. > > > > Best, > > Jincheng > > > > > > Justin Mclean 于2020年1月9日周四 下午4:27写道： > > > > > Hi, > > > > > > > When our community grows stronger, each\ module may have some > specific > > > person in charge. > > > > > > No that is not the Apache Way. No one should be in charge of an area. > > > > > > Thanks, > > > Justin > > >
[jira] [Commented] (IOTDB-409) Chinese and English documents are inconsistent (Chinese documents are incorrect)
[
https://issues.apache.org/jira/browse/IOTDB-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011578#comment-17011578
]
Jialin Qiao commented on IOTDB-409:
---
Hi, I suggest avoiding using the IOTDB_HOME in documents.
> Chinese and English documents are inconsistent (Chinese documents are
> incorrect)
>
>
> Key: IOTDB-409
> URL: https://issues.apache.org/jira/browse/IOTDB-409
> Project: Apache IoTDB
> Issue Type: Improvement
>Reporter: sunjincheng
>Priority: Major
> Attachments: image-2020-01-09-12-12-32-828.png,
> image-2020-01-09-12-13-13-306.png
>
>
> Chinese and English documents are inconsistent (Chinese documents are
> incorrect)， as follows:
> English:
> !image-2020-01-09-12-12-32-828.png|width=206,height=130!
> Chinese:
> !image-2020-01-09-12-13-13-306.png|width=408,height=306!
> In the current Chinese document, the user cannot know the directory
> `IOTDB_HOME` is
> `distribution/target/apache-iotdb-\{version}-SNAPSHOT-incubating-bin/apache-iotdb-\{version}-SNAPSHOT-incubating`.
>
> What do you think?
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Please update the apache parent pom to version 22
Hi all, the maven team just released version 22 of the apache parent. I would strongly suggest you update to this version. Not only because Apache in general likes projects to release using the latest apache parent. The main reason I think this is great is that with this you should automatically be creating reproducible builds when releasing. Chris
Re: [DISCUSS] Add the components definition in JIRA template
> No that is not the Apache Way. No one should be in charge of an area I think Jincheng's mean is, we can list some components to let users choose which component the given issue belongs to. As for which components should be listed, we need to have a discussion. > No one should be in charge of an area Yes everyone can assign an issue to himself/herself. Best, -- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 jincheng sun 于2020年1月9日周四 下午4:38写道： > > No that is not the Apache Way. No one should be in charge of an area. > > Oh, great thanks for correcting me Justin, maybe it's my language > expression problems. I mean some contributors and committers will be very > interested in some components, then spend more time, and be more familiar > with the code. > > Best, > Jincheng > > > Justin Mclean 于2020年1月9日周四 下午4:27写道： > > > Hi, > > > > > When our community grows stronger, each\ module may have some specific > > person in charge. > > > > No that is not the Apache Way. No one should be in charge of an area. > > > > Thanks, > > Justin >
Re: [DISCUSS] Add the components definition in JIRA template
> No that is not the Apache Way. No one should be in charge of an area. Oh, great thanks for correcting me Justin, maybe it's my language expression problems. I mean some contributors and committers will be very interested in some components, then spend more time, and be more familiar with the code. Best, Jincheng Justin Mclean 于2020年1月9日周四 下午4:27写道： > Hi, > > > When our community grows stronger, each\ module may have some specific > person in charge. > > No that is not the Apache Way. No one should be in charge of an area. > > Thanks, > Justin
Re: [DISCUSS] Add the components definition in JIRA template
Hi, Attaching a component of each issue will help contributors quickly locate the problem. This has nothing to do with specifying someone in a certain area, it just a classification of issues :) I would like to give an approach 4 - TsFile (module: tsfile) - Storage (StorageEngine in server module, including buffer management, flush management) - Query (Query processor in server module) - Merge (Compaction in server) - CLI (module: iotdb-client) - Rpc-client (modules: iotdb-jdbc, service-rpc, iotdb-session) - Python-client - Distribution - Grafana - Spark-TsFile - Spark-IoTDB - Hive-tsfile - Hadoop-tsfile - Example - WebSite - Doc - Other Justin Mclean 于2020年1月9日周四 下午4:27写道： > Hi, > > > When our community grows stronger, each\ module may have some specific > person in charge. > > No that is not the Apache Way. No one should be in charge of an area. > > Thanks, > Justin -- — Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
Re: [DISCUSS] Add the components definition in JIRA template
Hi, > When our community grows stronger, each\ module may have some specific person > in charge. No that is not the Apache Way. No one should be in charge of an area. Thanks, Justin
[DISCUSS] Add the components definition in JIRA template
Hi folks, Currently we can not select one components when create a JIRA. [1]. At present, this problem is not obvious because there are not many contributors of IoTDB, and the active committers need to have a certain understanding of each module. When our community grows stronger, each module may have some specific person in charge. At that time, it is meaningful for us to specify specific components for JIRA., because that way, the component owner can pay attention to them and discuss with the contributors. So my proposal is: Add the components definition in JIRA template [2](there is permission control, maybe PPMC should be able to access). If my proposal is accepted by IoTDB community, we should have a discussion about how to define the components for IoTDB. I'm not familiar with the components of IoTDB. Maybe PPMC such as Xiangdong and Jialin etc., and the committers of IoTDB will have better solutions. My two cents: Approach 1 (align the modules): - Client - Server - Tsfile - Spark-tsfile - Hadoop-tsfile - Spark-iotdb-connector - Hive-connector - Grafana - Distribution - Service-rpc - Jdbc - Session - Example - WebSite Approach 2(Grading management): - Client - Client-java - Client-py - Service-rpc - Jdbc - Session - Server - Tsfile - Spark-tsfile - Hadoop-tsfile - Connector - Spark-iotdb-connector - Hive-connector - Grafana - Distribution - Example - WebSite Approach 3(Pretty simple. We can expand it at any time): - Client - Server - Tsfile - Connector - Grafana - Distribution - Example - WebSite Approach 4（Other better options) Best, Jincheng [1] https://issues.apache.org/jira/browse/IOTDB-410 [2] https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/components
