[jira] [Closed] (IOTDB-203) A new result set format

2019-10-22 Thread Jialin Qiao (Jira)
[ https://issues.apache.org/jira/browse/IOTDB-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jialin Qiao closed IOTDB-203. - Fix Version/s: 0.9.0 Resolution: Fixed > A new result set for

Re: A new result set format

2019-10-06 Thread Lei Rui
gn Details # REALIZATION OF GROUP BY DEVICE - Code Realization # USER GUIDANCE OF GROUP BY DEVICE # ORIGINAL DEMANDS 1. As stated in JIRA IOTDB-203 and discussed in this email thread, a new result set format / narrow table / group by device 2. filter the devices using regular expression. For example

Re: A new result set format

2019-09-07 Thread Julian Feinauer
ian > > Am 07.09.19, 04:29 schrieb "Jialin Qiao" : > > Hi, > > As described in this issue, a new result set format is wanted by users. I'd like to open a discussion here. > > For simplicity, I refer this format "time, root

A new result set format

2019-09-07 Thread Xiangdong Huang
t; > Lastly, I think the better query execution efficiency that a narrow table > may sometimes has is not the drive purpose, > because presenting the query result in a wide table and in a narrow table > are two different tasks. > > > Sincerely, > Lei Rui > > > Fro

Re: A new result set format

2019-09-07 Thread Rui, Lei
a narrow table may sometimes has is not the drive purpose, because presenting the query result in a wide table and in a narrow table are two different tasks. Sincerely, Lei Rui From: Jialin Qiao Date: 9/7/2019 15:26 To: Subject: Re: A new result set format Hi Julian, He is my friend

Re: A new result set format

2019-09-07 Thread Rui, Lei
1" with a narrow table format? Lastly, I think the better query execution efficiency that a narrow table may sometimes has is not the drive purpose, because presenting the query result in a wide table and in a narrow table are two different tasks. Sincerely, Lei Rui From: Jialin Qiao Dat

Re: A new result set format

2019-09-07 Thread Rui, Lei
e better query execution efficiency that a narrow table may sometimes has is not the drive purpose, because presenting the query result in a wide table and in a narrow table are two different tasks. Sincerely, Lei Rui From: Jialin Qiao Date: 9/7/2019 15:26 To: Subject: Re: A new result set

Re: A new result set format

2019-09-07 Thread Jialin Qiao
t; 发件人: "Julian Feinauer" > 发送时间: 2019-09-07 13:52:17 (星期六) > 收件人: "dev@iotdb.apache.org" > 抄送: > 主题: Re: A new result set format > > Hi Jialin, > > perhaps one question about "wanted by users" means (as I didn’t see anything > on the l

Re: A new result set format

2019-09-06 Thread Julian Feinauer
Hi Jialin, perhaps one question about "wanted by users" means (as I didn’t see anything on the list). How do these users get in contact with you? Julian Am 07.09.19, 04:29 schrieb "Jialin Qiao" : Hi, As described in this issue, a new result set format is

A new result set format

2019-09-06 Thread Jialin Qiao
Hi, As described in this issue, a new result set format is wanted by users. I'd like to open a discussion here. For simplicity, I refer this format "time, root.sg1.d1.s1, root.sg1.d2.s1" to wide table, and "time, deviceId, s1" as narrow table. This issue is not only a

[jira] [Created] (IOTDB-203) A new result set format

2019-09-06 Thread Jialin Qiao (Jira)
Jialin Qiao created IOTDB-203: - Summary: A new result set format Key: IOTDB-203 URL: https://issues.apache.org/jira/browse/IOTDB-203 Project: Apache IoTDB Issue Type: New Feature