distributed-database

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

CREATE DATABASE IF NOT EXISTS tispark_test;
CREATE TABLE IF NOT EXISTS tispark_test.table_test(i int, s varchar(128));
CREATE ROLE IF NOT EXISTS 'test_read', 'test_write';
GRANT SELECT ON tispark_test.table_test TO 'test_read'@'%';
GRANT UPDATE ON `tispa

Forked from #72227 (initially reported by @amitsadaphule )

Describe the problem

The expected output in the test TestAnonymizeStatementsForReporting (conn_executor_test.go) is overly prescriptive as to the result of formatting an error containing a redacted statement.

Namely, it has particular requirements about how the stack trace is formatted.

This is unnecessary for the test, w

Please add into org.apache.shardingsphere.infra.config.DataSourceConfigurationTest

We create a number of threads in various places in our code, and in most cases we do not give these threads names. It could be helpful to have names that make it easier for us to see what a thread is doing. Some examples include:

1. The network thread created by bindings (some bindings name this thread, others do not)
2. External network threads (name proposed in #6033)
3. Trace logging threa

This would allow the CLI to try connecting to a different node is the first node goes down.

In yugabyte/yugabyte-db#8730, we added commands flush_sys_catalog and compact_sys_catalog. However, these commands only work at the leader sys catalog tablet. We should enhance these commands to work across peers, not just at the leader

We should use MockConnector to simulate connector that support missing columns on insert and test if row filtering is properly handled if columns are missing during the insert but used in row filters.

Related to: #10006 and #10005

Use case:
Add the ability to search for an element in an array and retrieve back the array index.
As per the PostgreSQL documentation:

array_position ( anycompatiblearray, anycompatible [, integer ] ) → integer

Returns the subscript of the first occurrence of the second argument in the array, or NULL if it's not present

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