[jira] [Commented] (IOTDB-533) tag 'latest' for IoTDB image in docker hub
[ https://issues.apache.org/jira/browse/IOTDB-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048837#comment-17048837 ] Xiangdong Huang commented on IOTDB-533: --- Hi [~LinYiming] many thanks. I have added the latest tag. Please enjoy it. > tag 'latest' for IoTDB image in docker hub > -- > > Key: IOTDB-533 > URL: https://issues.apache.org/jira/browse/IOTDB-533 > Project: Apache IoTDB > Issue Type: Improvement >Reporter: 林以明 >Priority: Minor > Labels: docker > Original Estimate: 1h > Remaining Estimate: 1h > > 'latest' tag of is missing in docker hub, which cause 'dokcer pull > apache/iotdb' fail if no version specified -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-533) tag 'latest' for IoTDB image in docker hub
林以明 created IOTDB-533: - Summary: tag 'latest' for IoTDB image in docker hub Key: IOTDB-533 URL: https://issues.apache.org/jira/browse/IOTDB-533 Project: Apache IoTDB Issue Type: Improvement Reporter: 林以明 'latest' tag of is missing in docker hub, which cause 'dokcer pull apache/iotdb' fail if no version specified -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-532) [Distributed] Enabling parallel processing within a data group
Tian Jiang created IOTDB-532: Summary: [Distributed] Enabling parallel processing within a data group Key: IOTDB-532 URL: https://issues.apache.org/jira/browse/IOTDB-532 Project: Apache IoTDB Issue Type: Improvement Reporter: Tian Jiang In the present implementation, the logs in a data group are executed serially which means for one data group, there is only one client that can be served at the same time. To increase concurrency, the data group should be able to process multiple client requests simultaneously. In order to do this, the following changes should be made: The log manager should be locked only when getting a new index. When a log is failed, the logs after it should also be removed. The internal retires should be added to overcome temporary network failure or the thread being switched out which causing the logs with larger index to arrive ahead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Podling Iotdb Report Reminder - March 2020
Hi, I have written a draft for this report. If there are no suggestions, I will paste the content to the wiki tonight. # IoTDB 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. # Three most important unfinished issues to address before graduating: 1. Get more user feedbacks to the community 2. More committers should know how to release a version. And more PPMC should join to vote. 3. make sure the private mailing list is consistent with the PPMC list. # Are there any issues that the IPMC or ASF Board need to be aware of? No. # How has the community developed since the last report? 1. According to the statistics of https://lists.apache.org/, there are 1079 emails sent by 87 people, divided into 564 topics in these 3 months. 2. 6 new committers are added into the community. 3. 5 GSoC2020 ideas are published. # How has the project developed since the last report? 1. IoTDB v0.9.1, which contains 11 bug-fix, was released on 11 Jan 2020. It is finished by the 4th RM in the community. 2. 124 Pull requests are merged 3. Now IoTDB docker images and Python client lib are available on dockerHub and pipy.org. # How would you assess the podling's maturity? Please feel free to add your own commentary. [ ] Initial setup [ ] Working towards first release [X] Community building [ ] Nearing graduation [ ] Other: # Date of last release: 2020-01-11 (v0.9.1) # When were the last committers or PPMC members elected? 2020-02-01 # Have your mentors been helpful and responsive? yes. # Are things falling through the cracks? If so, please list any open issues that need to be addressed. No. # 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? Required Name Search is done. A google search didn’t show any major branding issues that the PPMC needs to deal with. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 于2020年3月2日周一 上午4:10写道： > 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 March 2020, 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, March 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/March2020 > > Note: This is manually populated. You may need to wait a little before > this page is created from a template. > > Note: The format of the report has changed to use markdown. > > Mentors > --- > > Mentors should review reports for their project(s) and sign them off on > the Incubator wiki page. Signing off reports shows that you are > following the project - projects that are not signed may raise alarms > for the Incubator PMC. > > Incubator PMC >
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[ https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048669#comment-17048669 ] Julian Feinauer commented on IOTDB-528: --- [~hxd]I did a very first and very simple implementation. In the video attached you see the speed that I have in clicking around. I have one sample each second for the first 100 days of the year so it would take extremly long to show "this year so far" wighout my little optimization". [^autozoom.mov] > [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire > > > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Major > Labels: performance > Attachments: autozoom.mov > > > When using itodb-grafana integration through SimpleJson it seems like it does > not do any aggregation at all. > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Podling Iotdb Report Reminder - March 2020
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 March 2020, 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, March 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/March2020 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
[jira] [Commented] (IOTDB-530) GROUP BY does not allow timezone information in 2nd Parameter
[
https://issues.apache.org/jira/browse/IOTDB-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048607#comment-17048607
]
Xiangdong Huang commented on IOTDB-530:
---
Hi,
select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01 group
by (1d, 2020-01-01T00:00:00+1:00, [2020-01-01T00:00:00+01:00,
2020-03-01T23:59:00+01:00]
It seems your first TimeZone should be "+01:00", please have a try.
> GROUP BY does not allow timezone information in 2nd Parameter
> -
>
> Key: IOTDB-530
> URL: https://issues.apache.org/jira/browse/IOTDB-530
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Planner/SQLParser
>Reporter: Julian Feinauer
>Priority: Major
>
> I tried to issue the following command:
> {code:java}
> select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01
> group by (1d, 2020-01-01T00:00:00+1:00, [2020-01-01T00:00:00+01:00,
> 2020-03-01T23:59:00+01:00]{code}
> where I wanted to use the 2nd Paramter in Group By in my timezone (for the
> 3rd parameter it works), but it fails and tells me that I can only enter date
> (without Timezone).
> So instead I have to do smth like
> {code:java}
> select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01
> group by (1d, 2019-12-31T17:00:00, [2020-01-01T00:00:00+01:00,
> 2020-03-01T23:59:00+01:00])
> {code}
> which is rather ugly.
> So the fix would be to allow also to enter the 2nd Parameter as time + offset.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[
https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048606#comment-17048606
]
Julian Feinauer commented on IOTDB-528:
---
Yes, indeed I know. I already scratched one for grafana which works reasonably
well... but currently i try to have one that creates the snapshot also : )
{code:java}
FROM openjdk:11-jre-slim
LABEL maintainer="j.feina...@pragmaticminds.de"
RUN mkdir /iotdb
ADD application.properties /iotdb/
ADD iotdb-grafana-0.10.0-SNAPSHOT.war /iotdb/
EXPOSE
WORKDIR /iotdb/
ENTRYPOINT ["java", "-Dspring.datasource.url=jdbc:iotdb://${IOTDB_HOST}:6667",
"-jar", "/iotdb/iotdb-grafana-0.10.0-SNAPSHOT.war"]
{code}
> [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
>
>
> Key: IOTDB-528
> URL: https://issues.apache.org/jira/browse/IOTDB-528
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Connectors/Grafana
>Reporter: Julian Feinauer
>Priority: Major
> Labels: performance
>
> When using itodb-grafana integration through SimpleJson it seems like it does
> not do any aggregation at all.
> In situations where one selects a big time range it should do some
> subsampling with group by to limit the number of rows being sent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[ https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048605#comment-17048605 ] Xiangdong Huang commented on IOTDB-528: --- That could not be better! Notice that we have docker images on dockerhub for v0.9 and 0.9.1, but just for the server and the client. The grafana-connector is not included. > [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire > > > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Major > Labels: performance > > When using itodb-grafana integration through SimpleJson it seems like it does > not do any aggregation at all. > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[ https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048604#comment-17048604 ] Julian Feinauer commented on IOTDB-528: --- Hey [~hxd] no need to hurry. I will implement it myself (should not be too hard, I guess) and see how far I get. I'm also currently trying to prepare some docker containers to make it easier to use everything : ) > [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire > > > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Major > Labels: performance > > When using itodb-grafana integration through SimpleJson it seems like it does > not do any aggregation at all. > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[ https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048603#comment-17048603 ] Xiangdong Huang commented on IOTDB-528: --- OK, if we let users assign how many data points they can bear, I think it makes sense. Then we can calculate the time interval of the aggregation automatically. Do you want to use it in the tutorial tomorrow? If not, I can implement tomorrow. Otherwise, I have to do it tonight.. > [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire > > > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Major > Labels: performance > > When using itodb-grafana integration through SimpleJson it seems like it does > not do any aggregation at all. > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[ https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048602#comment-17048602 ] Julian Feinauer commented on IOTDB-528: --- Exactly, this is what I meant. E.g. we could say we limit to 1000 points. So we always chose the granularity in a way, that we have to transfer fewer than 1000 points. > [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire > > > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Major > Labels: performance > > When using itodb-grafana integration through SimpleJson it seems like it does > not do any aggregation at all. > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[ https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048599#comment-17048599 ] Xiangdong Huang commented on IOTDB-528: --- Hi julian, you mean that suppose we have a parameter called granularity, and granularity=5s, then we return the downsampling result no matter whether users want to read the raw data? > [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire > > > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Major > Labels: performance > > When using itodb-grafana integration through SimpleJson it seems like it does > not do any aggregation at all. > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-530) GROUP BY does not allow timezone information in 2nd Parameter
[
https://issues.apache.org/jira/browse/IOTDB-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048594#comment-17048594
]
Xiangdong Huang commented on IOTDB-530:
---
Hm, I read the source code on the master. The group by syntax is changed and
now it only supports the start time and end time [1]. And notice that the time
interval is like: [start, end), which means the end time is excluded.
[1] [http://iotdb.apache.org/#/Documents/0.9.x/chap5/sec2]
v0.9 uses antlr3. let me see whether I can fix it...
> GROUP BY does not allow timezone information in 2nd Parameter
> -
>
> Key: IOTDB-530
> URL: https://issues.apache.org/jira/browse/IOTDB-530
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Planner/SQLParser
>Reporter: Julian Feinauer
>Priority: Major
>
> I tried to issue the following command:
> {code:java}
> select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01
> group by (1d, 2020-01-01T00:00:00+1:00, [2020-01-01T00:00:00+01:00,
> 2020-03-01T23:59:00+01:00]{code}
> where I wanted to use the 2nd Paramter in Group By in my timezone (for the
> 3rd parameter it works), but it fails and tells me that I can only enter date
> (without Timezone).
> So instead I have to do smth like
> {code:java}
> select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01
> group by (1d, 2019-12-31T17:00:00, [2020-01-01T00:00:00+01:00,
> 2020-03-01T23:59:00+01:00])
> {code}
> which is rather ugly.
> So the fix would be to allow also to enter the 2nd Parameter as time + offset.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-531) iotdb-grafana does not take domain as host
[ https://issues.apache.org/jira/browse/IOTDB-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048590#comment-17048590 ] Xiangdong Huang commented on IOTDB-531: --- yes, it should throw meaningful exception. > iotdb-grafana does not take domain as host > -- > > Key: IOTDB-531 > URL: https://issues.apache.org/jira/browse/IOTDB-531 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Critical > > When customizing the application.properties for iotdb-grafana it needs an ip > + port as it does not work withn domain + port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-531) iotdb-grafana does not take domain as host
[ https://issues.apache.org/jira/browse/IOTDB-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048589#comment-17048589 ] Julian Feinauer commented on IOTDB-531: --- Yes, indeed. But the parser does not fail but silently produce wrong results as it seems. > iotdb-grafana does not take domain as host > -- > > Key: IOTDB-531 > URL: https://issues.apache.org/jira/browse/IOTDB-531 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Critical > > When customizing the application.properties for iotdb-grafana it needs an ip > + port as it does not work withn domain + port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-531) iotdb-grafana does not take domain as host
[ https://issues.apache.org/jira/browse/IOTDB-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048586#comment-17048586 ] Xiangdong Huang commented on IOTDB-531: --- Hi the URL prefix should be, "jdbc:iotdb://", you write it as "jdbc:iotdb//"... > iotdb-grafana does not take domain as host > -- > > Key: IOTDB-531 > URL: https://issues.apache.org/jira/browse/IOTDB-531 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Critical > > When customizing the application.properties for iotdb-grafana it needs an ip > + port as it does not work withn domain + port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-531) iotdb-grafana does not take domain as host
[ https://issues.apache.org/jira/browse/IOTDB-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048584#comment-17048584 ] Julian Feinauer commented on IOTDB-531: --- Oh, sry for the confusion. That was not the issue. The issue was that it was never checked if the String really starts with the prefix... I will prepare a PR for that. > iotdb-grafana does not take domain as host > -- > > Key: IOTDB-531 > URL: https://issues.apache.org/jira/browse/IOTDB-531 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Critical > > When customizing the application.properties for iotdb-grafana it needs an ip > + port as it does not work withn domain + port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-531) iotdb-grafana does not take domain as host
[
https://issues.apache.org/jira/browse/IOTDB-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048582#comment-17048582
]
Julian Feinauer commented on IOTDB-531:
---
[~hxd] I found the issue.
It seems like
Utils:43 which is
{code:java}
String subURL = url.substring(Config.IOTDB_URL_PREFIX.length());
{code}
has to be changed to
{code:java}
String subURL = url.substring(Config.IOTDB_URL_PREFIX.length() - 1);
{code}
to work sucessfull.
> iotdb-grafana does not take domain as host
> --
>
> Key: IOTDB-531
> URL: https://issues.apache.org/jira/browse/IOTDB-531
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Connectors/Grafana
>Reporter: Julian Feinauer
>Priority: Critical
>
> When customizing the application.properties for iotdb-grafana it needs an ip
> + port as it does not work withn domain + port.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-531) iotdb-grafana does not take domain as host
[ https://issues.apache.org/jira/browse/IOTDB-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048579#comment-17048579 ] Xiangdong Huang commented on IOTDB-531: --- Hi, which version you are using? 0.9.1? > iotdb-grafana does not take domain as host > -- > > Key: IOTDB-531 > URL: https://issues.apache.org/jira/browse/IOTDB-531 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Critical > > When customizing the application.properties for iotdb-grafana it needs an ip > + port as it does not work withn domain + port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[ https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048580#comment-17048580 ] Julian Feinauer commented on IOTDB-528: --- Hey [~hxd] , my simple idea was to have a fixed rule which performs a group by query depending on the time range (you get from SimpleJSON). We could also make this optional in the config. > [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire > > > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Major > Labels: performance > > When using itodb-grafana integration through SimpleJson it seems like it does > not do any aggregation at all. > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-531) iotdb-grafana does not take domain as host
[ https://issues.apache.org/jira/browse/IOTDB-531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048578#comment-17048578 ] Julian Feinauer commented on IOTDB-531: --- This seems to be an issue related to the Parsing in the iotdb jdbc driver, not only in grafana (see org.apache.iotdb.jdbc.Utils.java). > iotdb-grafana does not take domain as host > -- > > Key: IOTDB-531 > URL: https://issues.apache.org/jira/browse/IOTDB-531 > Project: Apache IoTDB > Issue Type: Bug > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Critical > > When customizing the application.properties for iotdb-grafana it needs an ip > + port as it does not work withn domain + port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-531) iotdb-grafana does not take domain as host
Julian Feinauer created IOTDB-531: - Summary: iotdb-grafana does not take domain as host Key: IOTDB-531 URL: https://issues.apache.org/jira/browse/IOTDB-531 Project: Apache IoTDB Issue Type: Bug Components: Connectors/Grafana Reporter: Julian Feinauer When customizing the application.properties for iotdb-grafana it needs an ip + port as it does not work withn domain + port. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
[ https://issues.apache.org/jira/browse/IOTDB-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048574#comment-17048574 ] Xiangdong Huang commented on IOTDB-528: --- Hi, It seems SimpleJSON does not support aggregation push-down[1]. Actually, we need a better Grafana connector implementation to solve this problem. [1] [https://grafana.com/grafana/plugins/grafana-simple-json-datasource] > [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire > > > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana >Reporter: Julian Feinauer >Priority: Major > Labels: performance > > When using itodb-grafana integration through SimpleJson it seems like it does > not do any aggregation at all. > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [jira] [Created] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
Hi, It seems SimpleJSON does not support aggregation push-down[1]. Actually, we need a better Grafana connector implementation to solve this problem. [1] https://grafana.com/grafana/plugins/grafana-simple-json-datasource Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer (Jira) 于2020年3月1日周日 下午9:04写道： > Julian Feinauer created IOTDB-528: > - > > Summary: [GRAFANA] Implicitly do GROUP BY to avoid sending to > many data over the wire > Key: IOTDB-528 > URL: https://issues.apache.org/jira/browse/IOTDB-528 > Project: Apache IoTDB > Issue Type: Improvement > Components: Connectors/Grafana > Reporter: Julian Feinauer > > > When using itodb-grafana integration through SimpleJson it seems like it > does not do any aggregation at all. > > In situations where one selects a big time range it should do some > subsampling with group by to limit the number of rows being sent. > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
[jira] [Commented] (IOTDB-530) GROUP BY does not allow timezone information in 2nd Parameter
[
https://issues.apache.org/jira/browse/IOTDB-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048569#comment-17048569
]
Xiangdong Huang commented on IOTDB-530:
---
Hi [~geniuspig] and [~qiaojialin], can you fix this quickly?
> GROUP BY does not allow timezone information in 2nd Parameter
> -
>
> Key: IOTDB-530
> URL: https://issues.apache.org/jira/browse/IOTDB-530
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Planner/SQLParser
>Reporter: Julian Feinauer
>Priority: Major
>
> I tried to issue the following command:
> {code:java}
> select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01
> group by (1d, 2020-01-01T00:00:00+1:00, [2020-01-01T00:00:00+01:00,
> 2020-03-01T23:59:00+01:00]{code}
> where I wanted to use the 2nd Paramter in Group By in my timezone (for the
> 3rd parameter it works), but it fails and tells me that I can only enter date
> (without Timezone).
> So instead I have to do smth like
> {code:java}
> select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01
> group by (1d, 2019-12-31T17:00:00, [2020-01-01T00:00:00+01:00,
> 2020-03-01T23:59:00+01:00])
> {code}
> which is rather ugly.
> So the fix would be to allow also to enter the 2nd Parameter as time + offset.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-530) GROUP BY does not allow timezone information in 2nd Parameter
Julian Feinauer created IOTDB-530:
-
Summary: GROUP BY does not allow timezone information in 2nd
Parameter
Key: IOTDB-530
URL: https://issues.apache.org/jira/browse/IOTDB-530
Project: Apache IoTDB
Issue Type: Bug
Components: Planner/SQLParser
Reporter: Julian Feinauer
I tried to issue the following command:
{code:java}
select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01 group
by (1d, 2020-01-01T00:00:00+1:00, [2020-01-01T00:00:00+01:00,
2020-03-01T23:59:00+01:00]{code}
where I wanted to use the 2nd Paramter in Group By in my timezone (for the 3rd
parameter it works), but it fails and tells me that I can only enter date
(without Timezone).
So instead I have to do smth like
{code:java}
select avg(counter), count(counter) from root.fabrik1.linie01.steuerung01 group
by (1d, 2019-12-31T17:00:00, [2020-01-01T00:00:00+01:00,
2020-03-01T23:59:00+01:00])
{code}
which is rather ugly.
So the fix would be to allow also to enter the 2nd Parameter as time + offset.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IOTDB-376) Metric module is not enabled when calling executeQueryStatement()
[
https://issues.apache.org/jira/browse/IOTDB-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17048564#comment-17048564
]
Yuxin Zhang commented on IOTDB-376:
---
hi, I've finished this issue in PR
[https://github.com/apache/incubator-iotdb/pull/863,] please have a look at it.
> Metric module is not enabled when calling executeQueryStatement()
> -
>
> Key: IOTDB-376
> URL: https://issues.apache.org/jira/browse/IOTDB-376
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 0.8.0, 0.9.0, 0.8.1, 0.8.2
>Reporter: Xiangdong Huang
>Priority: Major
> Labels: easy-fix, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The metric module can records at most 200 recent query sqls, using
> 127.0.0.1:8181 to access the module.
> However, it effects only when users call executeStatement().
> When users call executeQueryStatement(), the related module is not called to
> update the records.
> It is easy to fix, just copy some codes in executeStatement() method to
> executeQueryStatement():
> {code:java}
> // code placeholder
> sqlArgument = new SqlArgument(resp, physicalPlan, statement, startTime,
> endTime);
> sqlArgumentsList.add(sqlArgument);
> if (sqlArgumentsList.size() > MAX_SIZE) {
> sqlArgumentsList.subList(0, DELETE_SIZE).clear();
> }
> {code}
> Of course, put the above codes into a new function and let
> executeStatement() and executeQueryStatement() (and maybe some other
> functions) call the new function is a good choice.
>
> By the way, it is a good idea if we can set MAX_SIZE in the configuration
> file.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-529) Relative times and NOW() operator cannot be used in Group By
Julian Feinauer created IOTDB-529:
-
Summary: Relative times and NOW() operator cannot be used in Group
By
Key: IOTDB-529
URL: https://issues.apache.org/jira/browse/IOTDB-529
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Engine, Planner/SQLParser
Reporter: Julian Feinauer
When doing a group by query it is only possible to give absolute timestamps for
the group by window.
One woudl expect the following query to be valid
{code:java}
select min_value(counter), avg(counter), max_value(counter), count(counter)
from root.fabrik1.linie01.steuerung01 GROUP BY (1m, [NOW()-1h,NOW()]);
{code}
but it is not.
{color:#6a8759} {color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-528) [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire
Julian Feinauer created IOTDB-528: - Summary: [GRAFANA] Implicitly do GROUP BY to avoid sending to many data over the wire Key: IOTDB-528 URL: https://issues.apache.org/jira/browse/IOTDB-528 Project: Apache IoTDB Issue Type: Improvement Components: Connectors/Grafana Reporter: Julian Feinauer When using itodb-grafana integration through SimpleJson it seems like it does not do any aggregation at all. In situations where one selects a big time range it should do some subsampling with group by to limit the number of rows being sent. -- This message was sent by Atlassian Jira (v8.3.4#803005)
