[jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully

2020-01-11 Thread Yuan Tian (Jira)
[ https://issues.apache.org/jira/browse/IOTDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17013630#comment-17013630 ] Yuan Tian commented on IOTDB-414: - I do the same thing on the master branch,  the create timeseries

Re: [jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully

2020-01-11 Thread Boris Zhu
because of the wrong syntax, `create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE, compression=SNAPPY` is equal to `create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE, compressor=UNCOMPRESSED` On Sun, Jan 12, 2020 at 12:51 AM Boris Zhu wrote: > Why create two

Re: [jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully

2020-01-11 Thread Boris Zhu
Why create two totally same time series? you mean error message isn't correct? On Sun, Jan 12, 2020 at 12:40 AM Xiangdong Huang wrote: > > the correct syntax is compressor=SNAPPY instead of compression=SNAPPY. > > But the error message is "The resultDataType or encoding or compression of > the

Re: [jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully

2020-01-11 Thread Xiangdong Huang
> the correct syntax is compressor=SNAPPY instead of compression=SNAPPY. But the error message is "The resultDataType or encoding or compression of the last node s1 is conflicting in the storage group root.sg1" ... Best, --- Xiangdong Huang School of Software,

[jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully

2020-01-11 Thread Boris Zhu (Jira)
[ https://issues.apache.org/jira/browse/IOTDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17013537#comment-17013537 ] Boris Zhu commented on IOTDB-414: - the correct syntax is compressor=SNAPPY instead of compression=SNAPPY.

Re: Historical data from Ditto

2020-01-11 Thread Xiangdong Huang
Hi, I have quickly read the document of Ditto. In my understanding, Ditto allow consume data from kafka or MQTT server to get the latest status of a Things (or, a device), and provides API to let users know the latest value of a device's feature (measurement concept in IoTDB). I think it is easy

Re: [Discussion] Whether to cache results in client?

2020-01-11 Thread Xiangdong Huang
Hi, if it is just for CLI, it is ok. but be cautious that do not out of memory. And do not do it in JDBC or thrift client module. in my opinion, we can cache some lines (e.g., 100lines), calculate the suitable blank space, and print the 100 lines, and then cache another 100 lines... Different

Re: Historical data from Ditto

2020-01-11 Thread Xiangdong Huang
Hi, Thanks Lukas. I also need to take some time to familiarize with Ditto. :-) > One important question for me would be the possibility to deploy Apache IoTDB on Kubernetes Now we can deploy IoTDB as a docker container. So I think it is ok to deploy it on K8S. But as it is a database, you may

[Discussion] Whether to cache results in client?

2020-01-11 Thread Boris Zhu
Hi, The client get results by rows instead of columns. So it's difficult to align results in one displayed table because we don't know the longest result in one column. The original method is to set a very long fixed length for a column. Obviously, the above method will cause unnecessary

Re: Historical data from Ditto

2020-01-11 Thread Lukas Ott
Hi Julian, Great to hear from you. Just for information I was active on https://gitter.im/eclipse/ditto and raised same issues on stackoverflow (ended up in a mini PR for Ditto concerning Kubernetes API break) So lets see how we can bring these two systems closer together. :) One important