[jira] [Resolved] (HBASE-28702) TestBackupMerge fails 100% of times on flaky dashboard

2024-07-20 Thread Liangjun He (Jira)
[ https://issues.apache.org/jira/browse/HBASE-28702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liangjun He resolved HBASE-28702. - Resolution: Fixed > TestBackupMerge fails 100% of times on flaky dashboard >

Re: Questions about respecting quotas in AggregateImplementation

2024-07-20 Thread Duo Zhang
Ah, you are right, we can add a flag to let the new client set it to a non default value. In this way I prefer we implement the 'partial result' logic. Sleeping at server side is not a good idea. Bryan Beaudreault 于2024年7月20日周六 23:09写道: > > Since the protocol is protobuf, it should be quite

Re: Questions about respecting quotas in AggregateImplementation

2024-07-20 Thread Bryan Beaudreault
Since the protocol is protobuf, it should be quite simple. We can add a new field supports_partial to the AggregationRequest proto. Only new clients would set this to true, and that would trigger the partial results on the client. We have a similar concept for how we handle supporting

Re: Questions about respecting quotas in AggregateImplementation

2024-07-20 Thread Duo Zhang
I do not think it is easy to change the current implementation to be 'partial results'. The current assumption of request/response is 'send a range and the agg type'/'return the agg result of the whole range'. If you want to make it possible to return earlier, I think we need to tell the client