Re: Considering the first Meetup of IoTDB in Beijing
Hi all, The meetup time is confirmed! Date: Jan, 04, 2020 Time: 13:00 - 17:00 Location: FIT Building, Tsinghua University, Beijing, China. There are 5 talks totally, 3 for Apache Pulsar, and 2 for Apache IoTDB (Jialin and me). Event info and register: http://www.huodongxing.com/event/4522241401100 Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年12月10日周二 下午6:48写道： > Hi, > > I would like to give a talk about the architecture and some components of > IoTDB. > > Thanks, > Jialin Qiao > > Xiangdong Huang 于2019年12月10日周二 下午5:24写道： > > > Hi all, > > > > Some guys from Apache Pulsar community contacted me to host a meetup > > together in Beijing on 4 Jun 2020 in Beijing (using Chinese). > > > > Does someone want to share a talk about IoTDB? (How to use IoTDB, IoTDB's > > design etc..) > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > > -- > — > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 >
Re: [DISCUSS] Enrich information of project committers in website
Hi, Let's keep this thread for discussion... > I agree that this information can show the diversity > directly, and considering people contribute as individuals, I prefer reduce > the maintenance costs. Considering the benefit that the info can show the diversity (and it is beneficial for graduation, right?), I think the overhead is acceptable, and PPMCs need to be responsible for the duty. I think we can try to maintain the info for a period. And, once we find that (1) the cost of maintaining the info is too heavy, and (2) the community is diverse enough, we may consider to remove the info. How about that? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 孙泽嵩 于2019年12月17日周二 上午11:28写道： > Thanks for your kindly help! > > I will try to propose a VOTE, and introduce the method about how to > maintain personal information in the website repository : ) > > > Best, > --- > Zesong Sun > School of Software, Tsinghua University > > 孙泽嵩 > 清华大学 软件学院 > > > 2019年12月16日 23:07，Xiangdong Huang 写道： > > > > detailed info may encourage the committers > >
Re: [VOTE] Enrich information of project committers in IOTDB website
Hi, +1 for the idea. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 孙泽嵩 于2019年12月17日周二 下午3:29写道： > Hi all, > > Thanks to @Jincheng, we intend to enrich information of project committers > in website. (The last VOTE e-mail was actually in a new thread… but somehow > showed together with the DISCUSS thread in some e-mail clients, so I change > the theme a little this time ...) > > I have opened a PR [1] in our website repository, so if this VOTE pass and > the PR is merged, every committer and contributor can open PR themselves to > maintain their own information. Besides, we also add two lists for those > contributors who have submitted PR(s) and propose issue(s) for IoTDB to > encourage more and more people to join us. > > I’d like to briefly introduce how to maintain your information: > > 1. Search your name in 'src/views/Contributor.vue' , and update the > information (including avatar, name, role, organization, apache id, and > starting date). > > 2. If your name hasn't existed in the page, you can just add your > information in the list accordingly: ‘conList' for committers, > ‘conWithPRList' for contributors who have submitted PR(s), and > ‘conWithIssueList' for contributors who have proposed issue(s). > > 3. As for avatar, you can either upload a picture (better to limit the > size <150KB) by adding one in '/assets/img/contributor-avatar', then you > only need to use the file name in the information; Or, you can use a photo > link. (You can see the example in PR description) > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > are required to pass. > > [ ] +1 accept > [ ] -1 reject (explanation required) > > [1] https://github.com/apache/incubator-iotdb-website/pull/50 < > https://github.com/apache/incubator-iotdb-website/pull/50> > > > Best, > --- > Zesong Sun > School of Software, Tsinghua University > > 孙泽嵩 > 清华大学 软件学院 > >
Re: [VOTE] Enrich information of project committers in website
Hi Zesong, Thanks very much. Can you open a new thread entitled "[VOTE] Enrich information of project committers in IoTDB website"? Current thread name is started with [discuss], which may lead to someones omitting the vote. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 孙泽嵩 于2019年12月17日周二 上午11:39写道： > Hi all, > > Thanks to @Jincheng, we intend to enrich information of project committers > in website. > > I have opened a PR [1] in our website repository, so if this VOTE pass and > the PR is merged, every committer and contributor can open PR themselves to > maintain their own information. Besides, we also add two lists for those > contributors who have submitted PR(s) and propose issue(s) for IoTDB to > encourage more and more people to join us. > > I’d like to briefly introduce how to maintain your information: > > 1. Search your name in 'src/views/Contributor.vue' , and update the > information (including avatar, name, role, organization, apache id, and > starting date). > > 2. If your name hasn't existed in the page, you can just add your > information in the list accordingly: ‘conList' for committers, > ‘conWithPRList' for contributors who have submitted PR(s), and > ‘conWithIssueList' for contributors who have proposed issue(s). > > 3. As for avatar, you can either upload a picture (better to limit the > size <150KB) by adding one in '/assets/img/contributor-avatar', then you > only need to use the file name in the information; Or, you can use a photo > link. (You can see the example in PR description) > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > are required to pass. > > [ ] +1 accept > [ ] -1 reject (explanation required) > > [1] https://github.com/apache/incubator-iotdb-website/pull/50 > > > Best, > --- > Zesong Sun > School of Software, Tsinghua University > > 孙泽嵩 > 清华大学 软件学院 > >
Re: [DISCUSS] Enrich information of project committers in website
Hi, Thanks for the suggestion. > So, I proposal that enrich information of project committers as follows I like the idea. More detailed info may encourage the committers (Give the committers more chance to show themselves). > But I don't know why this information was originally added, maybe @Xiangdong know more about this. :) > It can be for a number of reasons, some projects which were started by one company may want to show how diverse they have become and highlight that. Yes, indeed actually we initially wanted to show the diversity of the community. But unfortunately we forgot to maintain the list. For example, some guys in the list have graduated and still contribute to the project even they have worked for Microsoft, Ali and ByteDance etc.. If we can collect the info and keep update, it would be nice to show the diversity. But if we do not maintain that, it is a negative way... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 jincheng sun 于2019年12月16日周一 下午9:40写道： > Hi Justin， > > Thank you for your explanation，It makes more sense to me . > > +1 for remove the Organization information. > > Best， > Jincheng > > > > > Justin Mclean 于2019年12月16日 周一19:55写道： > > > Hi, > > > > > But I don't know why this information was originally added, maybe > > > @Xiangdong know more about this. :) > > > > It can be for a number of reasons, some projects which were started by > one > > company may want to show how diverse they have become and highlight that. > > In some cases some popular projects put IMO too much emphasis on who > their > > committers/(P)PMC member work for. In most cases I think it just someone > > has copied and pasting from another popular project without thinking why > > that is there. > > > > Thanks, > > Justin > > -- > > Best, > Jincheng > > Twitter: https://twitter.com/sunjincheng121 >
[jira] [Created] (IOTDB-371) [TravisCI] Fix maven version on WinOS.
Xiangdong Huang created IOTDB-371: - Summary: [TravisCI] Fix maven version on WinOS. Key: IOTDB-371 URL: https://issues.apache.org/jira/browse/IOTDB-371 Project: Apache IoTDB Issue Type: Bug Reporter: Xiangdong Huang Maven 3.6.2 has removed from [https://www-eu.apache.org/dist/maven/maven-3/3.6.2/binaries/apache-maven-3.6.2-bin.zip] , which will lead to the travis ci failure for WinOS. Modify .travis.yml file and upgrade the download link to 3.6.3 can solve the problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Maintain user roles of IoTDB Jira
Hi, I will fix the inconsistency about the roster. jincheng sun 于2019年12月16日 周一上午9:25写道： > Yes, I see :). Thank you for clarifying who can perform maintenance Justin > ! > > Best, > Jincheng > - > Committer & PMC Member at @ApacheFlink > Staff Engineer at @Alibaba > Blog: https://enjoyment.cool > Twitter: https://twitter.com/sunjincheng121 > -- > > > Justin Mclean 于2019年12月15日周日 上午7:51写道： > > > Hi, > > > > > I found that the committer information(Number of person) is not > > > synchronized between [1] and [2] pages. :) > > > > It up to the :PMC to do that. > > > > Thanks, > > Justin > > > -- --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
[jira] [Created] (IOTDB-368) Special design for time series which has high frequency (need to discuss the user scenario)
Xiangdong Huang created IOTDB-368: - Summary: Special design for time series which has high frequency (need to discuss the user scenario) Key: IOTDB-368 URL: https://issues.apache.org/jira/browse/IOTDB-368 Project: Apache IoTDB Issue Type: New Feature Reporter: Xiangdong Huang Hi, recently I find some users want to store time series with high frequency, e.g., 100KHz. As far as I know, IoTDB can support the above kind of frequency by using batch insertion (with 1 client). However, I think we can do it better: (1) considering better compression (both for the timestamp and the values) (2) In this case, does user really need to read data one point by one point? Running a special query on this kind of data may be helpful. More discussion is needed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-367) Aggregation query performance for the data in memory
Xiangdong Huang created IOTDB-367:
-
Summary: Aggregation query performance for the data in memory
Key: IOTDB-367
URL: https://issues.apache.org/jira/browse/IOTDB-367
Project: Apache IoTDB
Issue Type: Improvement
Reporter: Xiangdong Huang
A user follows and modifies the JDBCExample and then reports a performance
problem:
1. Two series are created.
!https://mail.google.com/mail/u/0?ui=2=dfcbf3c637=0.1=msg-f:1652861281026133792=16f02493ee8f4f20=fimg=s0-l75-ft=ANGjdJ_ohwmWuAixzEuDLdub7ai1AiTLlKZ3afZcP-k3w6jvqNhV6hrB9kwBHY6LPu7VAAeqh_bWicRmpFNBgoLcb_SJE727SNupshW10JxWyP7q7mEVEW6xlspxAkw=emb|width=2098,height=194!
2. the user runs aggregation queries while keeping writing data.
3. The user finds that the aggregation query latency increases along with the
number of data points increase. When the number of points is increased to 20
million, the query latency is about tens of seconds.
4. But, once the data is flushed on disk, the aggregation speed is back to
several milliseconds.
I think it is a design problem because we have no summary info for the data in
memory.
Codes:
{code:java}
// code placeholder
import java.sql.*;
import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.Date;
public class JDBCExample {
/**
* Before executing a SQL statement with a Statement object, you need to
create a Statement object using the createStatement() method of the Connection
object.
* After creating a Statement object, you can use its execute() method to
execute a SQL statement
* Finally, remember to close the 'statement' and 'connection' objects by
using their close() method
* For statements with query results, we can use the getResultSet() method
of the Statement object to get the result set.
*/
public static void main(String[] args) throws SQLException, ParseException {
Connection connection = getConnection();
if (connection == null) {
System.out.println("get connection defeat");
return;
}
int[] days={1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20};
int i=days.length;
while (i-->0){
AddInThread addInThread=new AddInThread(getConnection(),days[i]);
addInThread.start();
}
}
public static Connection getConnection() {
// JDBC driver name and database URL
String driver = "org.apache.iotdb.jdbc.IoTDBDriver";
String url = "jdbc:iotdb://192.168.5.244:6667/";
// Database credentials
String username = "root";
String password = "root";
Connection connection = null;
try {
Class.forName(driver);
connection = DriverManager.getConnection(url, username, password);
} catch (ClassNotFoundException e) {
e.printStackTrace();
} catch (SQLException e) {
e.printStackTrace();
}
return connection;
}
/**
* This is an example of outputting the results in the ResultSet
*/
private static void outputResult(ResultSet resultSet) throws SQLException {
if (resultSet != null) {
System.out.println("--");
final ResultSetMetaData metaData = resultSet.getMetaData();
final int columnCount = metaData.getColumnCount();
for (int i = 0; i < columnCount; i++) {
System.out.print(metaData.getColumnLabel(i + 1) + " ");
}
System.out.println();
while (resultSet.next()) {
for (int i = 1; ; i++) {
System.out.print(resultSet.getString(i));
if (i < columnCount) {
System.out.print(", ");
} else {
System.out.println();
break;
}
}
}
System.out.println("--\n");
}
}
}
class AddInThread extends Thread {
final Connection connection;
final int day;
final String datetimeText;
SimpleDateFormat format = new SimpleDateFormat("-MM-dd HH:mm:ss:SSS");
AddInThread(Connection connection,int days) {
this.connection = connection;
day = days;
datetimeText="2019-11-"+days+" 10:34:59:000";
}
@Override
public void run() {
try {
Date datetime = format.parse(datetimeText);
long times=datetime.getTime();
Statement statement = connection.createStatement();
Integer i = 100;
while (i-- >0) {
statement.execute("insert into
root.ch.baby.d01(timestamp,status) v
[jira] [Created] (IOTDB-366) Concurrent Error when multiple JDBC client send queries
Xiangdong Huang created IOTDB-366:
-
Summary: Concurrent Error when multiple JDBC client send queries
Key: IOTDB-366
URL: https://issues.apache.org/jira/browse/IOTDB-366
Project: Apache IoTDB
Issue Type: Bug
Affects Versions: 0.10.0-SNAPSHOT
Reporter: Xiangdong Huang
HI,
After the SQL parser is upgraded to Antlr4, seems a concurrent error is
introduce.
The error can be reproduced by:
In org.apache.iotdb.db.integration.IoTDBQueryDemoIT class, add a new test
function:
{code:java}
// code placeholder
@Test
public void testConcurrent() {
new Thread(new Runnable() {
@Override
public void run() {
try {
selectTest();
} catch (Exception e) {
e.printStackTrace();
}
}
}).start();
new Thread(new Runnable() {
@Override
public void run() {
try {
selectTest();
} catch (Exception e) {
e.printStackTrace();
}
}
}).start();
}
{code}
Notice, because it is a concurrent error, the issue is not reproduced every
time.
And, the exceptions in the above test function can not be caught by Junit, so
it is not a formal UT code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[Discuss] More reasonable issue permission on JIRA
Hi, Now IoTDB is using _Default Permission Scheme_ on jira [1]. The schema looks good, but one thing that I think we can have a change: Current the "Assignable User" needs to be Administrator/PMC/Committer. However, if someone (who is not a committer) reports a bug and he/she has the ability to fix that and can submit a PR. I think we can assign the issue to him/her. It will give more sense of honor to users who are not the committers but make real contribution to the project. And, it will attract more users to contribute to IoTDB, I think. Some users also point out that [2]. Therefore, I suggest to change "Assignable User" to Administrator/PMC/Committer/Reporter/Contributor.. Even though I have the administrator permission of IoTDB JIRA, but the above modification nees jira-administrator permission, which is higher than what I can do. Maybe @Christofer Dutz can help us. :-D. [1] https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/permissions [2] https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-365 Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: Maintain user roles of IoTDB Jira
By the way, For PPMC and Apache committers, I recommend you use your Apache ID to login JIRA. Then by default, I can grant all users who are on IoTDB roster[1] the committer permission. It will be more maintainable: once someone are voted as a new committer, we can maintain his/her JIRA permission at the same time. [1] https://whimsy.apache.org/roster/ppmc/iotdb Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年12月14日周六 下午1:03写道： > 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 > > 黄向东 > 清华大学 软件学院 >
Maintain user roles of IoTDB Jira
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] [Closed] (IOTDB-363) Fix link error for `Development-Contributing.md` and `Development-Document.md`
[ https://issues.apache.org/jira/browse/IOTDB-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xiangdong Huang closed IOTDB-363. - Fix Version/s: 0.8.2 0.8.1 0.9.0 0.8.0 Resolution: Fixed Many thanks for finding and fixing the issue :D > Fix link error for `Development-Contributing.md` and `Development-Document.md` > -- > > Key: IOTDB-363 > URL: https://issues.apache.org/jira/browse/IOTDB-363 > Project: Apache IoTDB > Issue Type: Bug >Reporter: sunjincheng >Priority: Major > Labels: pull-request-available > Fix For: 0.8.0, 0.9.0, 0.9.1, 0.8.1, 0.8.2 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently, the link [https://iotdb.apache.org/#/Documents] of docs in > [https://iotdb.apache.org/#/Development/Contributing] > is incorrect, I think we should correct it as follows: > 1) [https://iotdb.apache.org/#/Documents] -> > [https://iotdb.apache.org/#/Documents/progress/chap1/sec1] > or > 2) [https://iotdb.apache.org/#/Documents] -> > [https://iotdb.apache.org/#/Documents/0.9.0/chap1/sec1] > I prefer to `[https://iotdb.apache.org/#/Documents/progress/chap1/sec1]` > What do you think? -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [jira] [Created] (IOTDB-363) Fix link error for `Development-Contributing.md` and `Development-Document.md`
Hi, Great to see these issues are found and fixed!! Cheers! --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 jincheng sun 于2019年12月12日周四 下午10:21写道： > Thanks for your quick response Jialin! > > Would be nice if you can add the comments in JIRA [1] or the PR [2] :) > > Best, > jincheng > - > Committer & PMC Member at @ApacheFlink > Staff Engineer at @Alibaba > Blog: https://enjoyment.cool > Twitter: https://twitter.com/sunjincheng121 > -- > > [1] https://issues.apache.org/jira/browse/IOTDB-363 > [2] https://github.com/apache/incubator-iotdb/pull/647 > > > Jialin Qiao 于2019年12月12日周四 下午9:02写道： > > > Hi, > > > > Welcome! +1 for the progress version. > > > > Jialin Qiao > > > > sunjincheng (Jira) 于2019年12月12日周四 下午8:39写道： > > > > > sunjincheng created IOTDB-363: > > > - > > > > > > Summary: Fix link error for `Development-Contributing.md` > > and > > > `Development-Document.md` > > > Key: IOTDB-363 > > > URL: https://issues.apache.org/jira/browse/IOTDB-363 > > > Project: Apache IoTDB > > > Issue Type: Bug > > > Reporter: sunjincheng > > > Fix For: 0.9.1 > > > > > > > > > Currently, the link [https://iotdb.apache.org/#/Documents] of docs in > [ > > > https://iotdb.apache.org/#/Development/Contributing] > > > > > > is incorrect, I think we should correct it as follows: > > > > > > 1) [https://iotdb.apache.org/#/Documents] -> [ > > > https://iotdb.apache.org/#/Documents/progress/chap1/sec1] > > > > > > or > > > > > > 2) [https://iotdb.apache.org/#/Documents] -> [ > > > https://iotdb.apache.org/#/Documents/0.9.0/chap1/sec1] > > > > > > I prefer to `[ > https://iotdb.apache.org/#/Documents/progress/chap1/sec1]` > <https://iotdb.apache.org/#/Documents/progress/chap1/sec1]> > > <https://iotdb.apache.org/#/Documents/progress/chap1/sec1]> > > > <https://iotdb.apache.org/#/Documents/progress/chap1/sec1]> > > > > > > What do you think? > > > > > > > > > > > > -- > > > This message was sent by Atlassian Jira > > > (v8.3.4#803005) > > > > > > > > > -- > > — > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > >
Re: a question about writing TsFile-Page
Hi,
1. For PublicBAOS, it extends the ByteArrayOutputStream, so that it can
grow automatically.
As we do not define the init size, it should be 32.
I think giving a more intelligent init size is good, and it is the best if
the size == the real page size before the page has to be flushed.
Which factors impact the page size:
(1). The max point number ($n$) in a page: the size = the data type size *
$n$.
(2). The max page size $P$.
(3). The memtable size $M$ and the number of active Chunks $c$ in the
memtable: $M$/$c$.
The real scenarios may be more complicated.
If we can not find a intelligent way, at least what we can do is, we can
set the init size as an advanced parameter to let DBA tune.
For more info, please read the funcion ` void
checkPageSizeAndMayOpenANewPage()` in `ChunkWriterImpl`
If you have more questions, do not hesitate to send email.
Best,
--
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
atoiLiu 于2019年12月12日周四 下午6:06写道：
> Hi,
> I understand the process of writing TsFile, but there is a question that
> is not very clear to me. I hope someone can give me some advice.
> TsFile has the concept of Page, which consists of two pieces of data that
> grow on each other,
> 1. timeOut
> 2. ValueOut
> Both are cached by the PublicBAOS class, where I notice it extends
> ByteArrayOutputStream and doesn't initialize the capacity when used.
> private PageWriter(Encoder timeEncoder, Encoder valueEncoder) {
> this.timeOut = new PublicBAOS();
> this.valueOut = new PublicBAOS();
> this.timeEncoder = timeEncoder;
> this.valueEncoder = valueEncoder;
> }
> public PublicBAOS() {
> super();
> }
> public ByteArrayOutputStream() {
> this(32);
> }
> I noticed that we had a page size that was about 64K in the design
> expectation，
> and this will make the cache constantly grow and need to copy the data
> again,
> I think this is a waste, so I want to add an initial value to it, so how
> much is appropriate?
> private void grow(int minCapacity) {
> // overflow-conscious code
> int oldCapacity = buf.length;
> int newCapacity = oldCapacity << 1;
> if (newCapacity - minCapacity < 0)
> newCapacity = minCapacity;
> if (newCapacity - MAX_ARRAY_SIZE > 0)
> newCapacity = hugeCapacity(minCapacity);
> buf = Arrays.copyOf(buf, newCapacity);
> }
> In the implementation of ByteArrayOutputStream, the default is to double
> the extension.
> In the write flow of page, the default is to write first and then check if
> the data is larger than 64K, which may make the data larger than 64K.
> In this case it would be wrong to set 64K, which would waste more
> resources
> and I think the initial value should be less than 64K, because it might be
> OOM when the time series is very large，
> So I don't really know how much to set
>
> I don't know whether I am correct in thinking this way. I am looking
> forward to your reply
> thanks again
Re: Contributor Permission for IOTDB-362
Hi Jincheng, Welcome to contribution! Sorry I tried to assign the issue to you but failed. But do not worry, I will merge your PR after the code review. Best. --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 jincheng sun 于2019年12月12日周四 下午5:11写道： > Hi, > > My name is Jincheng Sun, I am just find a bug of IoTDB webside, more detail > can be found in [1], I'd like to contribute some minor improvements to the > IotDB, My JIRA user name is 'sunjincheng121'. > > Best, > Jincheng > > [1] https://issues.apache.org/jira/browse/IOTDB-362 >
Re: About the iotdb website
Hi, +1. @atoiLiu, are you good at building a website, and interested in that? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年12月12日周四 下午4:16写道： > Hi, > > +1 for updating the website. > > Thanks, > Jialin Qiao > > atoiLiu 于2019年12月12日周四 下午3:41写道： > > > Hi, > > I do n’t know if you invited friends to open the official website of > > iotdb, did they encounter any problems? > > 1. The official website style is very old and feels like a framework > > website opened a few years ago > > 2. The website opens slowly, and the carousel pictures sometimes cannot > be > > displayed correctly. > > 3. No internationalization, making reading relatively difficult > > > > I think the site may need to be updated to attract new customers > > > > Here are some really cool and fast websites： > > [1] http://servicecomb.apache.org/cn/ <http://servicecomb.apache.org/cn/ > > > > [2] https://pingcap.com/ <https://pingcap.com/> > > [3] http://dubbo.apache.org/zh-cn/ <http://dubbo.apache.org/zh-cn/> > > > > -- > — > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 >
Re: question about Apache Jenkins and Sonar
Hi, The analysis repo on SounarCloud has been created [1]. I read the guide [2] and the example of PLC4x [3] and Sling projects. I noticed that all of them mentioned "sonar_token", e.g., " withCredentials([string(credentialsId: 'chris-sonarcloud-token', variable: ' SONAR_TOKEN')]". I have created a token called xiangdong-iotdb-sonarcloud-token, but my question is, don't I need to put the value of the token into the configuration file? If I publish the token value, is that suitable? (According to my understanding, the token should be protected as a privacy). (I am trying how to config can work. But if someone can give a guide, it will be very helpful :-D ). [1] https://sonarcloud.io/dashboard?id=apache_incubator-iotdb [2] https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis [3] https://github.com/apache/plc4x/blob/develop/Jenkinsfile#L124 Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年12月1日周日 下午1:57写道： > Hi, > > thanks Chris and Willem. > I have created a jira ticket for applying creating a project on > sonarcloud.io [1]. > Before the application is complete, I disable the sonar analysis from > jenkins temporary. > > [1] https://issues.apache.org/jira/browse/INFRA-19507 > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Willem Jiang 于2019年12月1日周日 上午9:39写道： > >> You need to some setup[1] to enable the Sonar Cloud Service for Apache >> project. >> >> [1]https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Sat, Nov 30, 2019 at 10:31 PM Christofer Dutz >> wrote: >> > >> > Hi Xiangdong, >> > >> > The ASF SonarCube instance is no longer being run. >> > The build has to be changed to SounarCloud. >> > >> > Have a look at the PLC4X build (Jenkinsfile). >> > We did the change there some time ago. >> > >> > Chris >> > >> > Am 29.11.19, 17:24 schrieb "Xiangdong Huang" : >> > >> > Hi, >> > >> > I find Apache Jenkins build failed because "SonarQube installation >> defined >> > in this job (ASF Sonar Analysis) does not match any configured >> > installation. Number of installations that can be configured: 0." >> > >> > I checked recent commits, and find the most possible code >> modification is >> > that `vulnerability-checks` is moved to `apache-release` profile. >> > >> > So, is this task who triggers Jenkins to submit a job to SonarQube? >> > >> > If so, you'd better revoke your modification on the pom file, >> @jialin Qiao. >> > >> > Best, >> > -- >> > Xiangdong Huang >> > School of Software, Tsinghua University >> > >> > 黄向东 >> > 清华大学 软件学院 >> > >> > >> >
Re: [Discuss] about collecting info to know who are using IoTDB
Hi, I thought it is common... e.g., Hadoop and Spark also have the similar pages [1] and [2]. [1] https://cwiki.apache.org/confluence/display/HADOOP2/PoweredBy [2] https://spark.apache.org/powered-by.html Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Willem Jiang 于2019年12月12日周四 上午8:54写道： > I guess they just want to tell the new coming user, lots of companies > are build production system on top of this project. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Dec 12, 2019 at 5:26 AM Justin Mclean > wrote: > > > > Hi, > > > > > I notice that ShardingSpehere incubating project has a page for > collecting > > > who are using IoTDB[1]. They use github issue to collect the data [2]. > > > > I not sure this is that useful, people contribute to ASF projects as > individuals not companies. While it nice to know your project is being used > I don’t think there’s a lot of value in displaying that list. The ASF is > also vender neutral, why do some companies listed there have logos and some > do not? > > > > Thanks, > > Justin >
[Discuss] about collecting info to know who are using IoTDB
Hi, I notice that ShardingSpehere incubating project has a page for collecting who are using IoTDB[1]. They use github issue to collect the data [2]. I think it is helpful for the project graduation So, if IoTDB also collects the info, how to do that? Any ideas? 1. We do not open the issue module on Github. 2. For Chinese users, many of them do not have a Apache JIRA account and opening the jira may requires some skills in China because of Chinese network problem. So, how about opening a tickets on jira for collecting users out of China, and opening a online document, e.g., QQ document, to collect users in China (But it is hard to record that who maintains the document. (Everyone can modify the document, while on JIRA and github, the contents is binding with accounts)). [1] https://shardingsphere.apache.org/community/en/poweredby/ [2] https://github.com/sharding-sphere/sharding-sphere/issues/234 Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: [jira] [Created] (IOTDB-358) Questions about the `group by` down-samplying clause
Hi, > The answer is NO. If it calculated twice, it's a bug. So, it is a typo of the document, the correct version should be [0, 1d), [1d, 2d). > The new group by statement is like this: select count(*) from root where > time >= 1 and time <= 100 group by ([0, 100], 20ms, 20ms) > The 0 in [0, 100] is used as the start point. This statement should satisfy > most scenarios. Ah... so you give up the ability that letting users define the start point? Besides, I feel confusing about: `time >= 1 and time <= 100 group by ([0, 100]`, if `1` is for the time filter, and `0` is for the start time point, so why we have two `100`? What it is mean about `time >= 1 and time <= 99 group by ([0, 100]`, or `time >= 1 and time <= 100 group by ([0, 99]` ? Best, ------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年12月10日周二 下午6:55写道： > Hi, > > > My question is, is the data point at 1d calculated twice? > > The answer is NO. If it calculated twice, it's a bug. > > > it loses the ability to define the start point of the timestamp for > splitting the time window. > > The new group by statement is like this: select count(*) from root where > time >= 1 and time <= 100 group by ([0, 100], 20ms, 20ms) > The 0 in [0, 100] is used as the start point. This statement should satisfy > most scenarios. > > Thanks, > Jialin Qiao > > xiangdong Huang (Jira) 于2019年12月10日周二 下午4:50写道： > > > xiangdong Huang created IOTDB-358: > > - > > > > Summary: Questions about the `group by` down-samplying > clause > > Key: IOTDB-358 > > URL: https://issues.apache.org/jira/browse/IOTDB-358 > > Project: Apache IoTDB > > Issue Type: Bug > > Affects Versions: 0.9.0 > > Reporter: xiangdong Huang > > > > > > When reading issue #331, I read the `group by` document again and find > > some confusing contents: > > > > V0.9: > > > > [http://iotdb.apache.org/#/Documents/0.9.0/chap5/sec2] > > # (minor), typo, Fig 5.2 rather than Fig 3.2 > > # The first parameter of the GROUP BY statement above is the time > > interval for dividing the time axis. Taking this parameter (1d) as time > > interval and the default origin as the dividing origin, the time axis is > > divided into several continuous intervals, which are [0,1d], [1d, 2d], > [2d, > > 3d], etc. > > > > My question is, is the data point at 1d calculated twice? > > > > > > > > V0.10: > > [http://iotdb.apache.org/#/Documents/progress/chap5/sec2] > > > > the syntax is quite different with v0.9.0. I originally thought it was an > > improvement comparing with 0.9, but when I read the document, I find it > > loses the ability to define the start point of the timestamp for > splitting > > the time window. > > > > Can someone tell me why to design like this? > > > > > > > > > > > > > > > > -- > > This message was sent by Atlassian Jira > > (v8.3.4#803005) > > > > > -- > — > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 >
Re: [jira] [Created] (IOTDB-359) [0.9.0] TsFile Sketch Tool prints wrong results when the tsfile is very large
Hi, Does this bug only affects the sketch-print-tool, or the TsFile actually? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Lei Rui (Jira) 于2019年12月10日周二 下午5:53写道： > Lei Rui created IOTDB-359: > - > > Summary: [0.9.0] TsFile Sketch Tool prints wrong results when > the tsfile is very large > Key: IOTDB-359 > URL: https://issues.apache.org/jira/browse/IOTDB-359 > Project: Apache IoTDB > Issue Type: Bug > Reporter: Lei Rui > > > I used the TsFile sketch tool on a TsFile sized 2.2G, and the printed > result is wrong for that the ChunkGroupMetaDatas are not printed in their > address ascending order. > > I analyzed this bug and find that `int` is used when comparing the address > of ChunkGroupMetaDatas. However, the address should be long data type. > > I'll fix this bug soon :) > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
Re: [jira] [Created] (IOTDB-357) NullPointerException in ActiveTimeSeriesCounter
Hi, which version? 0.9.0?
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Jialin Qiao (Jira) 于2019年12月10日周二 上午11:41写道：
> Jialin Qiao created IOTDB-357:
> -
>
> Summary: NullPointerException in ActiveTimeSeriesCounter
> Key: IOTDB-357
> URL: https://issues.apache.org/jira/browse/IOTDB-357
> Project: Apache IoTDB
> Issue Type: Bug
> Reporter: Jialin Qiao
>
>
> Start a empty IoTDB, execute 3 sql:
> {code:java}
> SET STORAGE GROUP TO root.turbine;
> CREATE TIMESERIES root.turbine.d2.s0 WITH DATATYPE=DOUBLE,
> ENCODING=GORILLA;
> insert into root.turbine.d2(timestamp,s0) values(2,25.3);{code}
> Kill the server and restart, then you will see:
> {code:java}
> 11:37:45.157 [pool-1-IoTDB-Recovery-Thread-Pool-thread-1] ERROR
> org.apache.iotdb.db.conf.adapter.ActiveTimeSeriesCounter - Storage group
> root.turbine- registers active time series root.turbine.d2.s0
> failed11:37:45.157 [pool-1-IoTDB-Recovery-Thread-Pool-thread-1] ERROR
> org.apache.iotdb.db.conf.adapter.ActiveTimeSeriesCounter - Storage group
> root.turbine- registers active time series root.turbine.d2.s0
> failedjava.lang.NullPointerException: null at
> org.apache.iotdb.db.conf.adapter.ActiveTimeSeriesCounter.offer(ActiveTimeSeriesCounter.java:65)
> at
> org.apache.iotdb.db.engine.flush.MemTableFlushTask.syncFlushMemTable(MemTableFlushTask.java:87)
> at
> org.apache.iotdb.db.writelog.recover.TsFileRecoverPerformer.redoLogs(TsFileRecoverPerformer.java:213)
> at
> org.apache.iotdb.db.writelog.recover.TsFileRecoverPerformer.recover(TsFileRecoverPerformer.java:143)
> at
> org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.recoverSeqFiles(StorageGroupProcessor.java:294)
> at
> org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.recover(StorageGroupProcessor.java:223)
> at
> org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.(StorageGroupProcessor.java:210)
> at
> org.apache.iotdb.db.engine.StorageEngine.lambda$new$0(StorageEngine.java:119)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)11:37:45.158
> [pool-1-IoTDB-Recovery-Thread-Pool-thread-1] ERROR
> org.apache.iotdb.db.conf.adapter.ActiveTimeSeriesCounter - Update
> root.turbine- active ratio failedjava.lang.NullPointerException: null at
> org.apache.iotdb.db.conf.adapter.ActiveTimeSeriesCounter.updateActiveRatio(ActiveTimeSeriesCounter.java:79)
> at
> org.apache.iotdb.db.engine.flush.MemTableFlushTask.syncFlushMemTable(MemTableFlushTask.java:91)
> at
> org.apache.iotdb.db.writelog.recover.TsFileRecoverPerformer.redoLogs(TsFileRecoverPerformer.java:213)
> at
> org.apache.iotdb.db.writelog.recover.TsFileRecoverPerformer.recover(TsFileRecoverPerformer.java:143)
> at
> org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.recoverSeqFiles(StorageGroupProcessor.java:294)
> at
> org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.recover(StorageGroupProcessor.java:223)
> at
> org.apache.iotdb.db.engine.storagegroup.StorageGroupProcessor.(StorageGroupProcessor.java:210)
> at
> org.apache.iotdb.db.engine.StorageEngine.lambda$new$0(StorageEngine.java:119)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>
Re: Docker image uploaded under the account of apache
Hi all, Um I was trying to contact the owners of these docker repos. Sadly, only hxdiotdb (it is me..) and xingtanzjr are contacted. I also checked these repos. [1], [2] and [3] are fine, both of them mentioned the image is for Apache IoTDB, and showed iotdb's website. I can not contact to [4] and [5] (DockerHub does not share owners' info, even the email). [4] is indeed an Apache IoTDB image, but sounds [5] is not an Apache IoTDB image. [1] https://hub.docker.com/r/hxdiotdb/iotdb < https://hub.docker.com/r/hxdiotdb/iotdb> [2] https://hub.docker.com/r/dmonesr/iotdb < https://hub.docker.com/r/dmonesr/iotdb> [3] https://hub.docker.com/r/xingtanzjr/iotdb <https://hub.docker.com/r/xingtanzjr/iotdb> < https://hub.docker.com/r/xingtanzjr/iotdb> [4] https://hub.docker.com/r/fudanyuan/iotdb < https://hub.docker.com/r/fudanyuan/iotdb> [5] https://hub.docker.com/r/zongxiongchen/iotdb-core < https://hub.docker.com/r/zongxiongchen/iotdb-core> Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年12月9日周一 下午10:04写道： > Hi, > > > Nor do they need to, often a friendly email will achieve a good result > or an outcome that works for everyone. If a solution can’t be found then > brand can deal with it. > > If contacting with the owner, do we need to CC to the private@ mailing > list or this mailing list? > > Best, > -- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Kevin A. McGrail 于2019年12月9日周一 下午9:35写道： > >> What defines a major branding issue? Are they to police the internet? >> How are they to defermine they are major or not? These are very vague >> instructions to a podling about what to do. >> >> On 12/9/2019 2:58 AM, Justin Mclean wrote: >> > Hi, >> > >> >> I understand that request but that isn't a graduation issue if someone >> >> doesn't listen to them. >> > But they do need to contact them and look out for issues like this, I >> didn’t say that there needs to be no branding issues at graduation=, just >> that the podling is aware of any major ones and be dealing with them. >> > >> > Thanks, >> > Justin >> >> -- >> Kevin A. McGrail >> kmcgr...@apache.org >> >> Member, Apache Software Foundation >> Chair Emeritus Apache SpamAssassin Project >> https://www.linkedin.com/in/kmcgrail - 703.798.0171 >> >>
Re: [jira] [Created] (IOTDB-346) StorageGroupProcessor.sequenceFileList is ordered by fileName rather than dataTime
Hi,
I think it is a bug in the `load` function now, and needs to be fixed
quickly.
Firstly, let's consider that there is no `load` function.
In this case, the files will have the same order no matter you use which
device's timeline as the ordering dimension.
(Second, in your case, can we put the tsfile 105 into the sequence files?
Condition: all devices in a flushing memetable can be set in a time hole of
the sequence files.)
Third, lets's consider that if the `load` function is enable.
The worest case is that you add a file which has two devices (device 1 and
device2), and if you use device1's timeline to order files, it is between
F2 and F3, while it is between F1 and F2 if you use device2's timeline.
device1: F1 F2 _HOLE__ F3
device2: F1 __HOLE__ F2 F3
Then, why not split the file into two files?
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Jialin Qiao 于2019年12月10日周二 下午7:05写道：
> Hi,
>
> Things become complicated when the load file feature is introduced in
> IoTDB. The newly added data file may contain many devices with different
> time intervals. Therefore, one order of TsFileResources is insufficient.
> A possible solution is to sort the TsFileResources temporarily when
> querying.
>
> Thanks,
> Jialin Qiao
>
> Lei Rui (Jira) 于2019年12月9日周一 上午12:14写道：
>
> > Lei Rui created IOTDB-346:
> > -
> >
> > Summary: StorageGroupProcessor.sequenceFileList is ordered
> by
> > fileName rather than dataTime
> > Key: IOTDB-346
> > URL: https://issues.apache.org/jira/browse/IOTDB-346
> > Project: Apache IoTDB
> > Issue Type: Bug
> > Reporter: Lei Rui
> >
> >
> > `StorageGroupProcessor.sequenceFileList` is ordered by fileName rather
> > than by time of data, as reflected in the
> > `StorageGroupProcessor.getAllFiles` method code:
> > {code:java}
> > tsFiles.sort(this::compareFileName);
> > {code}
> >
> > I use the following examples to expose the bug when the order of fileName
> > is inconsistent with that of dataTime.
> >
> > First, for preparation, I created three tsfiles using the following sql:
> > {code:java}
> > SET STORAGE GROUP TO root.ln.wf01.wt01
> > CREATE TIMESERIES root.ln.wf01.wt01.status WITH DATATYPE=BOOLEAN,
> > ENCODING=PLAIN
> > CREATE TIMESERIES root.ln.wf01.wt01.temperature WITH DATATYPE=DOUBLE,
> > ENCODING=PLAIN
> > CREATE TIMESERIES root.ln.wf01.wt01.hardware WITH DATATYPE=INT32,
> > ENCODING=PLAIN
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(1, 1.1, false, 11)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(2, 2.2, true, 22)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(3, 3.3, false, 33)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(4, 4.4, false, 44)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(5, 5.5, false, 55)
> > flush
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(100, 100.1, false, 110)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(150, 200.2, true, 220)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(200, 300.3, false, 330)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(250, 400.4, false, 440)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(300, 500.5, false, 550)
> > flush
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(10, 10.1, false, 110)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(20, 20.2, true, 220)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(30, 30.3, false, 330)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(40, 40.4, false, 440)
> > INSERT INTO root.ln.wf01.wt01(timestamp,temperature,status, hardware)
> > values(50, 50.5, false, 550)
> > flush
> > {code}
> > The tsfiles created are organized in the following directory structure:
> > {code:java}
> > |data
> > |--sequence
> > |root.ln.wf01.wt01
> > |--1575813520203-101-0.tsfile
> > |--1575813520203-101-0.tsfile.resource
> > |--1575813520669-103-0.tsfile
> > |--1575813520669-103-0.tsfile.resource
&g
Considering the first Meetup of IoTDB in Beijing
Hi all, Some guys from Apache Pulsar community contacted me to host a meetup together in Beijing on 4 Jun 2020 in Beijing (using Chinese). Does someone want to share a talk about IoTDB? (How to use IoTDB, IoTDB's design etc..) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
[jira] [Created] (IOTDB-358) Questions about the `group by` down-samplying clause
xiangdong Huang created IOTDB-358: - Summary: Questions about the `group by` down-samplying clause Key: IOTDB-358 URL: https://issues.apache.org/jira/browse/IOTDB-358 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.9.0 Reporter: xiangdong Huang When reading issue #331, I read the `group by` document again and find some confusing contents: V0.9: [http://iotdb.apache.org/#/Documents/0.9.0/chap5/sec2] # (minor), typo, Fig 5.2 rather than Fig 3.2 # The first parameter of the GROUP BY statement above is the time interval for dividing the time axis. Taking this parameter (1d) as time interval and the default origin as the dividing origin, the time axis is divided into several continuous intervals, which are [0,1d], [1d, 2d], [2d, 3d], etc. My question is, is the data point at 1d calculated twice? V0.10: [http://iotdb.apache.org/#/Documents/progress/chap5/sec2] the syntax is quite different with v0.9.0. I originally thought it was an improvement comparing with 0.9, but when I read the document, I find it loses the ability to define the start point of the timestamp for splitting the time window. Can someone tell me why to design like this? -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [jira] [Created] (IOTDB-335) Separate query execution of the same timeseries with different aggregate functions
+1 for the idea. --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年12月5日周四 下午6:42写道： > Hi, > > This is a good optimization :) > > Thanks, > Jialin Qiao > > Lei Rui (Jira) 于2019年12月3日周二 下午2:20写道： > > > Lei Rui created IOTDB-335: > > - > > > > Summary: Separate query execution of the same timeseries > with > > different aggregate functions > > Key: IOTDB-335 > > URL: https://issues.apache.org/jira/browse/IOTDB-335 > > Project: Apache IoTDB > > Issue Type: Improvement > > Reporter: Lei Rui > > > > > > For example, > > > > select avg(s1),sum(s1) from root.sg.d0 > > > > select first_value(s1),first_time(s1) from root.sg.d0 > > > > select count(s1), sum(s1) from root.sg.d0 group by ([1,100],2ms) > > > > > > > > Probably the results of the same timeseries with different aggregate > > functions can be achieved in one query execution process. > > > > > > > > -- > > This message was sent by Atlassian Jira > > (v8.3.4#803005) > > > > > -- > — > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 >
Re: Add data to TSExecuteStatementResp
Hi, I think the idea is ok. And I quick review the codes, sounds no problem. Does anyone who is more familiar with the query process can review the codes? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 atoiLiu 于2019年12月9日周一 下午5:49写道： > Currently, when executing an SQL statement through JDBC, it is done in two > steps: > > 1. Query metadata set hasResultSet = true > > 2. When the client determines that hasResultSet = true, it will initiate > the next data query and call the fetchResult method of the server > > I think this step can be optimized to reduce one request to the server, > especially if the data is empty or the total amount of data is less than > the fetchSize > > So I added the TSQueryDataSet to TSExecuteStatementResp so that the client > could traverse the data directly. > > > > I hope my idea can contribute to the community. Can anyone review it for > me? > > Pr: > https://github.com/apache/incubator-iotdb/pull/631 < > https://github.com/apache/incubator-iotdb/pull/631> > > > In addition, I found a new problem. > When I input a random random SQL in client, the server would throw an > antlr error, which could not be caught by the expected SQLParserException > and was kindly prompted to the user. > I think adding try...catch to the parseSQLToPhysicalPlan should solve > this problem. I don’t know if i am right ,so sorry.
Re: Docker image uploaded under the account of apache
Hi, > Nor do they need to, often a friendly email will achieve a good result or an outcome that works for everyone. If a solution can’t be found then brand can deal with it. If contacting with the owner, do we need to CC to the private@ mailing list or this mailing list? Best, -- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Kevin A. McGrail 于2019年12月9日周一 下午9:35写道： > What defines a major branding issue? Are they to police the internet? > How are they to defermine they are major or not? These are very vague > instructions to a podling about what to do. > > On 12/9/2019 2:58 AM, Justin Mclean wrote: > > Hi, > > > >> I understand that request but that isn't a graduation issue if someone > >> doesn't listen to them. > > But they do need to contact them and look out for issues like this, I > didn’t say that there needs to be no branding issues at graduation=, just > that the podling is aware of any major ones and be dealing with them. > > > > Thanks, > > Justin > > -- > Kevin A. McGrail > kmcgr...@apache.org > > Member, Apache Software Foundation > Chair Emeritus Apache SpamAssassin Project > https://www.linkedin.com/in/kmcgrail - 703.798.0171 > >
Re: Docker image uploaded under the account of apache
Hi, > but they do need to recognise that they are Apache projects > If the project didn't set them up > and they are doing branding correctly, the issue should be handed off to > brand to followup. For example, in my previous Repo [1], I wrote a short description " Apache IoTDB (incubating) docker images", is that ok for a personal maintained Repo? Or do they have to declaim the incubator disclaimer? And in [1], I built an image for iotdb 0.8.2 snapshot, if some personal repo have the similar case, do they need to remove RC and snapshot images? [1] https://hub.docker.com/repository/docker/hxdiotdb/iotdb Best, ------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Kevin A. McGrail 于2019年12月9日周一 上午9:34写道： > I disagree this is a graduation issue. If the project didn't set them up > and they are doing branding correctly, the issue should be handed off to > brand to followup. > > On Sun, Dec 8, 2019, 20:19 Justin Mclean wrote: > > > Hi, > > > > > Do we need to contact others to delete the repo? (I think these users > > have > > > the right to use apache iotdb and build a repo called iotdb) > > > > They don’t need to delete them, but they do need to recognise that they > > are Apache projects and follow our branding/trademarks. This is not an > > urgent issue, just something in general that needs to be sorted out > before > > you graduate. > > > > Thanks, > > Justin >
Re: Docker image uploaded under the account of apache
Hi, I can only recognize two of them... xingtanzjr and hxdiotdb... one is my private repo and the other belongs to Jinrui Zhang, we can remove these repo because they are not useful now. Do we need to contact others to delete the repo? (I think these users have the right to use apache iotdb and build a repo called iotdb) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年12月9日周一 上午5:08写道： > Hi, > > https://hub.docker.com/r/apache/iotdb < > https://hub.docker.com/r/apache/iotdb> looks good to me. > > We may have some branding/trademark issues with: > https://hub.docker.com/r/xingtanzjr/iotdb < > https://hub.docker.com/r/xingtanzjr/iotdb> > https://hub.docker.com/r/fudanyuan/iotdb < > https://hub.docker.com/r/fudanyuan/iotdb> > https://hub.docker.com/r/hxdiotdb/iotdb < > https://hub.docker.com/r/hxdiotdb/iotdb> > https://hub.docker.com/r/dmonesr/iotdb < > https://hub.docker.com/r/dmonesr/iotdb> > https://hub.docker.com/r/zongxiongchen/iotdb-core < > https://hub.docker.com/r/zongxiongchen/iotdb-core> > > Thanks, > Justin > >
[jira] [Created] (IOTDB-345) upgrade thrift from 0.12 to 0.13
xiangdong Huang created IOTDB-345: - Summary: upgrade thrift from 0.12 to 0.13 Key: IOTDB-345 URL: https://issues.apache.org/jira/browse/IOTDB-345 Project: Apache IoTDB Issue Type: Bug Reporter: xiangdong Huang It seems thrift 0.12 has a bug that when a connection is clsoed, an exception is printed on the server side. And, if you install thrift dependency using `pip`, you can not find the 0.12 version. Only 0.13.0 exists. So, it is good to upgrade it to 0.13 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[Result] Apache IoTDB (incubating) 0.8.2 Release
The vote for release Apache IoTDB (Incubating) 0.8.2 has passed with 4 +1 PPMC/IPMC binding votes and 1 +1 non-PPMC votes. PPMC +1 Vote from: Jialin Qiao, Dongfang Mao, Tianan Li, Jistin Mclean and non-PPMC +1 Vote from: Haonan Hou The vote thread: https://lists.apache.org/thread.html/dadba801d3e72b97d997d17470bcf98bdfd217cde14434c8db847ca4%40%3Cdev.iotdb.apache.org%3E Many thanks to all who voted or provided comments! Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Docker image uploaded under the account of apache
Hi all, Apache has an account on dockerHub, and there are many apache software images on it. I opened a ticket to get the permission to upload IoTDB image there several days ago [1]. Now I have get the permission and have uploaded the docker image of IoTDB 0.8.1 and 0.9.0 there. Please have a review to point out the mistake (according to [2]). Now, you can run IoTDB server as a docker container by using "docker run -d -p 6667:6667 -p 31999:31999 -p 8181:8181 --name some-iotdb apache/iotdb:0.9.0" and then start a client-cli by using `docker exec -it some-iotdb /bin/bash` Enjoy it! [1] https://issues.apache.org/jira/browse/INFRA-19459 [2] https://cwiki.apache.org/confluence/display/INCUBATOR/DistributionGuidelines Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: Pypi distribution for IoTDB Python Client API
Hi all, I have uploaded the python package to PyPy formal repo. Now you can install the python package of IoTDB by : pip3 install apache-iotdb:0.9.0 For more details, see [1]: [1] https://pypi.org/project/apache-iotdb/ Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年12月5日周四 上午10:25写道： > Hi, > > Looks good to me. > > Thanks, > Justin >
Re: About add trace or explain
Hi, It is a useful function. Actually for each query, now there is a queryId attached, and it can play as the traceid, I think. The left thing is recording each step's time cost. But if someone implement it, please be careful about the performance side effect. Like Cassandra, there is a command called `tracing on | off`. If the tracing is enable, then a (distributed) write command will be split into about 5 steps and the query command will be split into about 8 steps (I forget the details), but it absolutely harmful for the performance and brings heavily replica inconsistency (because Cassandra will persist the tracing results). So, `tracing on` is disable by default and usually it is just enabled for a short time. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 iotdb_contributor 于2019年12月7日周六 上午2:04写道： > > > hi, > At present, iotdb has a very good design for monitoring the execution > status and time of SQL and it can be displayed to users intuitively. > However, when the user or we do the testing ourselves, we can't > intuitively feedback the direction we need to optimize. > Do we need to design a traceid, which is generated from the method that > reaches serviceimpl, and records the execution time of all important > methods in detail, so that the problem At a glance. > > > 各位好： > > 现在iotdb已经有一个非常好的监视模块，可以打印sql时间和状态等，但仅仅知道一个sql比较慢的时候还不能更快速的定位到慢在哪里，所以我们有没有必要实现一个traceid这类东西，从Tsserviceimp的入口方法开始追踪，包罗所有重要的函数，这样有利于我们直观的优化或分析数据库，或许对未来的集群版本提供更大的帮助！ > 以上只是猜想，烦请各位批评指正！
Re: [jira] [Created] (IOTDB-343) Test method in session to help user to analyze time cost
Hi,
It sounds strange and unusual, but in some case it is useful... Considering
the following POC codes:
```
long begin = System.currentTime();
while () {
String json = getDataFromPLC();
double[] data = parseJson();
iotdbClient.insert(data);
}
long timeCost = System.currentTime() - begin;
```
After a user runs the codes, he may complains: "Why IoTDB has such a poor
performance??? Don't you say that IoTDB have an outstanding performance???
r u kidding me?"
Is that really IoTDB's performance problem? Maybe or not.
If the user asks us for help, we can simply modify the codes like:
```
long total = 0;
while() {
String json = getDataFromPLC();
double[] data = parseJson();
long begin = System.currentTime();
iotdbClient.insert(data);
total += System.currentTime() - begin;
}
```
In this way, we just count the time cost of IoTDB, and omit the time cost
that locally data process.
First, it needs change source codes a lot. Normal users may do not want to
modify their codes so many.
Second, if you show the result to users, "The original time cost is 400s,
but IoTDB just uses 10s", they may be not satisfied, because it looks like
passing the buck. If you want to tell them that "it is your local process
that runs slow", you'd better show that directly: "The original time cost
is 400s, and your local cost is 390s." It gives users a better feeling.
(Negotiaton skills).
Notice that IoTDB is an open source software and users may do not ask our
help. So, the easier way to modify the code to get the result is:
```
long begin = System.currentTime();
while () {
String json = getDataFromPLC();
double[] data = parseJson();
// iotdbClient.insert(data);
}
long timeCost = System.currentTime() - begin;
```
However, if so, we can not guarantee that whether the modern compiler
optimize the codes and skip `parseJson()` function. So the result may
mislead us.
Therefore, if we have a testInsert() method, which just sends request to
IoTDB, and IoTDB returns directly. You can just tell users: if you want to
judge the performance problem, just replace `insert()` with `testInsert()`,
then you will know using your client hardware and the network environment,
what the performance limit is.
```
long begin = System.currentTime();
while () {
String json = getDataFromPLC();
double[] data = parseJson();
iotdbClient.testinsert(data);
}
long timeCost = System.currentTime() - begin;
```
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Jialin Qiao 于2019年12月5日周四 下午6:41写道：
> Hi,
>
> I wonder is it necessary to open a testMethod in our client API…
> It only passes the parameters but does nothing in the server side.
>
> Thanks,
> Jialin Qiao
>
> 南京大学软件学院薛恺丰 <827011...@qq.com> 于2019年12月5日周四 上午10:22写道：
>
> > Hi~
> > I'm working on this issue. Pleases feel free to discuss with me.
> >
> >
> >
> >
> > --原始邮件--
> > 发件人:"Yuan Tian (Jira)" > 发送时间:2019年12月5日(星期四) 上午10:20
> > 收件人:"dev" >
> > 主题:[jira] [Created] (IOTDB-343) Test method in session to help user
> > to analyze time cost
> >
> >
> >
> > Kaifeng Xue created IOTDB-343:
> > -
> >
> >
> > Summary: Test method in session to help user to analyze time cost
> >
>
> > Key: IOTDB-343
> >
>
> > URL: https://issues.apache.org/jira/browse/IOTDB-343
> >
> > <
> https://issues.apache.org/jira/browse/IOTDB-343
> >;
> > Project: Apache IoTDB
> > Issue Type: New
> > Feature
> >
> > Reporter: Kaifeng Xue
> >
> >
> > In our users' scenery, them often preprocess raw data into insert request
> > and then insert to IOTDB. We should support them to analyze the
> > preprocessing time and our database's executing time. So we should add
> test
> > method in session. In these test method, server just return success
> without
> > handling requests.
> >
> >
> >
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.4#803005)
>
>
>
> --
> —
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
Re: About the link address in the .md document
Hi, It is a problem now.. I tried and it is not a correct url now. Add the iotdb.apache.org as the prefix can solve the problem. But, if you add the iotdb.apache.org prefix, then you will jump out of Github when you click the link. (Anyway, it is better than 404 error) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 刘大伟 <13965...@qq.com> 于2019年12月5日周四 下午12:10写道： > Hi, > > I am used to reading* .md *documents directly from github's web page, but > I found that many of the links can not jump directly to the corresponding > address. > > The problem arises because the address used in the document is > (/#/Documents/progress/…) > , is it necessary to add https://iotdb.apache.org ? > > Here's an example: > > > https://github.com/apache/incubator-iotdb/blob/master/docs/Documentation/UserGuide/5-Operation%20Manual/2-DML%20(Data%20Manipulation%20Language).md >
Publish some performance benchmarking result on the website
Hi all,
As IoTDB (0.9) has a outstanding performance (strictly speaking, in some
scenarios), I'd like to add a new webPage on the iotdb website to show the
performance, and describe how to reproduce the performance result.
e.g., iotdb.apache.org/Performance/#{version}
As I am using IoTDB-benchmark, therefore, the added new webPage may need to
add a link to [1], and in the repo [1], we need to share the benchmark
workload configurations to let users reproduce the result.
I'd like to invite Qingxin Feng to provide benchmark results. And, welcome
contributors who are familiar with the VUE web development.
[1] https://github.com/thulab/iotdb-benchmark
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Re: Pypi distribution for IoTDB Python Client API
Hi all, If no more objections in the following 2 days, I will upload the python library to formal PyPi repo. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年12月4日周三 上午12:00写道： > Hi, > > I write a setup.py to distribute IoTDB's Python library to PyPi. > > Now I just upload it to Test PyPi [1], please have a review to point out > which is needed to modify (according to the guide [2]). > > If no more issues, I will submit a PR for the setup.py file and upload the > binary python files to PyPi formally. > > Notice: if you want to try the python client example by using [3], you > need to modify Line 26 and 31 from `from rpc.` to `from iotdb.rpc` > > [1] https://test.pypi.org/project/apache-iotdb/ > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/DistributionGuidelines > [3] > https://github.com/apache/incubator-iotdb/blob/release%2F0.9.0/client-py/src/client_example.py > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 >
discuss the design and codes for the distributed version
Hi, I notice Tian Jiang is working on `cluster_new` branch and the branch keeps updating frequently. Distributed version is not an easy work and is likely not a single guy can finish well. I'd like to begin to read the codes to understand Tian Jiang's idea. I find a very old issue [1] which is for the distributed version. So, let's discuss about the design and current codes in that issue. @江天 And welcome other contributors to joining. [1] https://issues.apache.org/jira/browse/IOTDB-68 <https://issues.apache.org/jira/browse/IOTDB-68?jql=project%20%3D%20IOTDB%20AND%20text%20~%20distribution> Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: 中文文档中第五章第一节有错误
Hi，
I think doc/release/{version} is better.
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Jialin Qiao 于2019年12月4日周三 下午8:07写道：
> Hi,
>
> We could create a doc branch for each release tag, such as
> release/0.9.0_doc for release/0.9.0.
> This branch only accepts the bug-fix of doc for a released version.
>
> Thanks,
> Jialin QIao
>
> Xiangdong Huang 于2019年12月4日周三 下午5:05写道：
>
> > Hi,
> >
> > Thanks for the report! Glad to see more users are reading the documents.
> >
> > A translation from the Translation Robot Xiangdong Huang:
> >
> > An error in Chinese document: Set TTL and Cancel TTL commands in the
> > document is the same, it is obvious an mistake.
> >
> > I also checked the English version. It is correct in the English version.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
> >
> >
> > 隋凯凌 于2019年12月4日周三 下午4:54写道：
> >
> >>
> >>
> >> 您好，我发现了在中文文档中的错误，请改正。
> >> 在英文文档中此处为unsit，中文文档中，取消ttl的命令与设置ttl的命令相同
> >>
> >
>
Re: 中文文档中第五章第一节有错误
Hi, Thanks for the report! Glad to see more users are reading the documents. A translation from the Translation Robot Xiangdong Huang: An error in Chinese document: Set TTL and Cancel TTL commands in the document is the same, it is obvious an mistake. I also checked the English version. It is correct in the English version. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 隋凯凌 于2019年12月4日周三 下午4:54写道： > > > 您好，我发现了在中文文档中的错误，请改正。 > 在英文文档中此处为unsit，中文文档中，取消ttl的命令与设置ttl的命令相同 >
Pypi distribution for IoTDB Python Client API
Hi, I write a setup.py to distribute IoTDB's Python library to PyPi. Now I just upload it to Test PyPi [1], please have a review to point out which is needed to modify (according to the guide [2]). If no more issues, I will submit a PR for the setup.py file and upload the binary python files to PyPi formally. Notice: if you want to try the python client example by using [3], you need to modify Line 26 and 31 from `from rpc.` to `from iotdb.rpc` [1] https://test.pypi.org/project/apache-iotdb/ [2] https://cwiki.apache.org/confluence/display/INCUBATOR/DistributionGuidelines [3] https://github.com/apache/incubator-iotdb/blob/release%2F0.9.0/client-py/src/client_example.py Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
[DISCUSS] Apache IoTDB (incubating) 0.8.2 RC2 release
Hi, If you have any questions about 0.8.2 RC2, please discuss here. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
[VOTE] Apache IoTDB (incubating) 0.8.2 RC2 release
Hi all, Now I open a new vote for Apache IoTDB (incubating) 0.8.2 RC2, which fixes issues in RC1. Apache IoTDB (incubating) 0.8.2 is a bug-fix version from 0.8.1. You can get its mainly changes from [5]. Apache IoTDB (Incubating) 0.8.2 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. If approved we will seek final release approval from the IPMC. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Release tag: release/0.8.2 Hash for the release tag: 09a94f2c02dec27f483a2ccb41a8265331be193d Before voting +1 PMC/PPMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases. You can achieve the above by following [4]. [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4]) [ ] -1 reject (explanation required) [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1021 [2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc2 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release [5] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc2/RELEASE_NOTES.md Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
[jira] [Created] (IOTDB-336) Binary files incompatible between JDK8 and JDK11
xiangdong Huang created IOTDB-336: - Summary: Binary files incompatible between JDK8 and JDK11 Key: IOTDB-336 URL: https://issues.apache.org/jira/browse/IOTDB-336 Project: Apache IoTDB Issue Type: Bug Reporter: xiangdong Huang I tried to use JDK11 to compile a binary file, you can get it at [https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc1]. However, if a user uses JDK8 to run it, an exception will occur: java.lang.NoSuchMethodError: java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer; It is because before JDK9, ByteBuffer.clear() returns Buffer, while from JDK9 on, the method return ByteBuffer. According to [https://github.com/apache/curator/pull/312], add a parameter `–release 8` can solve the problem. In maven, we can add a property called ``` 8 ``` I am verifying the solution now. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [DISCUSS] Release Apache IoTDB incubating 0.8.2 (bugfix of 0.8.*)
Hi, I find that the binary file can run on JKD11 but run failed on JDK8. I will open a vote of 0.8.2 RC2 after finding out why and fixing it. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年12月2日周一 下午11:40写道： > Taking this to a parallel discuss thread to keep the vote thread cleaner. > > Yeah I did notice that this is indeed a release vote for a real RC ... > sorry for that ... my bad. > > I just read that "someone would like to release" and then the votes > started empty ... > For me this appeared to be a typical discussion ... but when scrolling > down I did now finally see it's actually a real release thread. > > So please just ignore my mumbling. > > Chris > > Am 02.12.19, 14:35 schrieb "Xiangdong Huang" : > > Hi, > > Seems that this is the first time that Francis Du appears in the > mailing > list (and the community). > Maybe he/she is a user or someone who is interested in IoTDB. So it is > understandable that he/she just vote a +1 (no matter for the > discussion or > the release)... > > Yes putting the discussion and the vote together may mislead > participators.. > > And I will withdraw the RC1 because the binary files can not run on > someones' computers... (It is ok on my MacOS, I need to check why.) > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Christofer Dutz 于2019年12月2日周一 下午5:01写道： > > > Hi all, > > > > Just a little suggestion ... ask questions like this in a "[DISCUSS]" > > thread ... > > This is not actually something you should really vote on and the > title is > > quite misleading. > > I for example thought: "Why did Francis vote +1 on a release without > > stating what he did to verify" > > Till I noticed it's not a vote on a release, but a vote on the > question to > > start doing a release. > > > > Chris > > > > > > > > Am 02.12.19, 05:15 schrieb "Francis Du" : > > > > +1 > > > > Xiangdong Huang 于2019年12月1日周日 下午4:57写道： > > > > > Hi all, > > > > > > I'd like to release Apache IoTDB 0.8.2 to fix some critical > bugs in > > 0.8.1. > > > Even though 0.9 is almost released and contains these > bug-fixes, it > > is > > > still needed to maintain 0.8.* for a while because the data > file is > > > incompatible between 0.8 and 0.9 (The good news is there is an > auto > > upgrade > > > tool for the data file in 0.9). > > > > > > Apache IoTDB (incubating) 0.8.2 is a bug-fix version from > 0.8.1. You > > can > > > get its mainly changes from [5]. > > > > > > Apache IoTDB (Incubating) 0.8.2 has been staged under [2] and > it’s > > time to > > > vote > > > on accepting it for release. All Maven artifacts are available > > under [1]. > > > If approved we will seek final release approval from the IPMC. > > > > > > Voting will be open for 72hr. > > > > > > A minimum of 3 binding +1 votes and more binding +1 than > binding -1 > > > are required to pass. > > > > > > Release tag: release/0.8.2 > > > Hash for the release tag: > f81db4a2f62090eb9f51417a729a1cf18b140935 > > > > > > Before voting +1 PMC/PPMC members are required to download > > > the signed source code package, compile it as provided, and > test > > > the resulting executable on their own platform, along with also > > > verifying that the package meets the requirements of the ASF > policy > > > on releases. > > > > > > You can achieve the above by following [4]. > > > > > > [ ] +1 accept (indicate what you validated - e.g. performed > the > > non-RM > > > items in [4]) > > > > > > [ ] -1 reject (explanation required) > > > > > > > > > [1] > > > https://repository.apache.org/content/repositories/orgapacheiotdb-1020 >
Re: Avoid packing incorrect files into source-release.zip
Hi Chris, > And you should guide the RM to the target/checkout/target directory instead of the target directory. I think this is what makes the error. I used target/*-source-release.zip* rather than target/checkout/target/ . Many thanks, and thanks for reading Chinese documents... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年12月2日周一 下午11:46写道： > Hi Xiangdong, > > I think I know what the general problem is: > From that page (not much I can actually understand much) > But it does mention the release:perform step and immediately after that I > mentions the source and binary distributions. > Also it mentions validating the source and binaries build by the prepare > step and does the release perform after that. > > You have to execute the perform step and then validate the signatures of > the artifacts built by that. > > So you should move the source and bin distribution validation guilde to > after the release:perform. > And you should guide the RM to the target/checkout/target directory > instead of the target directory. > > Chris > > > > Am 02.12.19, 14:42 schrieb "Xiangdong Huang" : > > Hi Chris, > > I am sure that I ran `mvn release:perform` after ran `mvn > release:prepare`. On page [1], step 3.1 and 3.2 are `mvn > release:prepare` > and `mvn release:perform` > > As I am going to generate RC2 of 0.8.2, I can try once again. > > [1] > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130027555 > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Christofer Dutz 于2019年12月2日周一 下午4:59写道： > > > Hi Xiangdong, > > > > the "mvn release:prepare" step does the following: > > - Checks if there are uncommitted filed > > - Updates the version to the release version > > - Checks if there are remaining SNAPSHOT dependencies > > - Runs a full build including tests with this version > > - If this build succeeds, It commits the changes and tags this commit > > - Then it changes the versions to the next development version > > - Then it commits this version too > > - Then it pushes the changes > > > > The step you have to do now is run the "mvn release:perform" > > - Check out the tagged version from git into the main > "target/checkout" > > directory > > - Spawns a "mvn -P apache-release deploy" build in that directory > > - This builds the source bundle in "target/checkout/target" and > creates > > the hashes and signs the artifacts > > - During the build it also deploys the maven artifacts to the apache > nexus > > > > As soon as that's done, you: > > - Go to the Apache nexus and close the staging repo > > - Create a new staged release by uploading the RELEASE_NOTES, README > and > > the source bundle together with the hashes and signatures to SVN > > > > To me it looks as if you're simply uploading the stuff created in the > > first step, which is not correct as it isn't > > executed from a clean checkout and it will contain other stuff > that's just > > laying around in your workspace. > > > > Chris > > > > > > Am 01.12.19, 15:35 schrieb "Xiangdong Huang" : > > > > Hi, > > > > > it will checkout the git revision the prepare goal tagged as > release > > version. It will checkout this into the target/checkout > directory. > > If so, it is quite strange that why there was something > incorrect in > > previous releases.. > > > > Now the command is `mvn release:prepare > -DautoVersionSubmodules=true`, > > I am > > not sure whether it download source code from github first, I > need to > > check > > it when I run release next time.. > > > > > So I guess you re-ran the release build more than once > > Yes it may be. Sometime I ran `mvn release:prepare` and if > I find > > failures, I ran `mvn release:rollback` and run > `relrease:prepare` again > > after fixing problems and didnot ran `mvn clean`.. > > > > >The other problem you are having is that the build is generating > > things > > outside the targe
Re: Avoid packing incorrect files into source-release.zip
Hi Chris, I am sure that I ran `mvn release:perform` after ran `mvn release:prepare`. On page [1], step 3.1 and 3.2 are `mvn release:prepare` and `mvn release:perform` As I am going to generate RC2 of 0.8.2, I can try once again. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=130027555 Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年12月2日周一 下午4:59写道： > Hi Xiangdong, > > the "mvn release:prepare" step does the following: > - Checks if there are uncommitted filed > - Updates the version to the release version > - Checks if there are remaining SNAPSHOT dependencies > - Runs a full build including tests with this version > - If this build succeeds, It commits the changes and tags this commit > - Then it changes the versions to the next development version > - Then it commits this version too > - Then it pushes the changes > > The step you have to do now is run the "mvn release:perform" > - Check out the tagged version from git into the main "target/checkout" > directory > - Spawns a "mvn -P apache-release deploy" build in that directory > - This builds the source bundle in "target/checkout/target" and creates > the hashes and signs the artifacts > - During the build it also deploys the maven artifacts to the apache nexus > > As soon as that's done, you: > - Go to the Apache nexus and close the staging repo > - Create a new staged release by uploading the RELEASE_NOTES, README and > the source bundle together with the hashes and signatures to SVN > > To me it looks as if you're simply uploading the stuff created in the > first step, which is not correct as it isn't > executed from a clean checkout and it will contain other stuff that's just > laying around in your workspace. > > Chris > > > Am 01.12.19, 15:35 schrieb "Xiangdong Huang" : > > Hi, > > > it will checkout the git revision the prepare goal tagged as release > version. It will checkout this into the target/checkout directory. > If so, it is quite strange that why there was something incorrect in > previous releases.. > > Now the command is `mvn release:prepare -DautoVersionSubmodules=true`, > I am > not sure whether it download source code from github first, I need to > check > it when I run release next time.. > > > So I guess you re-ran the release build more than once > Yes it may be. Sometime I ran `mvn release:prepare` and if I find > failures, I ran `mvn release:rollback` and run `relrease:prepare` again > after fixing problems and didnot ran `mvn clean`.. > > >The other problem you are having is that the build is generating > things > outside the target directory. > A PR is available[1], which is proposed by a new contributor. A PPCM > has > reviewed the codes and approved on github. > But we need to guarantee that new committers also obey the rule in the > future. So be careful in the code review stage. > > By the way, I think an assembly file is useful for the following > scenario: > > > What is more, it is very helpful when we switch different branches > for > releasing. for example, in v0.9.0, there is a module called session, > which > does not exist in 0.8.0. So, if I switch the branch from 0.9 to 0.8 (or > rel/0.8) for a minor version releasing (e.g., 0.8.2), I have to remove > the > session folder manually. If I forgot that, a dirty source-release.zip > is > generated. But if we have an assembly.xml, it will avoid that. > > As I am using IDEAJ, there is a plain text file `session.iml` (like > .classpath and .project in Eclipse) in session's directory. The file > does > not disappear when I switch to 0.8, and even `mvn clean` does not > delete > the file. > I am not sure whether `mvn release:prepare > -DautoVersionSubmodules=true` > will ignore it ( yes if the command download source codes from > github), but > if I try `mvn package -Papache-release -DskipTests`, the file will be > packed, which is incorrect. > > [1] https://github.com/apache/incubator-iotdb/pull/578 > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Christofer Dutz 于2019年12月1日周日 下午8:57写道： > > > HI all, > > > > I think the problem was that you were not doing the releases right > or not > > staging the right artifacts. > > If you run release:perform ... it will checkout the git
Re: [VOTE] Release Apache IoTDB incubating 0.8.2 (bugfix of 0.8.*)
Hi, Seems that this is the first time that Francis Du appears in the mailing list (and the community). Maybe he/she is a user or someone who is interested in IoTDB. So it is understandable that he/she just vote a +1 (no matter for the discussion or the release)... Yes putting the discussion and the vote together may mislead participators.. And I will withdraw the RC1 because the binary files can not run on someones' computers... (It is ok on my MacOS, I need to check why.) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年12月2日周一 下午5:01写道： > Hi all, > > Just a little suggestion ... ask questions like this in a "[DISCUSS]" > thread ... > This is not actually something you should really vote on and the title is > quite misleading. > I for example thought: "Why did Francis vote +1 on a release without > stating what he did to verify" > Till I noticed it's not a vote on a release, but a vote on the question to > start doing a release. > > Chris > > > > Am 02.12.19, 05:15 schrieb "Francis Du" : > > +1 > > Xiangdong Huang 于2019年12月1日周日 下午4:57写道： > > > Hi all, > > > > I'd like to release Apache IoTDB 0.8.2 to fix some critical bugs in > 0.8.1. > > Even though 0.9 is almost released and contains these bug-fixes, it > is > > still needed to maintain 0.8.* for a while because the data file is > > incompatible between 0.8 and 0.9 (The good news is there is an auto > upgrade > > tool for the data file in 0.9). > > > > Apache IoTDB (incubating) 0.8.2 is a bug-fix version from 0.8.1. You > can > > get its mainly changes from [5]. > > > > Apache IoTDB (Incubating) 0.8.2 has been staged under [2] and it’s > time to > > vote > > on accepting it for release. All Maven artifacts are available > under [1]. > > If approved we will seek final release approval from the IPMC. > > > > Voting will be open for 72hr. > > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 > > are required to pass. > > > > Release tag: release/0.8.2 > > Hash for the release tag: f81db4a2f62090eb9f51417a729a1cf18b140935 > > > > Before voting +1 PMC/PPMC members are required to download > > the signed source code package, compile it as provided, and test > > the resulting executable on their own platform, along with also > > verifying that the package meets the requirements of the ASF policy > > on releases. > > > > You can achieve the above by following [4]. > > > > [ ] +1 accept (indicate what you validated - e.g. performed the > non-RM > > items in [4]) > > > > [ ] -1 reject (explanation required) > > > > > > [1] > https://repository.apache.org/content/repositories/orgapacheiotdb-1020 > > [2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc1 > > [3] https://www.apache.org/dev/release.html#approving-a-release > > [4] > > > > > https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release > > [5] > > > > > https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc1/RELEASE_NOTES.md > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > > -- > Name : Francis Du > Email : francisdu...@gmail.com > > >
Re: Podling Iotdb Report Reminder - December 2019
Update: > There was a project called IoTDB, whose website is iotdb.org. I am not sure whether it is correct, because I can hardly find documents (or download urls of the software) about it... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年12月2日周一 上午10:34写道： > Hi, > > How about the following: > > Required Name Search is done. > On Google Search: > 1. There is a dataset called "iotdb" (Internet of Things Database, from > http://www.green-ic.org/). The last update date is 2017-08-16. > 2. There was a project called IoTDB, whose website is iotdb.org. But > the website can not be accessed. (But the registry expiry date is > 2020-05-27). > A related project called iotdb-mqtt (on NPM) is also not maintained. > > > As all the above are not maintained now, do we need to do something else? > > Best, > > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Justin Mclean 于2019年12月1日周日 下午5:44写道： > >> Hi, >> >> > Looks fine up to now. >> >> I know a name search has been done, A quick google search shows a number >> of minor issues, might be a couple you want to deal with. >> >> Thanks, >> Justin > >
[VOTE] Release Apache IoTDB incubating 0.8.2 (bugfix of 0.8.*)
Hi all, I'd like to release Apache IoTDB 0.8.2 to fix some critical bugs in 0.8.1. Even though 0.9 is almost released and contains these bug-fixes, it is still needed to maintain 0.8.* for a while because the data file is incompatible between 0.8 and 0.9 (The good news is there is an auto upgrade tool for the data file in 0.9). Apache IoTDB (incubating) 0.8.2 is a bug-fix version from 0.8.1. You can get its mainly changes from [5]. Apache IoTDB (Incubating) 0.8.2 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. If approved we will seek final release approval from the IPMC. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Release tag: release/0.8.2 Hash for the release tag: f81db4a2f62090eb9f51417a729a1cf18b140935 Before voting +1 PMC/PPMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases. You can achieve the above by following [4]. [ ] +1 accept (indicate what you validated - e.g. performed the non-RM items in [4]) [ ] -1 reject (explanation required) [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1020 [2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release [5] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc1/RELEASE_NOTES.md Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: Podling Iotdb Report Reminder - December 2019
Hi, The new question in the report is: Is the PPMC managing the podling's brand / trademarks? Are 3rd parties respecting and correctly using the podlings name and brand? If not what actions has the PPMC taken to correct this? Has the VP, Brand approved the project name? Looks fine up to now. If someone know about that, please let me know and I will add it into the report. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年12月1日周日 下午4:01写道： > Hi, > > > I will move the report to confluence tomorrow after @JialinQiao finishing > > releasing 0.9.0. > > > > If Jialin can not finish the release tomorrow, I think I have to remove > > related content… > > The report can be updated before the board meets or you can just put it in > the next report, in theory the report is only for what happen in November > and anything happening between now and the board meeting can be put in the > next report, but I do see some projects not being strict about this. > > Thanks, > Justin
Re: Question about a mix of Unix and windows new lines and extra blank spaces in ASF headers.
Hi Justin,
Many thanks!
> * copyright ownership. The ASF licenses this file to you under the
Apache License, Version 2.0
It is a obvious inconsistent format. I will fix it.
For others, they look different because they are from different file
formats, e.g., java file with /***/, bat file with @REM, antlr g file with
//, script file with #.
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Justin Mclean 于2019年12月1日周日 下午3:17写道：
> Hi,
>
> >> I did notice a mix of unix and windows new lines, you might want to fix
> > that. This is also a very minor slight inconsistency with the ASF headers
> > (extra spaces in some).
>
> Compare these lines:
> regarding copyright ownership. The ASF licenses this file
> * regarding copyright ownership. The ASF licenses this file
> * copyright ownership. The ASF licenses this file to you under the
> Apache License, Version 2.0
> * regarding copyright ownership. The ASF licenses this file
> * regarding copyright ownership. The ASF licenses this file
> # regarding copyright ownership. The ASF licenses this file
> // regarding copyright ownership. The ASF licenses this file
> @REM regarding copyright ownership. The ASF licenses this file
> regarding copyright ownership. The ASF licenses this file
>
> This was put through a sort -u so each line is a variation on the other.
> There may be other differences, I’ve not checked.
>
> I found this by accident via:
> search “copyright” | sort -u
>
> Where search is:
> function search() {
> find . -type f -exec grep -i "$1" {} \; -print
> }
>
> Just a little tool I use to help find things in releases. My incubator
> talks usually mention this.
>
> Thanks,
> Justin
>
>
>
>
Question about a mix of Unix and windows new lines and extra blank spaces in ASF headers.
Hi, In our vote thread on general@, @Justin Mclean pointed out some issues: > I did notice a mix of unix and windows new lines, you might want to fix that. This is also a very minor slight inconsistency with the ASF headers (extra spaces in some). I have no idea about how to find them out.. Does anyone can give me some indication? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: question about Apache Jenkins and Sonar
Hi, thanks Chris and Willem. I have created a jira ticket for applying creating a project on sonarcloud.io [1]. Before the application is complete, I disable the sonar analysis from jenkins temporary. [1] https://issues.apache.org/jira/browse/INFRA-19507 --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Willem Jiang 于2019年12月1日周日 上午9:39写道： > You need to some setup[1] to enable the Sonar Cloud Service for Apache > project. > > [1]https://cwiki.apache.org/confluence/display/INFRA/SonarQube+Analysis > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Nov 30, 2019 at 10:31 PM Christofer Dutz > wrote: > > > > Hi Xiangdong, > > > > The ASF SonarCube instance is no longer being run. > > The build has to be changed to SounarCloud. > > > > Have a look at the PLC4X build (Jenkinsfile). > > We did the change there some time ago. > > > > Chris > > > > Am 29.11.19, 17:24 schrieb "Xiangdong Huang" : > > > > Hi, > > > > I find Apache Jenkins build failed because "SonarQube installation > defined > > in this job (ASF Sonar Analysis) does not match any configured > > installation. Number of installations that can be configured: 0." > > > > I checked recent commits, and find the most possible code > modification is > > that `vulnerability-checks` is moved to `apache-release` profile. > > > > So, is this task who triggers Jenkins to submit a job to SonarQube? > > > > If so, you'd better revoke your modification on the pom file, > @jialin Qiao. > > > > Best, > > -- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > >
Re: Avoid packing incorrect files into source-release.zip
Sorry the PR link is [1]. [1] https://github.com/apache/incubator-iotdb/pull/610 Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年12月1日周日 下午1:45写道： > Hi, > > Considering we packed some incorrect files in the last release (RC1 to > RC4), I think writing an assembly.xml file for generating the > source-release.zip is a good way to avoid that. > > What is more, it is very helpful when we switch different branches for > releasing. for example, in v0.9.0, there is a module called session, which > does not exist in 0.8.0. So, if I switch the branch from 0.9 to 0.8 (or > rel/0.8) for a minor version releasing (e.g., 0.8.2), I have to remove the > session folder manually. If I forgot that, a dirty source-release.zip is > generated. But if we have an assembly.xml, it will avoid that. > > I have written the source-assembly.xml now in PR [1]. The assembly file > looks ugly because we have to declare the files one by one. (I tried the > tag, which is more convenient. But because our > module.artifactId != module.folder name, there is some issues that I can > not solve. Finally I gave up using tag). > > If the PR is accepted, then for all contributors please notice that: > > (1) If you add new source files into a src/ docs/ license folder, it is ok. > (2) If you add a new module, create a new folder, or write a plain text > file under the project's (or a module's) root directory, you have to > maintain the source-assembly.xml file.. Otherwise the new added files will > not be packed into source-release.zip. > > Hope in this way, we can no longer get dirty source-release.zip files. > > [1] > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 >
Avoid packing incorrect files into source-release.zip
Hi, Considering we packed some incorrect files in the last release (RC1 to RC4), I think writing an assembly.xml file for generating the source-release.zip is a good way to avoid that. What is more, it is very helpful when we switch different branches for releasing. for example, in v0.9.0, there is a module called session, which does not exist in 0.8.0. So, if I switch the branch from 0.9 to 0.8 (or rel/0.8) for a minor version releasing (e.g., 0.8.2), I have to remove the session folder manually. If I forgot that, a dirty source-release.zip is generated. But if we have an assembly.xml, it will avoid that. I have written the source-assembly.xml now in PR [1]. The assembly file looks ugly because we have to declare the files one by one. (I tried the tag, which is more convenient. But because our module.artifactId != module.folder name, there is some issues that I can not solve. Finally I gave up using tag). If the PR is accepted, then for all contributors please notice that: (1) If you add new source files into a src/ docs/ license folder, it is ok. (2) If you add a new module, create a new folder, or write a plain text file under the project's (or a module's) root directory, you have to maintain the source-assembly.xml file.. Otherwise the new added files will not be packed into source-release.zip. Hope in this way, we can no longer get dirty source-release.zip files. [1] Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: Podling Iotdb Report Reminder - December 2019
Hi, >> If rate the maturity from 0 (initial steup) to 10 (can graduate), the >> reporter thinks it can be around 4.5. > I don’t think this podling is quite at that point yet, but good progress has been made. I gives a high score for enhancing morale :D. We can remove it in the formal report. Indeed we need to try our best to make it come true. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年12月1日周日 下午12:36写道： > Hi, > > > Some questions like "How does the podling rate their own maturity" is > > quite subjective, so I use "from the reporter's view" or "the reporter > > thinks". Please comment your idea, and I will modify the draft. > > I would just answer for the whole PMC and if anyone disagrees they can > raise it and discuss why and modify the report if needed. > > > If rate the maturity from 0 (initial steup) to 10 (can graduate), the > > reporter thinks it can be around 4.5. > > I don’t think this podling is quite at that point yet, but good progress > has been made. > > Thanks, > Justin
Re: Podling Iotdb Report Reminder - December 2019
Hi, Please review the draft of the report of December2019. (Some questions like "How does the podling rate their own maturity" is quite subjective, so I use "from the reporter's view" or "the reporter thinks". Please comment your idea, and I will modify the draft.) # IoTDB # A brief description of your project, which assumes no knowledge of the project or necessarily of its field IoTDB is a data store for managing large amounts of time series data such as timestamped data from IoT sensors in industrial applications. IoTDB has been incubating since 2018-11-18. #A list of the three most important issues to address in the move towards graduation.: - Learn to discuss things on the mailing list, rather than just post an ISSUE created or closed message, or discuss on Github. - More committers should know how to release a version. And more PPMC should join to vote. - Write more documentation to help new contributors. # Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? - No. # How has the community developed since the last report? - New contributors appears, e.g., HT Hou for PR527, liutaohua for PR578, yx-zhang for PR540, francisdu for ISSUE293, SilverNarcissus for PR327, nlosilva1 for PR298, Zesong Sun etc.. - According to github's records, there are 50 contributors now. - New committer Jack Tsai. - New PPMC: Julian Feinauer - Twitter account is created: Apacheiotdb - More than 137 mails are recorded on dev@ mailing list # How has the project developed since the last report? - IoTDB released two versions, v0.8.1 and 0.9.0 (will be finished tomorrow). - IoTDB v0.9.0 fixed 16 bugs, introduced 31 new features and 27 improvements. (According to the statistics of 0.9.0's RELEASE_NOTE) # How does the podling rate their own maturity. - The community is more diverse than before. As far as the reporter knows, the contributors come from more than 10 companies/organizers. - More users begin to report the bugs, which means that more and more users are using IoTDB. - According to the reporter's view, IoTDB is more stable and has better performance than before. If using the template of previous reports, the status of the community can be: Initial setup Working towards first release - Community building Nearing graduation If rate the maturity from 0 (initial steup) to 10 (can graduate), the reporter thinks it can be around 4.5. # Other: Date of last release: 2019-11-2 (need to check tomorrow) # When were the last committers or PPMC members elected? 2019-11-05 for new committer and 2019-11-07 for new PPMC # Have your mentors been helpful and responsive? Very helpful, especially for releasing versions. Signed-off-by: (iotdb) Justin Mclean Comments: (iotdb) Christofer Dutz Comments: (iotdb) Willem Ning Jiang Comments: (iotdb) Kevin A. McGrail Comments: IPMC/Shepherd notes: ------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 于2019年11月26日周二 上午4:17写道： > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meeting is scheduled for Wed, 18 December 2019, 10:30 am PDT. > The report for your podling will form a part of the Incubator PMC > report. The Incubator PMC requires your report to be submitted 2 weeks > before the board meeting, to allow sufficient time for review and > submission (Wed, December 04). > > Please submit your report with sufficient time to allow the Incubator > PMC, and subsequently board members to review and digest. Again, the > very latest you should submit your report is 2 weeks prior to the board > meeting. > > Candidate names should not be made public before people are actually > elected, so please do not include the names of potential committers or > PPMC members in your report. > > Thanks, > > The Apache Incubator PMC > > Submitting your Report > > -- > > Your report should contain the following: > > * Your project name > * A brief description of your project, which assumes no knowledge of > the project or necessarily of its field > * A list of the three most important issues to address in the move > towards graduation. > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > * How has the community developed since the last report > * How has the project developed since the last report. > * How does the podling rate their own maturity. > > This should be appended to the Incubator Wiki page at: > > https://cwiki.apache.org/confluence/display/INCUBATOR/December2019 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Not
question about Apache Jenkins and Sonar
Hi, I find Apache Jenkins build failed because "SonarQube installation defined in this job (ASF Sonar Analysis) does not match any configured installation. Number of installations that can be configured: 0." I checked recent commits, and find the most possible code modification is that `vulnerability-checks` is moved to `apache-release` profile. So, is this task who triggers Jenkins to submit a job to SonarQube? If so, you'd better revoke your modification on the pom file, @jialin Qiao. Best, -- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Pay attention to mentors' comments
Hi all, I am writing the podling report of December, and then find our mentors' comments on September. Sorry for the late reading. But I think most of us have not read the content, so I copy two of them (which require us change) here: - More active involvement by the PPMC is needed in veoting releases. While it improved, still more discussion needs to happen on the mailing list. - I really would like to see more mailing list usage, cause the number of commit messages is in strong contrast to the discussions. I as a mentor some time don't have a clue what the project is working on. I think many guys are working hard to commit codes, but remember to share your idea before you implement it (or after you implemented it). "the number of commit messages is in strong contrast to the discussions", hope we can avoid that, and hope IoTDB can graduate as soon as possible :D Best, -- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
[jira] [Created] (IOTDB-329) MetricService not quite in Integration Tests (easy-fix, for fresh contributors)
xiangdong Huang created IOTDB-329: - Summary: MetricService not quite in Integration Tests (easy-fix, for fresh contributors) Key: IOTDB-329 URL: https://issues.apache.org/jira/browse/IOTDB-329 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.8.0, 0.9.0, 0.8.1 Reporter: xiangdong Huang Attachments: image-2019-11-29-22-38-52-640.png There are some error infos on Travis: !image-2019-11-29-22-38-52-640.png! It is because in our ITs, MetricService is not closed after an IT finished. It is quite easy to fix that, just add the code into `EnvironmentUtils.cleanEnv()`: ``` MetricsService.getInstance().stop(); ``` before `cleanAllDir();` -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-328) Check the validity of settings in configuration files when restart and upgrade
xiangdong Huang created IOTDB-328: - Summary: Check the validity of settings in configuration files when restart and upgrade Key: IOTDB-328 URL: https://issues.apache.org/jira/browse/IOTDB-328 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.8.0, 0.9.0, 0.8.1 Reporter: xiangdong Huang Hi, Considering a scenario: A user used v0.8.0 first, and changed some parameters (e.g., the default encoding method of the time column), and wrote data. Then, suppose the user upgrades iotdb to 0.9. As there are some new features are introduced in 0.9 and the configuration file may be updated, the user may replace his iotdb-engine.properties file by using the latest template. However, at this time, the user may forget to change the default encoding method of the time column in the new configure file, which will bring errors. So, two new functions are needed: (1) saving parameters that can not be changed after an intializaion from the configuration file to system/ folder; (2) When startup, verify the parameters.. To do that, we need to discuss about that which parameters are needed to be recorded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Refactor Statistics
Hi Jialin, There are UTs failed... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年11月29日周五 下午9:07写道： > Hi, > > I have fixed issue > - IOTDB-325 <https://issues.apache.org/jira/browse/IOTDB-325> in this PR: > https://github.com/apache/incubator-iotdb/pull/587 > > This is mainly a code optimization： > - Move start time, end time, count in PageHeader and ChunkMetadata into > Statistics inside the two > - Remove maxTombstoneTime in ChunkHeader > - Remove StatisticsForFilter > - Simplify the serialize and deserialize of Statistics > > Thanks, > Jialin Qiao >
Re: How to upgrade thrift?
Hi, https://github.com/ccascone/mvn-thrift-compiler only supports thrift 0.9.*. Now we have thrift compiler binary files at https://github.com/jt2594838/mvn-thrift-compiler, which can be used for thrift 0.12 and 0.13. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Tian Jiang 于2019年11月26日周二 下午12:13写道： > Greetings, > > > The currently used thrift has a known bug and can be fixed by upgrading it > to 0.10.0 or higher. But I am not familiar with the plugin that downloads > thrift, could someone help me fix it? > > > https://issues.apache.org/jira/browse/IOTDB-322 > https://issues.apache.org/jira/browse/THRIFT-2157 > > > Best, > Tian Jiang > | | > Tian Jiang > | > | > jt2594...@163.com > | > 签名由网易邮箱大师定制 > >
Re: [VOTE] Apache IoTDB 0.9.0 (incubating) RC5 release
+1. I checked: - mvn apache-rat:check. - DISCLAIMER LICENSE NOTICE exist and the content is ok. - No *.jar, no *.tsfile, no *.ts binary files in the source-release.zip file - compiling the source codes on WinOS successfully, all UT passed. - can run start-server.bat and start-client.bat on WinOS Minor issues: - Document: no readme for tools/upgrade/offline-upgrade.sh, After the releasing, we need add a document on the website for the tool (or on the github, or on the confluence. Either is ok.) - As Kevin said and discussions before, the client scripts should be moved to bin out of sbin. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年11月23日周六 下午6:57写道： > Hi all, > > > Now I open a new ticket for Apache IoTDB (incubating) 0.9.0 RC5, which fixs > some issues comparing with RC4. You can find the details at the end of this > email. > > > Apache IoTDB (incubating) 0.9.0 is a major version with many exciting > features. > You can get the release notes in [5]. > > > Apache IoTDB (Incubating) 0.9.0 has been staged under [2] and it’s time to > vote on accepting it for release. All Maven artifacts are available under > [1]. > If approved we will seek final release approval from the IPMC. > > > Voting will be open for 72hr. > > > A minimum of 3 binding +1 votes and more binding +1 than binding -1 are > required to pass. > > > Release tag: release/0.9.0 > > > Hash for the release tag: 257df94d57c29c628b1ab0d6a2fdd20ba7df9ca4 > > > Per [3] "Before voting +1 PMC/PPMC members are required to download the > signed source code package, compile it as provided, and test the resulting > executable on their own platform, along with also verifying that the > package > meets the requirements of the ASF policy on releases." > > > Difference with RC4: > > > - Fix windows start problem > - Fix deadlock between merge and query > > > > > You can achieve the above by following [4]. > > > [ ] +1 accept (indicate what you validated - e.g. performed the non-RM > items in [4]) > [ ] -1 reject (explanation required) > > > [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1018 > [2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.0/rc5 > [3] https://www.apache.org/dev/release.html#approving-a-release > [4] > https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release > [5] > https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.0/rc5/RELEASE_NOTES.md > > > Thanks, > -- > Jialin Qiao > School of Software, Tsinghua University > > > 乔嘉林 > 清华大学 软件学院
[jira] [Created] (IOTDB-320) [Travis] [WinOS] [ERROR] OS=Windows and the assembly descriptor contains a *nix-specific root-relative-reference (starting with slash) /
xiangdong Huang created IOTDB-320: - Summary: [Travis] [WinOS] [ERROR] OS=Windows and the assembly descriptor contains a *nix-specific root-relative-reference (starting with slash) / Key: IOTDB-320 URL: https://issues.apache.org/jira/browse/IOTDB-320 Project: Apache IoTDB Issue Type: Bug Reporter: xiangdong Huang Travis for WinOS has the following error: [INFO] 1736[INFO] --- maven-assembly-plugin:3.0.0:single (server-assembly) @ iotdb-server --- 1737[INFO] Reading assembly descriptor: src/assembly/server.xml 1738[ERROR] OS=Windows and the assembly descriptor contains a *nix-specific root-relative-reference (starting with slash) / 1739[INFO] Copying files to C:\Users\travis\build\apache\incubator-iotdb\server\target\iotdb-server-0.9.1-SNAPSHOT 1740[WARNING] Assembly file: C:\Users\travis\build\apache\incubator-iotdb\server\target\iotdb-server-0.9.1-SNAPSHOT is not a regular file (it may be a directory). It cannot be attached to the project build for installation or deployment. 1741[ERROR] OS=Windows and the assembly descriptor contains a *nix-specific root-relative-reference (starting with slash) / 1742[INFO] Building zip: C:\Users\travis\build\apache\incubator-iotdb\server\target\iotdb-server-0.9.1-SNAPSHOT.zip 1743[INFO] 1744[INFO] --- maven-failsafe-plugin:2.22.0:integration-test (run-integration-tests) @ iotdb-server --- 1745[INFO] [https://travis-ci.org/apache/incubator-iotdb/jobs/615886573] It may because / is incorrect for Win users. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: A SQL to Query a Group of Devices Seperately
Hi, The term "group by device" is fine for ok. Or, we can I think classify the queries into 3 part: 1. return data points time series by time series, while in each timeseries, the data points are ordered by the timestamp. (Or, totally ordered by timestamp for all timeseries) 2. Join all time series that belong to the same device on the timestamp, in Relational SQL, looks like d1.s1 join d1.s2 on d1.s1.time=d1.s2.time join d1.s3 on d1.s1.time=d1.s3.time ... 3. Join all the time series in the database, which is what IoTDB now supports. This issue IOTDB-305 is for solving the 2nd query. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Lei Rui 于2019年11月23日周六 下午12:02写道： > Hi Tsai, > > > +1 for your idea. It sounds good to me. > > > Best, > Lei Rui > On 11/23/2019 09:42，Jack Tsai wrote： > Hi all, > > I am recently working on this issue: > https://issues.apache.org/jira/browse/IOTDB-305, which is about resolving > the problem while users want to query something like below as the issue > reporter Lei Rui said: > > select * from root.sg.d1,root.sg.d2 where s1=1 (a demo > conception) > / select * from root.sg.* where s1=1 (a demo conception) > > There is no specific sql that could satisfy this kind of query > requirement. The only one which is similar to this concept is using the > “group by device” statement. However, it also cannot return the appropriate > result the users need as what Lei Rui mentioned in the issue. > > Now, I plan to edit the implement logic of the “group by device” > statement. The original implement method, which is like using the “and” > statement to form the condition part of the sql as mentioned in this issue, > cannot well suited for regular users’ requirements. > > In conclusion, the original function of the “group by device” will be > abandoned, and it will be replaced by the one which mentioned in this issue > to satisfy users query. I’m not sure whether this is OK for you guys or the > project. So if you got any advice, please welcome to discuss with me. > > Best regards, > Jack Tsai >
[jira] [Created] (IOTDB-319) java deadlock (not sure how to reproduce)
xiangdong Huang created IOTDB-319: - Summary: java deadlock (not sure how to reproduce) Key: IOTDB-319 URL: https://issues.apache.org/jira/browse/IOTDB-319 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.9.0 Reporter: xiangdong Huang Attachments: deadlock.out Hi, my colleague gives me an IoTDB instance which has no response for "select " SQL. (but for Schema query sql, it works). I used jstack to check the process and find a deadlock, you can get the detailed info in the attachment. Found one Java-level deadlock: = "pool-2-IoTDB-JDBC-Client-thread-16": waiting to lock monitor 0x7fdab800ff68 (object 0x0003c7163218, a org.apache.iotdb.db.query.control.FileReaderManager), which is held by "pool-2-IoTDB-JDBC-Client-thread-3" "pool-2-IoTDB-JDBC-Client-thread-3": waiting for ownable synchronizer 0x0003c6106f40, (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync), which is held by "MergeThread-0" "MergeThread-0": waiting to lock monitor 0x7fdab800ff68 (object 0x0003c7163218, a org.apache.iotdb.db.query.control.FileReaderManager), which is held by "pool-2-IoTDB-JDBC-Client-thread-3" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-318) do not print error log into log_error.log file when the server receives a wrong SQL
xiangdong Huang created IOTDB-318: - Summary: do not print error log into log_error.log file when the server receives a wrong SQL Key: IOTDB-318 URL: https://issues.apache.org/jira/browse/IOTDB-318 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.9.0 Reporter: xiangdong Huang Hi, log_error.log and log_warn.log are two important files for DBA, and the messages in those files should be valuable enough. Now, if a client sends a incorrect sql to iotdb, e.g., " show select a from from root.b;", then the server will print error info to log_error.log, like : 2019-11-23 10:35:13,749 [pool-2-IoTDB-JDBC-Client-thread-15] ERROR org.apache.iotdb.db.service.TSServiceImpl:653 - meet error while parsing SQL to physical plan:2019-11-23 10:35:13,749 [pool-2-IoTDB-JDBC-Client-thread-15] ERROR org.apache.iotdb.db.service.TSServiceImpl:653 - meet error while parsing SQL to physical plan:org.apache.iotdb.db.exception.query.IllegalASTFormatException: Parsing error, statement [show devices root.perform.group_9] failed when parsing AST tree to generate logical operator. Detailed information: [line 1:5 'show'] at org.apache.iotdb.db.qp.QueryProcessor.parseSQLToAST(QueryProcessor.java:102) at org.apache.iotdb.db.qp.QueryProcessor.parseSQLToPhysicalPlan(QueryProcessor.java:69) at org.apache.iotdb.db.service.TSServiceImpl.executeStatement(TSServiceImpl.java:633) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:1465) at org.apache.iotdb.service.rpc.thrift.TSIService$Processor$executeStatement.getResult(TSIService.java:1450) at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39) at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) This kind of error can just be considered as an info level log, and do not need to print its exception stack. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Apache IoTDB 0.9.0 (incubating) RC4 release
Hi,
the same -1.
"can't start iotdb on Windows" is reproduced on my PC.
Good luck..
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Lei Rui 于2019年11月22日周五 下午5:15写道：
> Hi,
> because of the issue IOTDB-315 "Can't start iotdb on windows" just found,
> I change my vote to -1 (PPMC binding).
>
>
> Best,
> Lei Rui
>
>
> On 11/22/2019 11:12，Tian Jiang wrote：
>
>
> Hi,
> +1 (PPMC vote)
>
> The followings are successfully verified:
>
> Source release:
> 1. ASC sinature
> 2. Hashes
> 3. LICENSE, NOTICE, README, RELEASE_NOTES
> 4. RAT
> 5. mvn clean package
> 6. start server and client
> 7. execute basic operations and reboot
> 8. python client
>
> Binary distribution:
> 1. ASC sinature
> 2. Hashes
> 3. start server and client
> 4. execute basic operations and reboot
> 5. python client
>
>
> Best,
> Tian Jiang
> | |
> Tian Jiang
> |
> |
> jt2594...@163.com
> |
> 签名由网易邮箱大师定制
>
>
> On 11/22/2019 09:44，Lei Rui wrote：
> My vote is +1 (PPMC binding).
>
>
> 1. download staged artifacts. Check their signature and hashes.
> ✔ [RM] verify the reported signature is for an "apache.org" address
> ("gpg: Good signature from ...")
> ✔ [RM] verify the reported hashes
> 2. extract src bundle
> ✔ verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
> the extracted source bundle
> ✔ [RM] verify the staged source README, RELEASE_NOTE files correspond to
> those in the extracted source bundle
> 3. staged src bundle items: content, can compile & test
> ✔ check the contents of LICENSE, NOTICE, README, RELEASE_NOTES
> ✔ UNPACK the binary artefact and check the contents of LICENSE-binary and
> NOTICE-binary
> ✔ build from directions in README with an empty maven local repo: mvn
> clean package -DskipTests -Dmaven.repo.local=../.m2
> ✔ [RM] review target/rat.txt (though the build should fail if RAT
> constraints aren't met)
> - mvn clean apache-rat:check
> - Find and files containing binary content with this command: find . -type
> f -name 'rat.txt' -exec grep -l " B " {} \;
> - Then review for B (binary) content in those files:
> grep " B " ./grafana/target/rat.txt
> grep " B " ./server/target/rat.txt
> I find:
> B
> /home/ruilei/tools/downloaded-iotdb-0.9.0rc4/0.9.0/rc4/apache-iotdb-0.9.0-incubating/grafana/img/add_data_source.png
> B
> /home/ruilei/tools/downloaded-iotdb-0.9.0rc4/0.9.0/rc4/apache-iotdb-0.9.0-incubating/grafana/img/edit_data_source.png
> B
> /home/ruilei/tools/downloaded-iotdb-0.9.0rc4/0.9.0/rc4/apache-iotdb-0.9.0-incubating/grafana/img/add_graph.png
> B
> /home/ruilei/tools/downloaded-iotdb-0.9.0rc4/0.9.0/rc4/apache-iotdb-0.9.0-incubating/server/src/main/resources/iotdb/ui/static/iotdb-logo.png
> ✔ Search for SNAPSHOT references: find . -type f -name 'pom.xml' -exec
> grep -l "SNAPSHOT" {} \;
> ✔ ./mvnw.sh install
> ✔ ./mvnw.sh site:site
>
>
> Best,
> Lei Rui
>
>
> On 11/21/2019 12:41，Jialin Qiao wrote：
> Hi all,
>
>
> Now I open a new ticket for Apache IoTDB (incubating) 0.9.0 RC4, which fixs
> some issues comparing with RC3. You can find the details at the end of this
> email.
>
>
> Apache IoTDB (incubating) 0.9.0 is a major version with many exciting
> features.
> You can get the release notes in [5].
>
>
> Apache IoTDB (Incubating) 0.9.0 has been staged under [2] and it’s time to
> vote on accepting it for release. All Maven artifacts are available under
> [1].
> If approved we will seek final release approval from the IPMC.
>
>
> Voting will be open for 72hr.
>
>
> A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
> required to pass.
>
>
> Release tag: release/0.9.0
>
>
> Hash for the release tag: eedfec84462c0f574f9d6ade5ac53801cb3bc869
>
>
> Per [3] "Before voting +1 PMC/PPMC members are required to download the
> signed source code package, compile it as provided, and test the resulting
> executable on their own platform, along with also verifying that the
> package
> meets the requirements of the ASF policy on releases."
>
>
> Difference with RC3:
>
>
> Remove the .tsfile
>
>
>
>
> You can achieve the above by following [4].
>
>
> [ ] +1 accept (indicate what you validated - e.g. performed the non-RM
> items in [4])
> [ ] -1 reject (explanation required)
>
>
> [1] https://repository.apache.org/content/repositories/orgapacheiotdb-1016
> [2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.0/rc4
> [3] https://www.apache.org/dev/release.html#approving-a-release
> [4]
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
> [5]
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.9.0/rc4/RELEASE_NOTES.md
>
>
> Thanks,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
>
> 乔嘉林
> 清华大学 软件学院
Re: [jira] [Created] (IOTDB-315) Can't start iotdb on windows
Ops, is 0.9.0-RC4 also involved? --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Lei Rui (Jira) 于2019年11月22日周五 下午4:18写道： > Lei Rui created IOTDB-315: > - > > Summary: Can't start iotdb on windows > Key: IOTDB-315 > URL: https://issues.apache.org/jira/browse/IOTDB-315 > Project: Apache IoTDB > Issue Type: Bug > Reporter: Lei Rui > > > > D:\new\incubator-iotdb\server\target\iotdb-server-0.9.0-SNAPSHOT\sbin>.\start-server.bat > > Starting IoTDB > > If you want to change this configuration, please check > conf/iotdb-env.sh(Unix or OS X, if you use Windows, check > conf/iotdb-env.bat). > 此时不应有 (。 > > > > I use master branch. commit id=def4daf2addef0062fe04f698a825301ffa343bc > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
How to release/distribute the plugins of IoTDB (garafana-connector, spark-connector, hive-connector etc.)
Hi, We have source-release.zip and binary.zip files, but the binary distribution zip file does not contains the grafana-connector, spark-connector and hive-connector, as these modules are not required for all users. And, including them may cause the binary zip file very large, which is not friendly for users who want to run IoTDB on a raspberry pi or some other embedded devices.. So, can we release these plugins in separate? If so, what is the process? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
How to add a "search" function on the website for retrievaling documents
Hi, Can our website support search content among the documents? Is that possible and easy to do technically? E.g., if I want to find out how to set the TTL (because it is a new feature and I just know that we have the function but I didn't used it), a search button will help me a lot. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: [VOTE] Apache IoTDB 0.9.0 (incubating) RC3 release
Hi, I have no other issues. look forward to rc4. - signature and hash fine - DISCLAIMER exists - LICENSE and NOTICE ok for me - all ASF files have ASF source headers - can compile from source Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Kevin A. McGrail 于2019年11月21日周四 上午10:07写道： > Any other issues that you see? That way we can streamline an rc4. > > On Wed, Nov 20, 2019, 21:05 Xiangdong Huang wrote: > > > Hi, > > > > Sorry I want to -1 > > > > "./tsfile/read_write_rle.tsfile" is not needed, it is generated by some > UT. > > This file is to large, ~40MB, that is why I want to -1. > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > > > Justin Mclean 于2019年11月21日周四 上午9:34写道： > > > > > Hi, > > > > > > +1 (binding) > > > > > > I checked: > > > - incubating in name > > > - signature and hash fine > > > - DISCLAIMER exists > > > - LICENSE and NOTICE good > > > - no unexpected binary files in course release, although there is this > > [1] > > > is this needed? > > > - all ASF files have ASF source headers > > > - can compile from source > > > > > > Thanks, > > > Justin > > > > > > 1. ./tsfile/read_write_rle.tsfile > > >
Re: [VOTE] Apache IoTDB 0.9.0 (incubating) RC3 release
Hi, Sorry I want to -1 "./tsfile/read_write_rle.tsfile" is not needed, it is generated by some UT. This file is to large, ~40MB, that is why I want to -1. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年11月21日周四 上午9:34写道： > Hi, > > +1 (binding) > > I checked: > - incubating in name > - signature and hash fine > - DISCLAIMER exists > - LICENSE and NOTICE good > - no unexpected binary files in course release, although there is this [1] > is this needed? > - all ASF files have ASF source headers > - can compile from source > > Thanks, > Justin > > 1. ./tsfile/read_write_rle.tsfile
[jira] [Created] (IOTDB-310) do not delete bad WAL files
xiangdong Huang created IOTDB-310: - Summary: do not delete bad WAL files Key: IOTDB-310 URL: https://issues.apache.org/jira/browse/IOTDB-310 Project: Apache IoTDB Issue Type: Improvement Reporter: xiangdong Huang in iotdb-264, we skip the bad wal, and then, the wal file will be deleted. we can try to just rename the wal to save the wal after all others are replayed. If so, it gives a chance to let users check the file manually in the future. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: release 0.8.2
Hi, Yes, I'd like to do that and Jialin can go on to release 0.9.0 meanwhile. But I think I will encounter the same problem about the ASF header of MavenWrapper.java file when starting a vote... Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年11月20日周三 下午3:56写道： > Hi Xiangdong, > > that sounds reasonable to me (that’s what minor releases are for). > So if cherry-pick the fix and voluinteer as RM I think it’s a good move to > do so! > > Julian > > Am 20.11.19, 08:51 schrieb "Xiangdong Huang" : > > Hi, > > Some users report the bug of IoTDB-264, which has been fixed in 0.9.0 > (not > released now). It is a critical bug and it is very easy to trigger the > bug > (if users define time series A's data type as INT, but they write into > the > time series a float data). > > However, these users are using 0.8.1 and may want to keep using 0.8.1 > for a > while, So, I'd like to release 0.8.2 latter for fix that bug. > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > >
release 0.8.2
Hi, Some users report the bug of IoTDB-264, which has been fixed in 0.9.0 (not released now). It is a critical bug and it is very easy to trigger the bug (if users define time series A's data type as INT, but they write into the time series a float data). However, these users are using 0.8.1 and may want to keep using 0.8.1 for a while, So, I'd like to release 0.8.2 latter for fix that bug. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: [VOTE] Apache IoTDB 0.9.0 (incubating) RC2 release
Hi Chris, So, sounds that we need to remove the declaration in the LICENSE file? ``` The following class is modified from Maven Wrapper, which is under Apache License 2.0: ./.mvn/wrapper/MavenWrapperDownloader.java ``` Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年11月19日周二 下午4:52写道： > Hi Justin, > > this is a file I personally wrote and submitted to the maven-wrapper > project. > So technically it could have the Apache header ... after all, I put it > there. So I think the Apache header doesn't have to be replaced. > > Chris > > > > Am 18.11.19, 21:21 schrieb "Justin Mclean" : > > HI, > > I’m -1 on this as the maven wrapper [1] is still not being handled > correctly, please read my previous comments. This is a 3rd party file and > should not have an ASF header, you can't alter the header of a 3rd party > file without permission. Thanks for fixing the other issues. > > Thanks, > Justin > > 1. .mvn/wrapper/MavenWrapperDownloader.java > > > >
[jira] [Created] (IOTDB-309) build docker file failed because installing thrift failed
xiangdong Huang created IOTDB-309: - Summary: build docker file failed because installing thrift failed Key: IOTDB-309 URL: https://issues.apache.org/jira/browse/IOTDB-309 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.8.1, 0.8.0 Reporter: xiangdong Huang Someone told me that he built docker failed, because ``` E: Version '0.9.1-2.1' for 'thrift-compiler' was not found ``` I have reproduced the exception. It is because apt repository has update the version to 0.9.1-2.1+b1 so, just modify the line 25 in Dockerfile as: ``` && apt install wget unzip lsof procps maven thrift-compiler=0.9.1-2.1+b1 -y \ ``` . -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Apache IoTDB 0.9.0 (incubating) RC2 release
Hi, So, remove the current header, put its original header back, and exclude the file from apache-rat-plugin. (The file has been claimed in iotdb's LICENSE file) Is that ok? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年11月19日周二 上午4:21写道： > HI, > > I’m -1 on this as the maven wrapper [1] is still not being handled > correctly, please read my previous comments. This is a 3rd party file and > should not have an ASF header, you can't alter the header of a 3rd party > file without permission. Thanks for fixing the other issues. > > Thanks, > Justin > > 1. .mvn/wrapper/MavenWrapperDownloader.java > >
[jira] [Created] (IOTDB-308) jdk error when using Travis + Windows
xiangdong Huang created IOTDB-308: - Summary: jdk error when using Travis + Windows Key: IOTDB-308 URL: https://issues.apache.org/jira/browse/IOTDB-308 Project: Apache IoTDB Issue Type: Bug Reporter: xiangdong Huang Attachments: image-2019-11-18-22-09-34-671.png Sometime travis may failed on WinOS because of: !image-2019-11-18-22-09-34-671.png! It is a quite strange exception. The only thing I can do is change a new JDK.. So, I tried to download jdk zip file manually. And, in many cases, travis on WinOS will be timeout, which is als needed to be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Come back to the community
I also write a document to introduce how to sign other's key, you can get it at [1]. It is translated from calcite's document[2]. Hope it is helpful for you. [1] https://cwiki.apache.org/confluence/display/IOTDB/How+to+certify+someone%27s+GPG+key+in+Chinese [2] https://gist.github.com/F21/b0e8c62c49dfab267ff1d0c6af39ab84 --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年11月18日周一 下午1:21写道： > Hi, > > After one weeks disappearance, I am back to the community now :D > > And I have signed Jialin's GPG key @Jialin, hope it does not delayed your > RM work. > > Best, > ------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 >
Come back to the community
Hi, After one weeks disappearance, I am back to the community now :D And I have signed Jialin's GPG key @Jialin, hope it does not delayed your RM work. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: [disccuss] Apache IoTDB 0.9.0 incubating RC1 release
Hi Justin, > I’m not sure that is the right solution. Was this file developed at the ASF or elsewhere? My understanding is that it come from a 3rd party and thus should not have an ASF header but a 3rd party one. Be sure to mention what license it is under in the LICENSE file as well. (I guess that) the file comes from [1], but I am not sure because Chris added it into the project. (Chris is also the maintainer of the file according to the records on Github of [1]). I added a declarison in License file from 0.8.1 version: ``` The following class is modified from Maven Wrapper ./.mvn/wrapper/MavenWrapperDownloader.java ``` And, in [1] originally has an ASF header. So maybe it is fine to add an ASF header in the file in our project. [1] https://github.com/takari/maven-wrapper/blob/master/.mvn/wrapper/MavenWrapperDownloader.java Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年11月15日周五 上午10:20写道： > Hi, > > >> - NOTICE is incorrect "Copyright 2019 and onwards” is not valid to say > > > > I checked [1], it should be " Copyright 2001-2019 The Apache Software > > Foundation” > > Probably you just want "Copyright 2019” I think, as they are the only > years that IoTDB have made a release. > > >> - NOTICE is missing information from from the common NOTICE file [1][3] > > > > Hi, @Justin, are you meaning the following guidance? " Copyright > > notifications which have been relocated from source files (rather than > > removed) must be preserved in NOTICE. However, elements such as the > > copyright notifications embedded within BSD and MIT licenses need not be > > duplicated in NOTICE -- it suffices to leave those notices in their > > original locations.” > > No, it’s this: "If the dependency supplies a NOTICE file, its contents > must be analyzed and the relevant portions bubbled up into the top-level > NOTICE file." > > > Hi Justin, I have added the ASF header on release-0.8.1, but forgot to > > cherry-pick the modifications to the master… > > I’m not sure that is the right solution. Was this file developed at the > ASF or elsewhere? My understanding is that it come from a 3rd party and > thus should not have an ASF header but a 3rd party one. Be sure to mention > what license it is under in the LICENSE file as well. > > Thanks, > Justin
[disccuss] Apache IoTDB 0.9.0 incubating RC1 release
Hi, > - LICENSE need to mention license of Maven Wrapper As Lei Rui and Justin pointed out some issues, I find it is my fault that some changes are not cherry-picked from rel/0.8 to master and rel/0.9. So, we need to scan the commitlogs between release-0.8.0 to release-0.8.1 and cherry-pick needed commitlogs to rel/0.9 and the master branch. @Jialin > - NOTICE is incorrect "Copyright 2019 and onwards” is not valid to say I checked [1], it should be " Copyright 2001-2019 The Apache Software Foundation" > - NOTICE is missing information from from the common NOTICE file [1][3] Hi, @Justin, are you meaning the following guidance? " Copyright notifications which have been relocated from source files (rather than removed) must be preserved in NOTICE. However, elements such as the copyright notifications embedded within BSD and MIT licenses need not be duplicated in NOTICE -- it suffices to leave those notices in their original locations." > large number of files have the incorrect ASF header. There should be no "Copyright © 2019 Apache IoTDB(incubating) If you are using IDEA to generate the ASF header on a new file, please fix them to avoid the same error in the future... > It is still unclear where the "Maven Wrapper” code comes from and the file is missing a license header. Hi Justin, I have added the ASF header on release-0.8.1, but forgot to cherry-pick the modifications to the master... > - There an unexpected binary file in the release [4] (maven-wrapper.jar) @Jialin, help me to add a step "rm .mvnw/wrapper/*.jar" on the Chinese Guidance on Apache Confluence. [1] https://github.com/apache/commons-collections/blob/master/NOTICE.txt [3] http://www.apache.org/dev/licensing-howto.html#alv2-dep Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: [DISCUSS] Release 0.9.0
Hi Jialin, I can help with you at afternoon. Willem Jiang has signed my key last month. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Jialin Qiao 于2019年11月13日周三 下午12:25写道： > Hi Justin, > > Thanks! I will ask Xiangdong for help face to face. > > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 > > > -原始邮件- > > 发件人: "Justin Mclean" > > 发送时间: 2019-11-13 11:44:34 (星期三) > > 收件人: dev@iotdb.apache.org > > 抄送: > > 主题: Re: [DISCUSS] Release 0.9.0 > > > > Hi, > > > > > Could someone please help sign my gpg key? The signing step is here: > https://gist.github.com/F21/b0e8c62c49dfab267ff1d0c6af39ab84 > > > > This needs to be done in person face to face and requires verifying your > ID by some means (usually a government issues ID card). > > > > It is not a requirement for making a release but just adds you to the > wider ASF web of trust. > > > > Thanks, > > Justin >
Re: Self check whether the client is compatible with the server
Hi, Yes some of them are using released version (like 0.8), but sometimes they found a new feature is introduced in 0.9.0-SNAPSHOT and they'd like to use that (e.g., register timeseries automatically), they may try the snapshot version. Releasing 0.9.0 ASAP is needed. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年11月12日周二 下午3:34写道： > Hi, > > I'm curious to know why are they using snapshot versions rather than > released versions? Do you know why, in general users shouldn’t be using > snapshot versions. > > Thanks, > Justin
Self check whether the client is compatible with the server
Hi, Sorry this week I have few time to pay attention to the project development, but I have met many real users of IoTDB in factories and companies and introduced IoTDB to many new users recently. Then I notice that one of the main exceptions that users met is the version incompatible between the client and the server. (many users are trying 0.9.0-SANPSHT for a POC). So, I suggest that from 0.9 on, when the client connect to a server, the client need to check the version compatibility first, and show the error message (if there is) to users friendly. Even for the snapshot version, we can also add a temporary version to guarantee users can find why the client does not work. Best, -- --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: Javas ByteBuffer[vs Nettys ByteBuf
Hi, I did not. But I have tried calling Snappy.compress() and decompress() with on-heap and off-heap bytes about 6 months ago. off-heap compress is very fast. But in that experiment, creating off-heap bytes is time-consuming (because in that version, creating new byte array or bytebuffer is very frequent). I am also interested in the performance of Netty's ByteBuf. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年11月7日周四 下午3:13写道： > Hi folks, > > in iotdb we have a quite frequent use of Javas native ByteBuffer’s for our > IO. I was wondering if anybody did an analysis on object creation / > destruction and so on. > As some may know, the netty project provides an interface called ByteBuf ( > https://netty.io/4.0/api/io/netty/buffer/ByteBuf.html). Then, > implementations based on On-Heap or Off-Heap memory can be used for > specific use cases. Some operations are even zero-copy. > > Furthermore, ByteBuf are Reference counted and recycled, so the > performance will definetly be superior. > The only important question is if anybody already analyzed how much > potential there is and if its worth the effort? > > Julian >
Update Apache IoTDB Project Incubation Status Webpage
Hi, I have updated the content of http://incubator.apache.org/projects/iotdb.html by modifying iotdb.xml at https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects I added the creation dates of the Confluence, Mailing list, Github repo, copyright, and Verify distribution rights.. 1. After the page is updated, please have a check whether the info is correct (if you know the actual date).. 2. And, now 5 hours passed but the page is still not updated... Do I need to do something others? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: Working on refactoring metadata package
Hi, > 3. Do we consider add a long id to each path? (is that helpful?) > As far as I know, long id isn't helpful... maybe @Yanzhe An could give us more detailed information. > 3. Using string Ids does not induce too much overhead as far as I am concerned, not to mention the cost of maintaining the bidirectional index. And, considering about the cluster mode, we need to use Consistent Hashing to partition data and lookup data, right? If so, will an ID be better than a string? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Tian Jiang 于2019年11月4日周一 下午7:00写道： > 1. Adding some entities may help us manage the metadata, while I don't > think mere renaming really helps much. > > > 2. I don't think PTree helps at all. I would suggest remove useless codes > as much as possible, unless real situations where it is needed are found. > Even so, a careful redesign is probably necessary and current > implementation does not seem to survive. > > > 3. Using string Ids does not induce too much overhead as far as I am > concerned, not to mention the cost of maintaining the bidirectional index. > > > On 11/4/2019 18:42，Jialin Qiao wrote： > Hi, > > 1. How about using sg, device, measurement directly in this module? (Or we > can provide interface named like these). > > About the name of "storage group", maybe SeriesGroup or database is better. > > 2. How do you think about the legacy attributes in the module called pTree > (property tree, which is actually like the tag in InfluxDB), remove it? or > introduce reverse index? > > pTree is a good properties, I suggest to reserve it. However, how to use > pTree and mTree simultaneously should be well defined by a PM :-) > > 3. Do we consider add a long id to each path? (is that helpful?) > > As far as I know, long id isn't helpful... maybe @Yanzhe An could give us > more detailed information. > > Best, > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学 软件学院 > > -原始邮件- > 发件人: "Xiangdong Huang" > 发送时间: 2019-11-04 15:45:45 (星期一) > 收件人: dev@iotdb.apache.org > 抄送: > 主题: Re: Working on refactoring metadata package > > Hi, > > Well I planed to do that actually, but I find I can not guarantee my > developing time.. So it is good to see that you want to do that. > > Yes we need to discuss about how to refactor. At least there are something > to do: > > 1. How about using sg, device, measurement directly in this module? (Or we > can provide interface named like these). > 2. How do you think about the legacy attributes in the module called pTree > (property tree, which is actually like the tag in InfluxDB), remove it? or > introduce reverse index? > 3. Do we consider add a long id to each path? (is that helpful?) > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Tian Jiang 于2019年11月4日周一 上午11:54写道： > > Greetings, > > > As you may know, the metadata package is the last package that is not > refactored compared with other packages. These codes are old and some are > poorly organized and may be inefficient. Nevertheless, new bloods are > coming in and such codes are uneasy for them to understand. So I plan to > refactor the metadata package in order to remove the unused or inefficient > codes. > > > I don't have a hard standard or rule. I will just see what I can do. And > I will check out a branch "refactor_metadata" for this. You are welcomed to > join this job and discuss in this thread what should be refactored and how. > > > Best, > Tian Jiang >
Re: Working on refactoring metadata package
Hi, Well I planed to do that actually, but I find I can not guarantee my developing time.. So it is good to see that you want to do that. Yes we need to discuss about how to refactor. At least there are something to do: 1. How about using sg, device, measurement directly in this module? (Or we can provide interface named like these). 2. How do you think about the legacy attributes in the module called pTree (property tree, which is actually like the tag in InfluxDB), remove it? or introduce reverse index? 3. Do we consider add a long id to each path? (is that helpful?) Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Tian Jiang 于2019年11月4日周一 上午11:54写道： > Greetings, > > > As you may know, the metadata package is the last package that is not > refactored compared with other packages. These codes are old and some are > poorly organized and may be inefficient. Nevertheless, new bloods are > coming in and such codes are uneasy for them to understand. So I plan to > refactor the metadata package in order to remove the unused or inefficient > codes. > > > I don't have a hard standard or rule. I will just see what I can do. And > I will check out a branch "refactor_metadata" for this. You are welcomed to > join this job and discuss in this thread what should be refactored and how. > > > Best, > Tian Jiang
Re: Is there anything needed to be developed now?
Hi, There is problem about the JIRA privilege... if you can not assign the issue to yourself, please leave a comment in that issue. So others will know that. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Boris Zhu 于2019年11月2日周六 下午1:27写道： > hi all, > Can we assign some issues in case some people do the same issues meantime? > I don't have the right to assign them. > best, > Boris > > On Sat, Nov 2, 2019 at 11:16 AM Jialin Qiao > wrote: > > > Hi Jack, > > > > Maybe this issue is suitable for you: > > > > https://issues.apache.org/jira/browse/IOTDB-279 > > > > Best, > > -- > > Jialin Qiao > > School of Software, Tsinghua University > > > > 乔嘉林 > > 清华大学 软件学院 > > > > > -原始邮件- > > > 发件人: "Jack Tsai" > > > 发送时间: 2019-11-01 09:01:45 (星期五) > > > 收件人: "dev@iotdb.apache.org" > > > 抄送: > > > 主题: Is there anything needed to be developed now? > > > > > > Hi, > > > > > > I have finished the function about querying timeseries and devices > > recently. It is glad to see that IoTDB keeps releasing new releases these > > days. > > > > > > Is there anything I could help now? Maybe implementing some functions > > that is needed for the next release. > > > > > > Best regards, > > > Jack Tsai > > >
A very simple example about using PLC4j and Edgent to collect data and then storing data into IoTDB
Hi, I finished a simple example to using plc4j and edgent to collect data and then storing the data into iotdb. It is a simple example, but just for showing how to use IoTDB and Plc4j together. Latter, I think I can do some integration with plc4j-opm with IoTDB. e.g., add a method in OPM entity called createIoTDBSchema() to create the schema in IoTDB according to the attributes of the entity. Then an example about using OPM and iotdb will be easy to be implemented. I have submit a PR to PLC4x project [1]. How do you think to submit it once again to IoTDB's repository? [1] https://github.com/apache/plc4x/pull/99 Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
