4 Commits (35d1160ace75b44b0942bc29b7c8678ca84fe728)

Author	SHA1	Message	Date
Onur Tirtir	a9820e96a3	Make single_node_truncate.sql re-runnable ... First of all, this commit sets next_shard_id for single_node_truncate.sql because shard ids in the test output were changing whenever we modify a prior test file. Then the flaky test detector started complaining about single_node_truncate.sql. We fix that by specifying the correct test dependency for it in run_test.py.	2023-03-02 16:33:18 +03:00
Gledis Zeneli	badfd561b2	Prevent Citus table functions from being called on shards (Fix #5610) (#5694) ... DESCRIPTION: Prevent Citus table functions from being called on shards The operations that guard against using shards are: * Create Local Table * Create distributed table (which affects reference table creation as well). * I used a `ErrorIfRaltionIsKnownShard` instead of `ErrorIfIllegallyChangingKnownShard`. `ErrorIfIllegallyChangingKnownShard` allows the operation if `citus.enable_manual_changes_to_shards`, but I am not sure if it ever makes sense to create a distributed, reference, or citus local table out of a shard. I tried to go over the code to identify other UDF-s where shards could be illegaly changed, but I could not find any other. My knowledge of the codebase is not solid enough for me to say for sure. Fixes #5610	2022-02-14 16:06:48 +03:00
Ahmet Gedemenli	089ef35940	Disable dropping and truncating known shards ... Add test for disabling dropping and truncating known shards	2021-06-02 14:30:27 +02:00
Hanefi Onaldi	056005db4d	Improve tests for truncating local data (#5012) ... We have a slightly different behavior when using truncate_local_data_after_distributing_table UDF on metadata synced clusters. This PR aims to add tests to cover such cases. We allow distributing tables with data that have foreign keys to reference tables only on metadata synced clusters. This is the reason why some of my earlier tests failed when run on a single node Citus cluster.	2021-06-03 08:51:32 +03:00