[GitHub] [iotdb] ericpai edited a comment on pull request #4033: [IOTDB-1739] Constant timeseries generating functions

[GitBox <gi...@apache.org>]

ericpai edited a comment on pull request #4033:
URL: https://github.com/apache/iotdb/pull/4033#issuecomment-927450310


   > @ericpai Please take a look again :D
   
   The code is OK now. Here I have another one question about the design.
   
   _Does the result of wildcard path query of `const` function really satisfy user's actual requirement?_ 
   
      For example there're 2 timeseries root.sg.d1.s1, root.sg.d1.s2. And we have a query `SELECT const(*, type='int32', value='10') FROM root.sg.d1`.  In our logic, the function will be separated into two columns `const(root.sg.d1.s1, type='int32', 'value'='10')` and `const(root.sg.d1.s2, type='int32', 'value'='10')` right? But maybe a user wants to a single column with the union timestamps of all the measurements of `root.sg.d1`.  Moreover the user can't specify every timeseries in the parameters as there're so many ones.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org