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?

Postgres provides the fuzzystrmatch module, which includes several useful functions:

• levenshtein and levenshtein_less_equal, to calculate levenshtein distance between strings
• soundex and difference to calculate Soundex codes for names
• metaphone, dmetaphone and dmetaphone_alt to compute "sounds like" stri

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

databasename can not contain dot 。if contain， after dot string will be discard。 i found like pattern in SQLServerDataSourceMetaData class "jdbc:(microsoft:)?sqlserver://([\w-.]+):?([0-9]);\S(DatabaseName|database)=([\w-]+);?" should be "jdbc:(microsoft:)?sqlserver://([\w-.]+):?([0-9]);\S(DatabaseName|database)=([\w-.]+);?"

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-

For an onprem cloud provider, need validation to disable entering duplicate region codes on the "Region and Zones page". Currently, it fails silently without any visual feedback, and the only way to know is from the developer tools

{"error":"Region code already exists: us-west"}

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

Make tests in TestSetSessionTask more readable by using assertThatThrownBy.

e.g. https://github.com/prestosql/presto/blob/master/presto-main/src/test/java/io/prestosql/execution/TestSetSessionTask.java#L155

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