external
/
citus
mirror of https://github.com/citusdata/citus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
639 Commits
645 Branches
162 Tags
103 MiB
Commit Graph

10 Commits (6b5ca72db644499ddd8e283b0bc6c4fa60c777d7)

Author SHA1 Message Date
Onder Kalaci 807fc1cc28 Reference Table Support - Phase 1 
With this commit, we implemented some basic features of reference tables.

To start with, a reference table is
  * a distributed table whithout a distribution column defined on it
  * the distributed table is single sharded
  * and the shard is replicated to all nodes

Reference tables follows the same code-path with a single sharded
tables. Thus, broadcast JOINs are applicable to reference tables.
But, since the table is replicated to all nodes, table fetching is
not required any more.

Reference tables support the uniqueness constraints for any column.

Reference tables can be used in INSERT INTO .. SELECT queries with
the following rules:
  * If a reference table is in the SELECT part of the query, it is
    safe join with another reference table and/or hash partitioned
    tables.
  * If a reference table is in the INSERT part of the query, all
    other participating tables should be reference tables.

Reference tables follow the regular co-location structure. Since
all reference tables are single sharded and replicated to all nodes,
they are always co-located with each other.

Queries involving only reference tables always follows router planner
and executor.

Reference tables can have composite typed columns and there is no need
to create/define the necessary support functions.

All modification queries, master_* UDFs, EXPLAIN, DDLs, TRUNCATE,
sequences, transactions, COPY, schema support works on reference
tables as expected. Plus, all the pre-requisites associated with
distribution columns are dismissed.
 2016-12-20 14:09:35 +02:00
Metin Doslu d43a01ebae Don't allow tables with different replication models to be colocated 2016-12-16 15:23:49 +02:00
Metin Doslu 4ff550429f Add colocate_with option to create_distributed_table() 
With this commit, we support three versions of colocate_with: i.default, ii.none
and iii. a specific table name.
 2016-12-16 14:53:35 +02:00
Metin Doslu 16218413d0 Error on different shard placement count 
In ErrorIfShardPlacementsNotColocated(), while checking if shards are colocated,
error out if matching shard intervals have different number of shard placements.
 2016-10-26 18:46:05 +03:00
Metin Doslu 520e7e3cb2 Add mark_tables_colocated() to update colocation groups 
Added a new UDF, mark_tables_colocated(), to colocate tables with the same
configuration (shard count, shard replication count and distribution column type).
 2016-10-26 17:29:03 +03:00
Metin Doslu 663828363c Add create_reference_table() 
create_reference_table() creates a hash distributed table with shard count
equals to 1 and replication factor equals to shard_replication_factor
configuration value.
 2016-10-20 15:29:30 +03:00
Metin Doslu 7baf72cc86 Final refactoring 2016-10-20 11:29:11 +03:00
Metin Doslu 31f08f8377 Add create_distributed_table() 
create_distributed_table() creates a hash distributed table with default values
of shard count and shard replication factor.
 2016-10-20 10:58:25 +03:00
Burak Yucesoy 55341815a8 Make shard transfer functions co-location aware 
With this change, master_copy_shard_placement and master_move_shard_placement functions
start to copy/move given shard along with its co-located shards.
 2016-10-13 18:16:40 +03:00
Burak Yucesoy 1a618b9c43 Internal co-location API 
With this commit we introduce internal API for co-location related operations.
 2016-09-29 11:56:53 +03:00