distributed-database

What happened?

If you don't pass a --name argument to your etcd processes, they will all have the name default and the cluster will operate normally. However, when you add a member, the generated ETCD_INITIAL_CLUSTER variable will have multiple entries with the name "default". When this environment variable is used, etcd will parse these into a mapping under a single key ("defau

Enhancement

[2022-02-14T04:12:14.746Z] ----------------------------------------------------------------------
[2022-02-14T04:12:14.746Z] FAIL: db_test.go:7069: testSerialDBSuite.TestModifyColumnTypeWhenInterception
[2022-02-14T04:12:14.746Z] 
[2022-02-14T04:12:14.746Z] db_test.go:7124:
[2022-02-14T04:12:14.746Z]     c.Assert(checkMiddleWarningCount, Equals, true)
[2022-02-14T04:12:

We can use a wildcard for listing all grants for the tables in a database

> show grants on table mydb.* for mydb_mgmt;
  database_name | schema_name | table_name |  grantee  | privilege_type
----------------+-------------+------------+-----------+-----------------
  mydb          | public      | t1         | mydb_mgmt | ALL
  mydb          | public      | t2         | mydb_mgmt | A

Examples

The examples under https://github.com/apache/shardingsphere/tree/master/examples/docker are outdated.
Consider

• Bump the image to apache/shardingsphere:latest
• Use PostgreSQL as database (MySQL JDBC Driver is not included in ShardingSphere-Proxy by default)
• Update configurations

Our CMake build process produces tarball packages using the cpack TGZ target. This produces a server and client package with a file layout meant to match where the various artifacts go.

Meanwhile, the packages we include on the download page are a flat archive of various binaries produced by the build process. This include one regular package and one debug package with debug symbols for a few

Description

Create a cluster with TEST_docdb_log_write_batches=true and observe the following -

./bin/yb-ctl create --rf=1 --data_dir ~/yugabyte-data --tserver_flags 'TEST_docdb_log_write_batches=true'
./bin/ysqlsh
yugabyte=# create table test (k int primary key, v int);
CREATE TABLE
yugabyte=# insert into test values (1, 1);
ERROR:  Network error: recvmsg error: Connection refus

Instead of creating on the fly an Iceberg table with Trino and run queries against it, use static resources for setting up an Iceberg test environment which can be used to read Iceberg v1 / v2 tables and guard trino-iceberg plugin against regresssions.

Related discussion: trinodb/trino#11642 (comment)

Use case:
As an admin user - without access to a super user - I still want to be able to run ANAYLZE.

note: it is already possible to adjust stats.service.interval and indirectly trigger ANALYZE

Feature description:
ANALYZE is allowed with AL privileges.

https://crate.io/docs/crate/reference/en/4.7/sql/statements/analyze.html

Refactoring request

Rename the namespace starrocks::vectorized to starrocks for codes under be/src/storage.

So that we don't need to cast every time in the program.