Discussed in this comment

CockroachDB provides a function called gen_random_uuid() which returns a UUID value generated randomly.

However the pg name for this function is uuid_generate_v4()

See this doc

We also probably need to recognize `CREATE EXTE

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

There is still use old configuration in this page, we need to update them to new version

This issue is the umbrella issue tracking the effort to add namespace to FDB code base. Idea is that with namespace in place, code would be much easier to read and understand at the call site. The coupling between different parts of the system would be easier to be seen and understood. Also this can help with potential symbol collisions.

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-

Node-to-node tls is a pre-requisite in order to use "client-to-node" tls. Currently UI allows selecting "client-to-node" tls even if "node-to-node" tls is not selected. Both API and UI should do a pre-flight check for this.

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

Extract AbstractDynamicFilteringTests class, so that connectors that implement DF could use tests from that class to validate functionality. Each connector should not implement it's own test suite.

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