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

You may try to analyze first and spawn more subtasks on demand (no strict) instead of one big PR handle the whole package which is hard to review.

Describe the solution you'd like
Ability to export to Apache Parquet format.

EXPORT INTO PARQUET
  'azure://acme-co/customer-export-data?AZURE_ACCOUNT_KEY=hash&AZURE_ACCOUNT_NAME=acme-co'
   FROM TABLE bank.customers;

Describe alternatives you've considered
Using CSV format

Additional context
Parquet stores the file sc

Hi community,

This issue is for #11661

Aim

Add unit test for shardingsphere-shadow-core project to test its public functions.

Basic Qualifications

• Java
• Maven
• Junit.Test

Classes

Add unit test for classes to test its public functions.

• ShadowDataSourceConfigurationYamlSwapper
• ShadowTableConfigurationYamlSwapper
• ShadowRuleAlgorithmProviderConf

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-

Currently when yb-admin command is slightly misspelled, e.g. list_snapshot_schedule instead of list_snapshot_schedules, the user would be given the whole list of commands.

User experience can be improved by using the (partial) command as prefix.

If there is only one match, that match would be picked - we can ask the user to confirm the selection (or add option, say -accept-prefix-match which

If the --server option is used without a protocol, then it should use https when on port 443. For example, these invocations would be equivalent, with the first one having the new behavior:

trino --server example.net:443
trino --server https://example.net:443
trino --server https://example.net

This will make the CLI consistent with the JDBC driver in this regard. While it's t

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