distributed-database

"found" by the @discordapp troops the hard way: https://status.discordapp.com/incidents/62gt9cgjwdgf
pinging @zorkian who pointed it out to me.

trivial to repro, this is against a 3.3.13 on fedora-31.

$ etcdctl set /baa schnorp
$ etcdctl get /baa
schnorp
$ echo -ne 'PUT /v2/keys/baa HTTP/1.1\r\nHost: boo\r\nContent-Length: 123\r\n\r\n' | nc localhost 2379
HTTP/1.1 200 OK
...
$ et

Brief Motivation

This issue tracks the efforts to restructure TiDB tests, focusing on unit tests and integration tests, especially on separating integration_test.go as well as unifying test infrastructure in testify.

For the detailed design, see also:

• #26023

Join force

We are currently on the first phase on the effort and focus on

We do have the internal metadata concepts to make this happen in a relatively inexpensive way. That being said, we have not implemented this functionality. Please file a github issue to track it and discuss various design point. I will warn you that I don’t think this is something we’re in any hurry to implement. That issue can also be a way to gauge interest and work out syntax details. (by ajw

Hi community,

This issue is for #10887.

Aim

Add example to validate Parser SQLStatement for PostgreSQL Database.

Examples FYI

• MySQLParserStatementExample

fdbcli flags currently contain a mixture of _ and - (probably for historic reasons). I would propose to unify the flags and only use either _ or - personally I tend to hyphens like recommended in the POSXI standard (https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html). Current fdbcli help output:

FoundationDB CLI 6.2 (v6.2.29)
usage: /usr/bin/fdb/6.2/fdbcli

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-

Flush/Compact requests to the tServer are rpcs that are expected to take a long time. It does not make sense for these to use the same deadline (20s) and num_retries as other async_rpc_tasks.

We should have these tasks override these settings; similar to what BackfillChunk does to give itself more time; and also to disble/reduce retries in the case of flush/compact.

Without having this, we

In the past a conversion through Number "interface" has proven to be able to mask bugs in the code.
We should remove these conversions from io.trino.spi.type.TypeUtils#writeNativeValue.

Use case:

1.) A user may want to backup all tables but no metadata like users, privileges, etc. without explicitly defining each table inside the CREATE SNAPSHOT statement.

2.) A user may want to transfer users & privileges, custom analyzers or user-defined-functions from one cluster to another without backing up a complete cluster including all data (tables).

*Feature description

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