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

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

We have some transaction options (e.g. transaction timeouts, retry limits) that are persistent across transaction retries. This behavior can be useful if you want to enforce a timeout that starts from the beginning of your first try regardless of how many tries you take.

The persistent aspect of these options only applies if you use onError to implement your retry loop. If you instead reset y

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-

1. UniverseTaskBase.java, isServerAlive(), absent ybService.closeClient();
2. Universe.java, getMasterLeader(), it is better to put closeClient() into the finally block;
3. SetFlagInMemory.java, run(), closeClient() could be missed in case of any exceptions raised after getClient() and before closeClient();
4. WaitForServerReady.java, run(), it is better to put closeClient() into the `finally

We need to validate and sanitize the configuration. We already have this feature at some degree, but it's not good enough and poorly implemented. Every configuration struct has its own validator/sanitizer and these functions have to be called before running an Olric node.

Here is a sample. config.Client has its own Sanitize function and constructor.

// NewClient returns a new con

See https://github.com/prestosql/presto/runs/1497472672

• tests apparently hanged
• one test thread is here:

2020-12-04T07:53:43.1535741Z "pool-2-thread-2" prio=5 Id=16 BLOCKED on org.testng.TestClass@2a78dd6a owned by "pool-2-thread-1" Id=15
2020-12-04T07:53:43.1537790Z 	at app//org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:158)
2020-12-04T07:53

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