kaijianding
kaijianding
Build it from source, I did it, and it worked. https://github.com/qdore/Mutate#from-source
eg: there are lots of rows in a 1min batch. Some rows are like 1 day behind, some rows are very close to current time. `messageGap` is the min gap...
> @kaijianding Do you think the name `custom_query_id` is more suitable? And I suggest you can split this PR into multi PRs. One is to add new query id. the...
@alvin-celerdata this pr is modified to only kill query by query id, please review.
> 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}` for the query. `Query...
@alvin-celerdata > 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}` for the query....
@satanson any more comments?
1. `query_id` can be found using `show processlist` and `show proc '/current_queries'` when query **IS** running. When user can issue `show processlist` or `show proc '/current_queries'`, he can just do...
1. `KILL QUERY query_id` is not supported now. I meant `conn_id` that can kill a query from `show processlist`. 2. `ExecutionId` and `QueryId` are both existed now, and are assigned...
Yes, this feature is for expert, usually a platform user who is building a product on starrocks. This product will `set custom_query_id` for each query and guarantee the `custom_query_id` is...