??JDBCExample:??CentOS release 6.10 (Final) 8G
??500w??count??2000w??count
26lotDB??count 0.01??
import java.sql.*;
import java.text.ParseException;
import java.text.SimpleDateFormat;
import java.util.Date;
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
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
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
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
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
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
