[jira] [Closed] (IOTDB-379) website error
[ https://issues.apache.org/jira/browse/IOTDB-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-379. - Resolution: Won't Fix Hi, this issue has been forwarded to apache incubator. > website error > - > > Key: IOTDB-379 > URL: https://issues.apache.org/jira/browse/IOTDB-379 > Project: Apache IoTDB > Issue Type: Bug >Reporter: localhost >Priority: Trivial > > 1.open [http://incubator.apache.org/projects/iotdb.html] > 2.click [Incubation Guides|http://incubator.apache.org/policy/process.html] > see error -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IOTDB-525) Memory size of MemTable is added wrongly when executing batch insertion
[ https://issues.apache.org/jira/browse/IOTDB-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-525. - Fix Version/s: 0.10.0-SNAPSHOT Resolution: Fixed > Memory size of MemTable is added wrongly when executing batch insertion > --- > > Key: IOTDB-525 > URL: https://issues.apache.org/jira/browse/IOTDB-525 > Project: Apache IoTDB > Issue Type: Bug >Reporter: Yanzhe An >Priority: Major > Labels: pull-request-available > Fix For: 0.10.0-SNAPSHOT > > Time Spent: 20m > Remaining Estimate: 0h > > I found that when inserting *part* of a BatchInsertPlan which starts at *i* > and ends at *j* into a MemTable, the *whole* memory size of the > BatchInsertPlan will be added to the *memSize* of the MemTable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IOTDB-512) select count(*) no response
[
https://issues.apache.org/jira/browse/IOTDB-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jialin Qiao closed IOTDB-512.
-
Fix Version/s: 0.10.0-SNAPSHOT
Resolution: Fixed
> select count(*) no response
>
>
> Key: IOTDB-512
> URL: https://issues.apache.org/jira/browse/IOTDB-512
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Client/Java
>Reporter: FengQingxin
>Priority: Major
> Labels: pull-request-available
> Fix For: 0.10.0-SNAPSHOT
>
> Attachments: image-2020-02-24-16-50-07-639.png,
> image-2020-02-24-16-51-26-238.png, log_error.log
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Hello IoTDB Developers:
> When I using [select count(*) from root.*.*] in iotdb-cli, I got an error
> message like : {color:#FF}OutOfMemoryError: Java heap space{color}.
> IoTDB version: apache/iotdb master : 59cba45b28046264330aaedbab609590404f95af
> Data schema: SG=10；Device=50；Sensor=100；Points=100; Overflow:10%
> 11G ./sequence
> 1.2G ./unsequence
> 12G
>
> Please help me to check this issue.Thanks.
> B.R
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-479) JMX connection failed
[ https://issues.apache.org/jira/browse/IOTDB-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046581#comment-17046581 ] Jialin Qiao commented on IOTDB-479: --- If users meet this problem, the quick start record how to resolve. > JMX connection failed > - > > Key: IOTDB-479 > URL: https://issues.apache.org/jira/browse/IOTDB-479 > Project: Apache IoTDB > Issue Type: Bug > Components: Others >Affects Versions: 0.10.0-SNAPSHOT >Reporter: Xiangdong Huang >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Hi, > I find a case that the server has bind JMX port successfully after IoTDB > startup and the bind IP is also correct. (using `lsof -i:31999` to check.) > However, the user can not connect to the server using Jconsole or JvisualVM. > This issue usually happens when the server has more than one IP. > I tried several solutions and think the following may be useful: > add `-Dcom.sun.management.jmxremote.rmi.port=THE PORT` and > `-Djava.rmi.server.hostname=THE IP` to $IOTDB_JMX_OPTS in iotdb-env.sh. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IOTDB-479) JMX connection failed
[ https://issues.apache.org/jira/browse/IOTDB-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-479. - Resolution: Won't Fix > JMX connection failed > - > > Key: IOTDB-479 > URL: https://issues.apache.org/jira/browse/IOTDB-479 > Project: Apache IoTDB > Issue Type: Bug > Components: Others >Affects Versions: 0.10.0-SNAPSHOT >Reporter: Xiangdong Huang >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Hi, > I find a case that the server has bind JMX port successfully after IoTDB > startup and the bind IP is also correct. (using `lsof -i:31999` to check.) > However, the user can not connect to the server using Jconsole or JvisualVM. > This issue usually happens when the server has more than one IP. > I tried several solutions and think the following may be useful: > add `-Dcom.sun.management.jmxremote.rmi.port=THE PORT` and > `-Djava.rmi.server.hostname=THE IP` to $IOTDB_JMX_OPTS in iotdb-env.sh. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IOTDB-328) Check the validity of settings in configuration files when restart and upgrade
[ https://issues.apache.org/jira/browse/IOTDB-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-328. - Fix Version/s: 0.10.0-SNAPSHOT Resolution: Fixed > 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 >Priority: Major > Labels: easyfix > Fix For: 0.10.0-SNAPSHOT > > > 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)
[jira] [Commented] (IOTDB-380) Questions about asterisks in storage group or time series paths
[ https://issues.apache.org/jira/browse/IOTDB-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046656#comment-17046656 ] Jialin Qiao commented on IOTDB-380: --- Hi, setting storage group and create timeseries should share the same path definition that does not contain *. > Questions about asterisks in storage group or time series paths > --- > > Key: IOTDB-380 > URL: https://issues.apache.org/jira/browse/IOTDB-380 > Project: Apache IoTDB > Issue Type: Bug >Reporter: chenzhengwei >Priority: Major > > version : 0.9.0 > System : windows > scenario one: > 1, set storage group to root.ed do success > 2, create timeseries root.ed.*.cpu with datatype=INT32,encoding=RLE > 3, exception : > Msg: Statement format is not right: Parsing error, statement > [create timeseries root.ed.*.cpu with datatype=INT32,encoding=RLE] failed > when parsing AST tree to generate logical operator. Detailed information: > [line 1:32 mismatched input '*' expecting set null] > > scenario two: > 1, `set storage group to root.ed.* ` **** **** > or `set storage group to root.ed.*.xx ` > do success > 2, create timeseries root.ed.fc02.abc with datatype=INT32,encoding=RLE > or > create timeseries root.ed.fc02.xx with datatype=INT32,encoding=RLE > 3, exception: Msg: The seriesPath of [root.ed] already exist, it can't > be set to the storage group > > * Now I don't know how to use the * in the path. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
??????[jira] [Commented] (IOTDB-380) Questions about asterisks in storage group or time series paths
Hi, I'm fixing this issue, the PR is https://github.com/apache/incubator-iotdb/pull/853 Thanks, Yuxin Zhang -- -- ??: "Jialin Qiao (Jira)"https://issues.apache.org/jira/browse/IOTDB-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046656#comment-17046656 ] Jialin Qiao commented on IOTDB-380: --- Hi, setting storage group and create timeseries should share the same path definition that does not contain *. > Questions about asterisks in storage group or time series paths > --- > > Key: IOTDB-380 > URL: https://issues.apache.org/jira/browse/IOTDB-380 > Project: Apache IoTDB > Issue Type: Bug > Reporter: chenzhengwei > Priority: Major > > version : 0.9.0 > System : windows > scenario one: > 1, set storage group to root.ed do success > 2, create timeseries root.ed.*.cpu with datatype=INT32,encoding=RLE > 3, exception : > Msg: Statement format is not right: Parsing error, statement [create timeseries root.ed.*.cpu with datatype=INT32,encoding=RLE] failed when parsing AST tree to generate logical operator. Detailed information: [line 1:32 mismatched input '*' expecting set null] > > scenario two: > 1, `set storage group to root.ed.* ` **** **** > or `set storage group to root.ed.*.xx ` > do success > 2, create timeseries root.ed.fc02.abc with datatype=INT32,encoding=RLE > or > create timeseries root.ed.fc02.xx with datatype=INT32,encoding=RLE > 3, exception: Msg: The seriesPath of [root.ed] already exist, it can't be set to the storage group > > * Now I don't know how to use the * in the path. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Camel JDBC
Hello, I am new here and wanted to use IoTDB to put data from a PLC into a DB. I already managed some good results with plc4x, but I wanted to ask if there are any example of using IoTDB with Camel, as I am already using it for plc4x. Regards, Etienne
[jira] [Created] (IOTDB-526) [Distributed]Support metadata queries
Tian Jiang created IOTDB-526: Summary: [Distributed]Support metadata queries Key: IOTDB-526 URL: https://issues.apache.org/jira/browse/IOTDB-526 Project: Apache IoTDB Issue Type: Improvement Reporter: Tian Jiang Assignee: Tian Jiang Fix For: master branch Metadata queries, like "getNodeList", "getPathNextChildern", "getTimeseriesSchema" are currently unsupported. The point is that the paths being queried may contain wildcards(*) or they may be prefix paths, which makes it a little hard to figure out which data groups to send the query. The simplest way may be performing a broadcast and merge the results, which is clearly less efficient. I am hoping you can give a more brilliant idea to resolve this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Camel JDBC
Hi Etienne, Currently there isn't an existing example for Camel. I'm not familiar with Camel, but I think the IoTDB client could be easily integrated with Camel as a new processor or consumer. There is an example in PLC4X that integrates with IoTDB [1]. Also in IoTDB there are examples for kafka, rocketmq and IoTDB java clients (JDBC and Native API Session) [2], hope these may help you. If possible, welcome to contribute an example for Camel :) [1] https://github.com/apache/plc4x/tree/2406877695308ad177924b0fadc026489a10a8e6/plc4j/examples/hello-integration-iotdb [2] https://github.com/apache/incubator-iotdb/tree/master/example Thanks, -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Etienne Robinet" <43...@etu.he2b.be> > 发送时间: 2020-02-28 00:41:21 (星期五) > 收件人: dev@iotdb.apache.org > 抄送: > 主题: Camel JDBC > > Hello, > I am new here and wanted to use IoTDB to put data from a PLC into a DB. I > already managed some good results with plc4x, but I wanted to ask if there > are any example of using IoTDB with Camel, as I am already using it for plc4x. > Regards, > > Etienne
[BUILD-STABLE]: Job 'IoTDB-Pipeline/master [master] [281]'
BUILD-STABLE: Job 'IoTDB-Pipeline/master [master] [281]': Is back to normal.
[jira] [Closed] (IOTDB-380) Questions about asterisks in storage group or time series paths
[ https://issues.apache.org/jira/browse/IOTDB-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-380. - Fix Version/s: 0.10.0-SNAPSHOT Resolution: Fixed > Questions about asterisks in storage group or time series paths > --- > > Key: IOTDB-380 > URL: https://issues.apache.org/jira/browse/IOTDB-380 > Project: Apache IoTDB > Issue Type: Bug >Reporter: chenzhengwei >Assignee: Yuxin Zhang >Priority: Major > Labels: pull-request-available > Fix For: 0.10.0-SNAPSHOT > > Time Spent: 20m > Remaining Estimate: 0h > > version : 0.9.0 > System : windows > scenario one: > 1, set storage group to root.ed do success > 2, create timeseries root.ed.*.cpu with datatype=INT32,encoding=RLE > 3, exception : > Msg: Statement format is not right: Parsing error, statement > [create timeseries root.ed.*.cpu with datatype=INT32,encoding=RLE] failed > when parsing AST tree to generate logical operator. Detailed information: > [line 1:32 mismatched input '*' expecting set null] > > scenario two: > 1, `set storage group to root.ed.* ` **** **** > or `set storage group to root.ed.*.xx ` > do success > 2, create timeseries root.ed.fc02.abc with datatype=INT32,encoding=RLE > or > create timeseries root.ed.fc02.xx with datatype=INT32,encoding=RLE > 3, exception: Msg: The seriesPath of [root.ed] already exist, it can't > be set to the storage group > > * Now I don't know how to use the * in the path. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
