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:

Describe the problem
When trying to use SHOW CREATE on a materialized view, the generated DDL is no longer a materialized view but a normal view, and the internal rowid column is part of the column definition.

To Reproduce

1. Create a materialized view:

CREATE MATERIALIZED VIEW test AS (SELECT 1 AS foo);

2. Use SHOW CREATE:

SHOW CREATE test

3. See tha

Hi community,

This issue is for WeOpen-Star

We need to translate DistSQL cluster governance capabilities to English

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

source: https://docs.yugabyte.com/latest/architecture/transactions/isolation-levels/#root

We begin the section by listing out 4 transaction isolation levels in decreasing order of strictness. Where possible, subsequent sections should follow this order to make it easier for readers to follow. For example, rewrite the second paragraph to read:

YugabyteDB supports three transa

The similar issue with https://github.com/trinodb/trino/issues/10857 and https://github.com/trinodb/trino/issues/11110

trino> CREATE VIEW accumulo .schema_not_found.test AS SELECT 1 AS c1;
CREATE VIEW

Use case:

Get the total duration over many events. Something like select sum(age(ended, started)) from myevents or select sum(ended - started) from myevents - depending on crate/crate#12479

See https://github.com/crate/crate/blob/dc3ce297b1597d482949a2e57479890feb3adbf4/server/src/main/java/io/crate/execution/engine/aggregation/impl/SumAggregation.java#L67

Refactoring request

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

Requirements
We want to support the owner field for database / schema / table / source objects. The implementation should be based on the user account management design recorded in #2193 , and should work as an addition to the feature chunk for supporting the concepts of and operations related to database, schema, and users (tracked in #2150 )
References
Please use #2150 as the main ref

Is there an existing issue for the same feature request?

• I have checked the existing issues.

Is your feature request related to a problem?

Several showcase SQL requires the support of this function:


select DATE_FORMAT(b.measurement_time,'%Y-%m-%d') 

select DATE_FORMAT(FROM_UNIXTIME(tm.create_time), %Y%m%d)

Describe the feature you'd like

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