Hi,

I'm a little skeptical about the motivation for this feature.


If a large query really needs to take a long time to execute, is throwing an 
exception on the client side graceful?


For example, in some test scenarios, I would usually write hundreds of millions 
of points of data, and then perform `select count(*) from root grouy by level 
0` to verify that the insertion was successful. It usually executes for more 
than 20 minutes. If this feature is implemented, I can only get thrown 
exceptions when executing the query, what should I do then to verify the 
insertion?


Best
------------
Xinyu Tan

Reply via email to