| no_error_if_exists | If true, prevents an error from occurring if the table already exists and is of the given type. If a table with the same ID but a different type exists, it is still an error. The default value is false. The supported values are: |
| create_temp_table | If true, a unique temporary table name will be generated in the sys_temp schema and used in place of input parameter table_name. If is_result_table is true, then this is always allowed even if the caller does not have permission to create tables. The generated name is returned in qualified_table_name. The default value is false. The supported values are: |
| collection_name | [DEPRECATED--please specify the containing schema as part of input parameter table_name and use /create/schema to create the schema if non-existent] Name of a schema which is to contain the newly created table. If the schema is non-existent, it will be automatically created. |
| is_collection | [DEPRECATED--please use /create/schema to create a schema instead] Indicates whether to create a schema instead of a table. The default value is false. The supported values are: |
| disallow_homogeneous_tables | No longer supported; value will be ignored. The default value is false. The supported values are: |
| is_replicated | Affects the distribution scheme for the table's data. If true and the given type has no explicit shard key defined, the table will be replicated. If false, the table will be sharded according to the shard key specified in the given input parameter type_id, or randomly sharded, if no shard key is specified. Note that a type containing a shard key cannot be used to create a replicated table.
The default value is false. The supported values are: |
| foreign_keys | Semicolon-separated list of foreign keys, of the format '(source_column_name [, ...]) references target_table_name(primary_key_column_name [, ...]) [as foreign_key_name]'. |
| foreign_shard_key | Foreign shard key of the format 'source_column references shard_by_column from target_table(primary_key_column)'. |
| partition_type | Partitioning scheme to use. |
| partition_keys | Comma-separated list of partition keys, which are the columns or column expressions by which records will be assigned to partitions defined by partition_definitions. |
| partition_definitions | Comma-separated list of partition definitions, whose format depends on the choice of partition_type. See range partitioning, interval partitioning, list partitioning, hash partitioning, or series partitioning for example formats. |
| is_automatic_partition | If true, a new partition will be created for values which don't fall into an existing partition. Currently only supported for list partitions. The default value is false. The supported values are: |
| ttl | Sets the TTL of the table specified in input parameter table_name. |
| chunk_size | Indicates the number of records per chunk to be used for this table. |
| chunk_column_max_memory | Indicates the target maximum data size for each column in a chunk to be used for this table. |
| chunk_max_memory | Indicates the target maximum data size for all columns in a chunk to be used for this table. |
| is_result_table | Indicates whether the table is a memory-only table. A result table cannot contain columns with store_only or text_search data-handling or that are non-charN strings, and it will not be retained if the server is restarted. The default value is false. The supported values are: |
| strategy_definition | The tier strategy for the table and its columns. |
| is_virtual_union | <DEVELOPER> |
