Historical data from Ditto
Hi Iotdb developers, First short introduction: I met Julian Feinhauer and saw the talk about Apache IoTDB and then the following question came up: How can Apache IoTDB support the Histical data from Eclipse Ditto? This issue has been raised on Eclipse Ditto code repository: https://github.com/eclipse/ditto/issues/545 and i was wondering if there are plans to support this. As one of the developers already mentioned IoTDB as potential solution it would be awesome if IoTDB would provide a way to safe Historical Data of Ditto. Additionally https://stackoverflow.com/questions/56993884/how-to-get-historical-sensor-data-of-a-registered-hono-device Bosch IoT Suite seems to have an own way to safe historical data. Thanks in advance for your answers! Kind regards Lukas
AW: Historical data from Ditto
Hi Lukas, What a coincidence! Yesterday I met some of the ditto devs from Bosch and am currently thinking about exactly that! So let me familiarize a bit more with ditto then everything its possible! Julian Von meinem Mobiltelefon gesendet Ursprüngliche Nachricht Von: Lukas Ott Datum: Sa., 11. Jan. 2020, 13:36 An: dev@iotdb.apache.org Betreff: Historical data from Ditto Hi Iotdb developers, First short introduction: I met Julian Feinhauer and saw the talk about Apache IoTDB and then the following question came up: How can Apache IoTDB support the Histical data from Eclipse Ditto? This issue has been raised on Eclipse Ditto code repository: https://github.com/eclipse/ditto/issues/545 and i was wondering if there are plans to support this. As one of the developers already mentioned IoTDB as potential solution it would be awesome if IoTDB would provide a way to safe Historical Data of Ditto. Additionally https://stackoverflow.com/questions/56993884/how-to-get-historical-sensor-data-of-a-registered-hono-device Bosch IoT Suite seems to have an own way to safe historical data. Thanks in advance for your answers! Kind regards Lukas
Re: Historical data from Ditto
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 question for me would be the possibility to deploy Apache IoTDB on Kubernetes (including Keycloak Authentication -> That is already included in Eclipse Ditto) Lukas Am Sa., 11. Jan. 2020 um 13:41 Uhr schrieb Julian Feinauer < j.feina...@pragmaticminds.de>: > Hi Lukas, > > What a coincidence! > Yesterday I met some of the ditto devs from Bosch and am currently > thinking about exactly that! > > So let me familiarize a bit more with ditto then everything its possible! > > Julian > > Von meinem Mobiltelefon gesendet > > > Ursprüngliche Nachricht > Von: Lukas Ott > Datum: Sa., 11. Jan. 2020, 13:36 > An: dev@iotdb.apache.org > Betreff: Historical data from Ditto > Hi Iotdb developers, > > First short introduction: I met Julian Feinhauer and saw the talk about > Apache IoTDB and then the following question came up: How can Apache IoTDB > support the Histical data from Eclipse Ditto? > > This issue has been raised on Eclipse Ditto code repository: > https://github.com/eclipse/ditto/issues/545 and i was wondering if there > are plans to support this. As one of the developers already mentioned IoTDB > as potential solution it would be awesome if IoTDB would provide a way to > safe Historical Data of Ditto. > > Additionally > > https://stackoverflow.com/questions/56993884/how-to-get-historical-sensor-data-of-a-registered-hono-device > Bosch IoT Suite seems to have an own way to safe historical data. > > Thanks in advance for your answers! > > Kind regards > Lukas >
[Discussion] Whether to cache results in client？
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 spaces. I want to cache results in a client, and do you have another way? best wishes Boris
Re: Historical data from Ditto
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 have to use a network filesystem or run IoTDB on a certain node by force. As for the Keycloak Authentication, I also need time to familiarize with it.. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Lukas Ott 于2020年1月11日周六 下午8:46写道： > 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 question for me would be the possibility to deploy Apache > IoTDB on Kubernetes (including Keycloak Authentication -> That is already > included in Eclipse Ditto) > > Lukas > > Am Sa., 11. Jan. 2020 um 13:41 Uhr schrieb Julian Feinauer < > j.feina...@pragmaticminds.de>: > > > Hi Lukas, > > > > What a coincidence! > > Yesterday I met some of the ditto devs from Bosch and am currently > > thinking about exactly that! > > > > So let me familiarize a bit more with ditto then everything its possible! > > > > Julian > > > > Von meinem Mobiltelefon gesendet > > > > > > Ursprüngliche Nachricht > > Von: Lukas Ott > > Datum: Sa., 11. Jan. 2020, 13:36 > > An: dev@iotdb.apache.org > > Betreff: Historical data from Ditto > > Hi Iotdb developers, > > > > First short introduction: I met Julian Feinhauer and saw the talk about > > Apache IoTDB and then the following question came up: How can Apache > IoTDB > > support the Histical data from Eclipse Ditto? > > > > This issue has been raised on Eclipse Ditto code repository: > > https://github.com/eclipse/ditto/issues/545 and i was wondering if there > > are plans to support this. As one of the developers already mentioned > IoTDB > > as potential solution it would be awesome if IoTDB would provide a way to > > safe Historical Data of Ditto. > > > > Additionally > > > > > https://stackoverflow.com/questions/56993884/how-to-get-historical-sensor-data-of-a-registered-hono-device > > Bosch IoT Suite seems to have an own way to safe historical data. > > > > Thanks in advance for your answers! > > > > Kind regards > > Lukas > > >
Re: [Discussion] Whether to cache results in client？
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 loop may lead to a misaligned tab, but sounds it does not matter (you can even print the table header once again if a misaligned tab happens). Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Boris Zhu 于2020年1月11日周六 下午9:38写道： > 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 > spaces. I want to cache results in a client, and do you have another way? > > best wishes > Boris >
Re: Historical data from Ditto
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 to persist the data into IoTDB meanwhile. But if we want to provide high write performance (e.g., more than 10 million data points per second), we may need to use batch_write api, which is a little complex. Another thing that need to be discussed is that as ditto does not have api for query historical data. we have to design and add one. The third is, it sounds that Ditto does not require K8s and Keycloak Authentication. I quickly searched Keycloak and find it is a solution for Identity and Access Management. Hmm... IoTDB has a user/role management module, but does not support Keycloak... I think currently the community lacks committers to develop this feature. But we can create an issue about that, and maybe some familiar guys can do it. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2020年1月11日周六 下午10:05写道： > 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 have to use a network filesystem or run IoTDB on a certain node by > force. > > As for the Keycloak Authentication, I also need time to familiarize with > it.. > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Lukas Ott 于2020年1月11日周六 下午8:46写道： > >> 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 question for me would be the possibility to deploy Apache >> IoTDB on Kubernetes (including Keycloak Authentication -> That is already >> included in Eclipse Ditto) >> >> Lukas >> >> Am Sa., 11. Jan. 2020 um 13:41 Uhr schrieb Julian Feinauer < >> j.feina...@pragmaticminds.de>: >> >> > Hi Lukas, >> > >> > What a coincidence! >> > Yesterday I met some of the ditto devs from Bosch and am currently >> > thinking about exactly that! >> > >> > So let me familiarize a bit more with ditto then everything its >> possible! >> > >> > Julian >> > >> > Von meinem Mobiltelefon gesendet >> > >> > >> > Ursprüngliche Nachricht >> > Von: Lukas Ott >> > Datum: Sa., 11. Jan. 2020, 13:36 >> > An: dev@iotdb.apache.org >> > Betreff: Historical data from Ditto >> > Hi Iotdb developers, >> > >> > First short introduction: I met Julian Feinhauer and saw the talk about >> > Apache IoTDB and then the following question came up: How can Apache >> IoTDB >> > support the Histical data from Eclipse Ditto? >> > >> > This issue has been raised on Eclipse Ditto code repository: >> > https://github.com/eclipse/ditto/issues/545 and i was wondering if >> there >> > are plans to support this. As one of the developers already mentioned >> IoTDB >> > as potential solution it would be awesome if IoTDB would provide a way >> to >> > safe Historical Data of Ditto. >> > >> > Additionally >> > >> > >> https://stackoverflow.com/questions/56993884/how-to-get-historical-sensor-data-of-a-registered-hono-device >> > Bosch IoT Suite seems to have an own way to safe historical data. >> > >> > Thanks in advance for your answers! >> > >> > Kind regards >> > Lukas >> > >> >
[jira] [Created] (IOTDB-415) MetricService may start failed and leak a socket resource
Xiangdong Huang created IOTDB-415: - Summary: MetricService may start failed and leak a socket resource Key: IOTDB-415 URL: https://issues.apache.org/jira/browse/IOTDB-415 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.9.1, 0.9.0 Reporter: Xiangdong Huang Attachments: error.log Example: [https://travis-ci.org/apache/incubator-iotdb/jobs/635631638] Error log can be found in attachment. The reason analysis: The SocketServer starts successfully. But there is an exception in `server.join()`. Then `executorService.execute(new MetricsServiceThread(server));` throws a null pointer. Then IoTDB wants to quite but the socketserver is not closed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully
[ https://issues.apache.org/jira/browse/IOTDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013537#comment-17013537 ] Boris Zhu commented on IOTDB-414: - the correct syntax is compressor=SNAPPY instead of compression=SNAPPY. > Create Time series and show storage group Statements can not execute > successfully > -- > > Key: IOTDB-414 > URL: https://issues.apache.org/jira/browse/IOTDB-414 > Project: Apache IoTDB > Issue Type: Bug >Affects Versions: master branch >Reporter: Xiangdong Huang >Assignee: Boris Zhu >Priority: Major > > Hi, current master branch has some issues for executing some sqls. e.g.,: > > IoTDB> show timeseries; > show timeseries; > +-+-+-+-+-+ > | timeseries|storage group| dataType| encoding| compression| > +-+-+-+-+-+ > |root.sg1.d1.s1| root.sg1| INT64| RLE| SNAPPY| > |root.sg1.d1.s2| root.sg1| INT64| RLE| SNAPPY| > |root.sg1.d1.s3| root.sg1| INT64| RLE| SNAPPY| > +-+-+-+-+-+ > Total line number = 3 > It costs 0.006s > IoTDB> create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE, > compression=SNAPPY; > create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE, > compression=SNAPPY; > Msg: The resultDataType or encoding or compression of the last node s1 is > conflicting in the storage group root.sg1 > It costs 0.003s > IoTDB> show storage group; > show storage group; > Msg: column 2 does not exist > It costs 0.001s > # The create timeseries statement should be executed successfully. > # what is the problem of "show storage group"? > -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully
> 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, Tsinghua University 黄向东 清华大学 软件学院 Boris Zhu (Jira) 于2020年1月12日周日 上午12:39写道： > > [ > https://issues.apache.org/jira/browse/IOTDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013537#comment-17013537 > ] > > Boris Zhu commented on IOTDB-414: > - > > the correct syntax is compressor=SNAPPY instead of compression=SNAPPY. > > > > > Create Time series and show storage group Statements can not execute > successfully > > > -- > > > > Key: IOTDB-414 > > URL: https://issues.apache.org/jira/browse/IOTDB-414 > > Project: Apache IoTDB > > Issue Type: Bug > >Affects Versions: master branch > >Reporter: Xiangdong Huang > >Assignee: Boris Zhu > >Priority: Major > > > > Hi, current master branch has some issues for executing some sqls. e.g.,: > > > > IoTDB> show timeseries; > > show timeseries; > > +-+-+-+-+-+ > > | timeseries|storage group| dataType| encoding| compression| > > +-+-+-+-+-+ > > |root.sg1.d1.s1| root.sg1| INT64| RLE| SNAPPY| > > |root.sg1.d1.s2| root.sg1| INT64| RLE| SNAPPY| > > |root.sg1.d1.s3| root.sg1| INT64| RLE| SNAPPY| > > +-+-+-+-+-+ > > Total line number = 3 > > It costs 0.006s > > IoTDB> create timeseries root.sg1.d2.s1 with datatype=INT64, > encoding=RLE, compression=SNAPPY; > > create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE, > compression=SNAPPY; > > Msg: The resultDataType or encoding or compression of the last node s1 > is conflicting in the storage group root.sg1 > > It costs 0.003s > > IoTDB> show storage group; > > show storage group; > > Msg: column 2 does not exist > > It costs 0.001s > > # The create timeseries statement should be executed successfully. > > # what is the problem of "show storage group"? > > > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
Re: [jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully
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 last node s1 is conflicting in the storage group root.sg1" ... > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Boris Zhu (Jira) 于2020年1月12日周日 上午12:39写道： > > > > > [ > > > https://issues.apache.org/jira/browse/IOTDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013537#comment-17013537 > > ] > > > > Boris Zhu commented on IOTDB-414: > > - > > > > the correct syntax is compressor=SNAPPY instead of compression=SNAPPY. > > > > > > > > > Create Time series and show storage group Statements can not execute > > successfully > > > > > > -- > > > > > > Key: IOTDB-414 > > > URL: https://issues.apache.org/jira/browse/IOTDB-414 > > > Project: Apache IoTDB > > > Issue Type: Bug > > >Affects Versions: master branch > > >Reporter: Xiangdong Huang > > >Assignee: Boris Zhu > > >Priority: Major > > > > > > Hi, current master branch has some issues for executing some sqls. > e.g.,: > > > > > > IoTDB> show timeseries; > > > show timeseries; > > > +-+-+-+-+-+ > > > | timeseries|storage group| dataType| encoding| compression| > > > +-+-+-+-+-+ > > > |root.sg1.d1.s1| root.sg1| INT64| RLE| SNAPPY| > > > |root.sg1.d1.s2| root.sg1| INT64| RLE| SNAPPY| > > > |root.sg1.d1.s3| root.sg1| INT64| RLE| SNAPPY| > > > +-+-+-+-+-+ > > > Total line number = 3 > > > It costs 0.006s > > > IoTDB> create timeseries root.sg1.d2.s1 with datatype=INT64, > > encoding=RLE, compression=SNAPPY; > > > create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE, > > compression=SNAPPY; > > > Msg: The resultDataType or encoding or compression of the last node s1 > > is conflicting in the storage group root.sg1 > > > It costs 0.003s > > > IoTDB> show storage group; > > > show storage group; > > > Msg: column 2 does not exist > > > It costs 0.001s > > > # The create timeseries statement should be executed successfully. > > > # what is the problem of "show storage group"? > > > > > > > > > > > -- > > This message was sent by Atlassian Jira > > (v8.3.4#803005) > > >
Re: [jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully
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 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 last node s1 is conflicting in the storage group root.sg1" ... >> >> Best, >> --- >> Xiangdong Huang >> School of Software, Tsinghua University >> >> 黄向东 >> 清华大学 软件学院 >> >> >> Boris Zhu (Jira) 于2020年1月12日周日 上午12:39写道： >> >> > >> > [ >> > >> https://issues.apache.org/jira/browse/IOTDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013537#comment-17013537 >> > ] >> > >> > Boris Zhu commented on IOTDB-414: >> > - >> > >> > the correct syntax is compressor=SNAPPY instead of compression=SNAPPY. >> > >> > >> > >> > > Create Time series and show storage group Statements can not execute >> > successfully >> > > >> > >> -- >> > > >> > > Key: IOTDB-414 >> > > URL: https://issues.apache.org/jira/browse/IOTDB-414 >> > > Project: Apache IoTDB >> > > Issue Type: Bug >> > >Affects Versions: master branch >> > >Reporter: Xiangdong Huang >> > >Assignee: Boris Zhu >> > >Priority: Major >> > > >> > > Hi, current master branch has some issues for executing some sqls. >> e.g.,: >> > > >> > > IoTDB> show timeseries; >> > > show timeseries; >> > > >> +-+-+-+-+-+ >> > > | timeseries|storage group| dataType| encoding| compression| >> > > >> +-+-+-+-+-+ >> > > |root.sg1.d1.s1| root.sg1| INT64| RLE| SNAPPY| >> > > |root.sg1.d1.s2| root.sg1| INT64| RLE| SNAPPY| >> > > |root.sg1.d1.s3| root.sg1| INT64| RLE| SNAPPY| >> > > >> +-+-+-+-+-+ >> > > Total line number = 3 >> > > It costs 0.006s >> > > IoTDB> create timeseries root.sg1.d2.s1 with datatype=INT64, >> > encoding=RLE, compression=SNAPPY; >> > > create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE, >> > compression=SNAPPY; >> > > Msg: The resultDataType or encoding or compression of the last node s1 >> > is conflicting in the storage group root.sg1 >> > > It costs 0.003s >> > > IoTDB> show storage group; >> > > show storage group; >> > > Msg: column 2 does not exist >> > > It costs 0.001s >> > > # The create timeseries statement should be executed successfully. >> > > # what is the problem of "show storage group"? >> > > >> > >> > >> > >> > -- >> > This message was sent by Atlassian Jira >> > (v8.3.4#803005) >> > >> >
Re: [jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully
Hi, It's not two totally the same time series, one is d1, another is d2. Boris Zhu 于2020年1月12日周日 上午12:52写道： > 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 last node s1 is conflicting in the storage group root.sg1" ... > > > > Best, > > --- > > Xiangdong Huang > > School of Software, Tsinghua University > > > > 黄向东 > > 清华大学 软件学院 > > > > > > Boris Zhu (Jira) 于2020年1月12日周日 上午12:39写道： > > > > > > > > [ > > > > > > https://issues.apache.org/jira/browse/IOTDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013537#comment-17013537 > > > ] > > > > > > Boris Zhu commented on IOTDB-414: > > > - > > > > > > the correct syntax is compressor=SNAPPY instead of compression=SNAPPY. > > > > > > > > > > > > > Create Time series and show storage group Statements can not execute > > > successfully > > > > > > > > > > -- > > > > > > > > Key: IOTDB-414 > > > > URL: https://issues.apache.org/jira/browse/IOTDB-414 > > > > Project: Apache IoTDB > > > > Issue Type: Bug > > > >Affects Versions: master branch > > > >Reporter: Xiangdong Huang > > > >Assignee: Boris Zhu > > > >Priority: Major > > > > > > > > Hi, current master branch has some issues for executing some sqls. > > e.g.,: > > > > > > > > IoTDB> show timeseries; > > > > show timeseries; > > > > > +-+-+-+-+-+ > > > > | timeseries|storage group| dataType| encoding| compression| > > > > > +-+-+-+-+-+ > > > > |root.sg1.d1.s1| root.sg1| INT64| RLE| SNAPPY| > > > > |root.sg1.d1.s2| root.sg1| INT64| RLE| SNAPPY| > > > > |root.sg1.d1.s3| root.sg1| INT64| RLE| SNAPPY| > > > > > +-+-+-+-+-+ > > > > Total line number = 3 > > > > It costs 0.006s > > > > IoTDB> create timeseries root.sg1.d2.s1 with datatype=INT64, > > > encoding=RLE, compression=SNAPPY; > > > > create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE, > > > compression=SNAPPY; > > > > Msg: The resultDataType or encoding or compression of the last node > s1 > > > is conflicting in the storage group root.sg1 > > > > It costs 0.003s > > > > IoTDB> show storage group; > > > > show storage group; > > > > Msg: column 2 does not exist > > > > It costs 0.001s > > > > # The create timeseries statement should be executed successfully. > > > > # what is the problem of "show storage group"? > > > > > > > > > > > > > > > > -- > > > This message was sent by Atlassian Jira > > > (v8.3.4#803005) > > > > > > -- — Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院
[jira] [Commented] (IOTDB-414) Create Time series and show storage group Statements can not execute successfully
[
https://issues.apache.org/jira/browse/IOTDB-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17013630#comment-17013630
]
Yuan Tian commented on IOTDB-414:
-
I do the same thing on the master branch, the create timeseries statement is
actually executed successfully.
{code:java}
create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE,
compression=SNAPPY;{code}
and I use
compression=SNAPPY not compressor=SNAPPY, I don't know what's the difference
between them
> Create Time series and show storage group Statements can not execute
> successfully
> --
>
> Key: IOTDB-414
> URL: https://issues.apache.org/jira/browse/IOTDB-414
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: master branch
>Reporter: Xiangdong Huang
>Assignee: Boris Zhu
>Priority: Major
>
> Hi, current master branch has some issues for executing some sqls. e.g.,:
>
> IoTDB> show timeseries;
> show timeseries;
> +-+-+-+-+-+
> | timeseries|storage group| dataType| encoding| compression|
> +-+-+-+-+-+
> |root.sg1.d1.s1| root.sg1| INT64| RLE| SNAPPY|
> |root.sg1.d1.s2| root.sg1| INT64| RLE| SNAPPY|
> |root.sg1.d1.s3| root.sg1| INT64| RLE| SNAPPY|
> +-+-+-+-+-+
> Total line number = 3
> It costs 0.006s
> IoTDB> create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE,
> compression=SNAPPY;
> create timeseries root.sg1.d2.s1 with datatype=INT64, encoding=RLE,
> compression=SNAPPY;
> Msg: The resultDataType or encoding or compression of the last node s1 is
> conflicting in the storage group root.sg1
> It costs 0.003s
> IoTDB> show storage group;
> show storage group;
> Msg: column 2 does not exist
> It costs 0.001s
> # The create timeseries statement should be executed successfully.
> # what is the problem of "show storage group"?
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
