distributed-database

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create database db;
use db;
rename table tb1 to tb2;

2. What did you expect to see? (Required)

MySQL 5.7
ERROR 1017 (HY000): Can't find file: './db_optimistic/tb1.frm' (errno: 2 - No suc

We currently do not implement the ALTER SEQUENCE ... RESTART [with restart].

CREATE SEQUENCE customer_seq_alter_1 MINVALUE -2 MAXVALUE 2 START WITH 1 CACHE 5 INCREMENT BY -2;
SELECT nextval('customer_seq_alter_1'); 
SELECT nextval('customer_seq_alter_1');
ALTER SEQUENCE customer_seq_alter_1 RESTART; -- does not work

Hi, community:

This issue is to add more unit tests for the ShardingRenameTableStatementValidator class. Welcome to claim them.

The specific subtasks are as follows:

• Add unit test for ShardingRenameTableStatementValidator#preValidate
• Add unit test for ShardingRenameTableStatementValidator#postValidate

Through this issue, you can understand the process of participating in

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

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

ClickHouse supports renaming schemas using RENAME DATABASE command.

It's only supported for databases created using the ATOMIC engine - see https://clickhouse.com/docs/en/sql-reference/statements/rename/

Atomic engine has been available since v20.4.2.9-stable (see ClickHouse/ClickHouse@7928f2e) and has become the default since

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

• be/test/runtime/string_buffer_test.cpp
• be/src/runtime/string_buffer.hpp
• be/src/util/types.h

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