distributed-database

What happened?

In a Jepsen test run of five etcd 3.5.3 nodes, with process pauses (sending processes SIGSTOP and SIGCONT), compaction (performed via the admin API), and defragmentation (via etcdctl), one etcd process crashed with the following error message:

{"level":"panic","ts":"2022-06-13T14:11:27.870Z","caller":"etcdserver/apply.go:638","msg":"unexpected error during txn","error

ddl_api.go

// forbit cache table in system database.
-->
is that typo? could be forbidden cache table in system database.

When a roachprod user runs grafana-start, regardless of whether they pass a grafana-config, a user should be able to see a default dashboard, perhaps with the following pages.

Jira issue: CRDB-17197

Feature Request

For English only, other languages will not accept.

Please pay attention on issues you submitted, because we maybe need more details.
If no response anymore and we cannot make decision by current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Is your feature request related to a problem?

Yes, refer t

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

Jira Link: DB-2620

Description

Steps to repro -

• Setup xcluster replication between 2 universes with TLS ON and different certs.
• Start replication in demo1 table.
• Edit replication by adding demo2 table → fails.

Failing on 2.14, 2.15.0 and 2.15.1.

Platform Error message -

java.lang.RuntimeException: java.lang.RuntimeExce

Use case:

PosgreSQL client compatibility (e.g. Trino)
SQL compliance

CrateDB

CREATE TABLE doc.x (txt TEXT)
SELECT crate.doc.x.txt FROM crate.doc.x

PostgreSQL

postgres=# CREATE TABLE public.x (txt TEXT);
CREATE TABLE
postgres=# SELECT postgres.public.x.txt FROM postgres.public.x;
 txt 
-----
(0 rows)

[From PostgreSQL docs](https://www.postg

Enhancement

Sometimes we need to modify configurations like schedule_slot_num_per_path to accelerate balance or repair process. Currently, if we want to change the value of schedule_slot_num_per_path we need to restart FE leader which can be quiet user unfriendly.

now the field name is used in explain verbose and the column name of internal table in stream plan. but the name is not detailed enough.

project and agg

now the expressions in the LogicalProject and AggCall in the LogicalAgg we use the name like "expr#1", "agg#1". in the new design we will use the to_string() as its field name.
we can just maintain the input_ref in the name, but the

Describe this problem

Failed to execute query, err: Server(ServerError { code: 500, msg: "Failed to convert output, query: DROP TABLE demo;. Caused by: Rpc error, code:500, message:Failed to convert output - affected rows: 1" })

A drop table tells one row is affected

Steps to reproduce

drop table demo;

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