alvin
alvin
@kaijianding I want to discuss a little more on the return of this statement. What will be returned when there is a query killed? What will be returned when there...
> > What will be returned when there is a query killed? > `ERROR 1064 (HY000) at line 2: killed by kill statement : OriginStatement{originStmt='kill query 'aaa'', idx=0}` IMO we...
@kaijianding Because you are introducing a new statement, it would need to be discussed more before we merge it into the code base. StarRocks already has `query_id` for each query,...
> KILL QUERY conn_id|query_id Can you confirm that StarRocks has already supported it now? AFAIK, it hasn't supported kill query by query_id. As you can see in the [KILL](https://docs.starrocks.io/docs/sql-reference/sql-statements/Administration/KILL/) doc,...
> Because user want to kill a query from his own code if a query is taking too long time or user just want to cancel the query due to...
@liubotao Thanks for the issue ticket. I know that you have created a PR to implement this feature so I have some questions about it. first, can you make the...
@liubotao In many user environments, the backend or compute nodes are not exposed to the end clients. So if a client only can fetch results from BE/CN, it will this...
@liubotao Thank you very much for your contribution. However this change is super large, to make everyone on the same page, could you create a feature request GitHub Issue to...
> When user set a long TTL for table partitions, but the historic partitions are never scanned or rarely scanned, it would cause unnecessary storage waste and metadata pressure. So...
@MatthewH00 When a new feature is added to a database system, it will be very hard, if not impossible, to change or deprecate it. Because users have depended on these...