It is mentioned that there is an error code page for v2 protocol:
https://github.com/etcd-io/etcd/blob/ae7862e8bc8007eb396099db4e0e04ac026c8df5/server/etcdserver/api/v2error/error.go#L16

However, I can't find Documentation/v2/errorcode.md in this repo. Is the comment stale?

Most aggregate functions support multi-stage distributed execution in which on every node we perform a local aggregation, then we route all the intermediate results to all of the nodes (according to the grouping columns), and then we perform a final aggregation that gives us the result. For some aggregate functions the decomposition into local and final stages is trivial - e.g. in order to calcula

Now insert and query share the resource ( Max Process Count control) 。 When the query with high TPS，the insert will get error (“error: too many process”). I think separator the resource for Insert and Query will makes sense. Ensure enough resource for insert。It looks like Use Yarn， Insert and Query use the different resource quota。
Or the simple way , Can we set Ratio for Insert and

The test case SchemaBuilderTest is not make sense. It is better to redesign it for testing.

The network option setting code uses the default option code, which interprets the bytes passed to the option as a binary encoded 8 byte integer. The only way to set an integer value is to set the environment variable to the 8 byte binary encoding.

Hello Philip!
I think there is an issue with this part of the code of rqlite (store/store.go).

func (s *Store) Database(leader bool) ([]byte, error) {
	if leader && s.raft.State() != raft.Leader {
		return nil, ErrNotLeader
	}
	// Ensure only one snapshot can take place at once, and block all queries.
	s.mu.Lock()
	defer s.mu.Unlock()

	f, err := ioutil.TempFile("", "rqlilte-snap-

YugabyteDB version 2.2.5.0 (2fa951fa96f0d1ea7ec2b7ad228573430b4c20ff)
Platform version 2.4.0.0

The preferred zone displayed is us-central1-f

But preferred zone we are seeing in cluster configuration is: us-central1-b.

Migrate the tests from DataTypeTest to SqlDataTypeTest.

• DataTypeTestToSqlDataTypeTestConverter (being added in trinodb/trino#6391) may aid the migration.
• ideally the work should be done incrementally (in small steps) to facilitate the review process

See trinodb/trino#6391 for example approach.

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

Now that we support more than 1 data type, we should include the values data type in cache nodes. This give us a way of easily identifying what type of data a key points to e.g. string, queue (and more types in the future)

Currently a cache node object consists of a Key, a Value and a TTL. We should also add a field specifying the type of the Value