distributed-database

Although RULE is not listed as an allowed privilege on https://www.postgresql.org/docs/current/functions-info.html it turns out that PG supports a query like this

select has_table_privilege('table'::regclass::oid, 'RULE')

Some tools rely on this. We can implement it in CRDB by always returning false, since CRDB does not have RULE privileges.

Instructions:

• Modify t

Hi, community:

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

The specific subtasks are as follows:

• Add unit test for ShardingConditions#isAlwaysFalse
• Add unit test for ShardingConditions#merge
• Add unit test for ShardingConditions#isNeedMerge
• Add unit test for ShardingConditions#isSameShardingCondition

Throug

Calling setclass in fdbcli will try to change any process that matches the process filter given. If no processes are found, it silently does nothing. Instead, it should report back to the user that no processes matched the given filter.

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

Description

Currently, for e.g. say that out of 3 copies of a tablet, we want to have 2 copies in C1.R1.Z1 and 1 copy in C2.R2.Z2 then we would specify it as below:

./bin/yb-admin \
    -master_addresses $MASTER_RPC_ADDRS \
    modify_placement_info  \
    C1.R1.Z1,C1.R1.Z1,C2.R2.Z2 3

However, this is somewhat complex and hard to follow. We don't need to necessarily r

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:
Selecting a subset of array elements of an existing array inside the database without the need to unnest the array first or use a user-defined function.

CREATE TABLE t1 (id INTEGER, tags ARRAY(TEXT));
INSERT INTO t1 (id, tags) VALUES (1, ['database','search engine','document store']);

SELECT array_slice(tags,2,3) FROM t1;
--> ['search engine','document s

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