alter_table

Table on which the operation will be performed, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing table or view.

Modification operation to be applied. Allowed values are:

• create_index – Creates a column (attribute) index, low-cardinality index, chunk skip index, geospatial index, CAGRA index, or HNSW index (depending on the specified index_type), on the column name specified in input parameter value. If this column already has the specified index, an error will be returned.

• refresh_index – Refreshes an index identified by index_type, on the column name specified in input parameter value. Currently applicable only to CAGRA indices.

• delete_index – Deletes a column (attribute) index, low-cardinality index, chunk skip index, geospatial index, CAGRA index, or HNSW index (depending on the specified index_type), on the column name specified in input parameter value. If this column does not have the specified index, an error will be returned.

• move_to_collection – [DEPRECATED–please use move_to_schema and use GPUdb.create_schema() to create the schema if non-existent] Moves a table or view into a schema named input parameter value. If the schema provided is non-existent, it will be automatically created.

• move_to_schema – Moves a table or view into a schema named input parameter value. If the schema provided is nonexistent, an error will be thrown. If input parameter value is empty, then the table or view will be placed in the user’s default schema.

• protected – No longer used. Previously set whether the given input parameter table_name should be protected or not. The input parameter value would have been either ‘true’ or ‘false’.

• rename_table – Renames a table or view to input parameter value. Has the same naming restrictions as tables.

• ttl – Sets the time-to-live in minutes of the table or view specified in input parameter table_name.

• add_comment – Adds the comment specified in input parameter value to the table specified in input parameter table_name. Use column_name to set the comment for a column.

• add_column – Adds the column specified in input parameter value to the table specified in input parameter table_name. Use column_type and column_properties in input parameter options to set the column’s type and properties, respectively.

• change_column – Changes type and properties of the column specified in input parameter value. Use column_type and column_properties in input parameter options to set the column’s type and properties, respectively. Note that primary key and/or shard key columns cannot be changed. All unchanging column properties must be listed for the change to take place, e.g., to add dictionary encoding to an existing ‘char4’ column, both ‘char4’ and ‘dict’ must be specified in the input parameter options map.

• delete_column – Deletes the column specified in input parameter value from the table specified in input parameter table_name.

• set_default – Sets or replaces the default value expression for the column specified in input parameter value. The new default is taken from add_column_expression. Existing properties on the column are preserved.

• delete_default – Removes the default value expression from the column specified in input parameter value. Other column properties are preserved.

• create_foreign_key – Creates a foreign key specified in input parameter value using the format ‘(source_column_name [, …]) references target_table_name(primary_key_column_name [, …]) [as foreign_key_name]’.

• delete_foreign_key – Deletes a foreign key. The input parameter value should be the foreign_key_name specified when creating the key or the complete string used to define it.

• add_partition – Adds the partition specified in input parameter value, to either a range-partitioned or manual list-partitioned table.

• remove_partition – Removes the partition specified in input parameter value (and relocates all of its data to the default partition) from either a range-partitioned or manual list-partitioned table.

• delete_partition – Deletes the partition specified in input parameter value (and all of its data) from either a range-partitioned or manual list-partitioned table.

• set_global_access_mode – Sets the global access mode (i.e. locking) for the table specified in input parameter table_name. Specify the access mode in input parameter value. Valid modes are ‘no_access’, ‘read_only’, ‘write_only’ and ‘read_write’.

• refresh – For a materialized view, replays all the table creation commands required to create the view. For an external table, reloads all data in the table from its associated source files or data source.

• set_refresh_method – For a materialized view, sets the method by which the view is refreshed to the method specified in input parameter value - one of ‘manual’, ‘periodic’, or ‘on_change’. For an external table, sets the method by which the table is refreshed to the method specified in input parameter value - either ‘manual’ or ‘on_start’.

• set_refresh_start_time – Sets the time to start periodic refreshes of this materialized view to the datetime string specified in input parameter value with format ‘YYYY-MM-DD HH:MM:SS’. Subsequent refreshes occur at the specified time + N * the refresh period.

• set_refresh_stop_time – Sets the time to stop periodic refreshes of this materialized view to the datetime string specified in input parameter value with format ‘YYYY-MM-DD HH:MM:SS’.

• set_refresh_period – Sets the time interval in seconds at which to refresh this materialized view to the value specified in input parameter value. Also, sets the refresh method to periodic if not already set.

• set_refresh_span – Sets the future time-offset(in seconds) for the view refresh to stop.

• set_refresh_execute_as – Sets the user name to refresh this materialized view to the value specified in input parameter value.

• remove_text_search_attributes – Removes text search attribute from all columns.

• remove_shard_keys – Removes the shard key property from all columns, so that the table will be considered randomly sharded. The data is not moved. The input parameter value is ignored.

• set_strategy_definition – Sets the tier strategy for the table and its columns to the one specified in input parameter value, replacing the existing tier strategy in its entirety.

• cancel_datasource_subscription – Permanently unsubscribe a data source that is loading continuously as a stream. The data source can be Kafka / S3 / Azure / GCS.

• drop_datasource_subscription – Permanently delete a cancelled data source subscription.

• pause_datasource_subscription – Temporarily unsubscribe a data source that is loading continuously as a stream. The data source can be Kafka / S3 / Azure / GCS.

• resume_datasource_subscription – Resubscribe to a paused data source subscription. The data source can be Kafka / S3 / Azure / GCS.

• change_owner – Change the owner resource group of the table.

• set_load_vectors_policy – Set startup data loading scheme for the table; see description of ‘load_vectors_policy’ in GPUdb.create_table() for possible values for input parameter value.

• set_build_pk_index_policy – Set startup primary key generation scheme for the table; see description of ‘build_pk_index_policy’ in GPUdb.create_table() for possible values for input parameter value.

• set_build_materialized_view_policy – Set startup rebuilding scheme for the materialized view; see description of ‘build_materialized_view_policy’ in GPUdb.create_materialized_view() for possible values for input parameter value.

• rebuild_text_search_index – Drops and rebuilds the text search index for the table from current type metadata and chunk storage. Use this to repair a text-search index left incomplete by an interrupted or failed rebuild (for example, after a crash during an add-column that requested text search): re-running the original add_column will not work because the column already exists. This action is also dispatched automatically by GPUdb.alter_table_columns() after add_column completions that require a full re-index. The input parameter value is ignored.

The value of the modification, depending on input parameter action. For example, if input parameter action is add_column, this would be the column name; while the column’s definition would be covered by the column_type, column_properties, column_default_value, and add_column_expression in input parameter options. If input parameter action is ttl, it would be the number of minutes for the new TTL. If input parameter action is refresh, this field would be blank.

Optional parameters. Allowed keys are:

• action

• column_name

• table_name

• column_default_value – When adding a column, set a literal default value for existing records. For nullable columns, the default value will be null, regardless of data type. Also persisted as the column’s default for future inserts that omit the column.

• column_properties – When adding or changing a column, set the column properties (strings, separated by a comma: data, text_search, char8, int8 etc).

• column_type – When adding or changing a column, set the column type (strings, separated by a comma: int, double, string, null etc).

• copy_values_from_column – [DEPRECATED] Please use add_column_expression instead.

• rename_column – When changing a column, specify new column name.

• validate_change_column – When changing a column, validate the change before applying it (or not). Allowed values are:

  • true – Validate all values. A value too large (or too long) for the new type will prevent any change.

  • false – When a value is too large or long, it will be truncated.

  The default value is ‘true’.

• update_last_access_time – Indicates whether the time-to-live (TTL) expiration countdown timer should be reset to the table’s TTL. Allowed values are:

  • true – Reset the expiration countdown timer to the table’s configured TTL.

  • false – Don’t reset the timer; expiration countdown will continue from where it is, as if the table had not been accessed.

  The default value is ‘true’.

• add_column_expression – When adding a column or setting a new default with input parameter action set to set_default, the new default expression (GPUdb-syntax) for the column. Any valid expression may be used, including one containing references to existing columns in the same table. Persisted as the column’s default for future inserts that omit the column; for add_column, also used to backfill existing rows.

• add_column_expression_sql – Optional SQL-syntax form of add_column_expression, used only when the SQL syntax differs from the GPUdb syntax. Persisted alongside the GPUdb form so SHOW CREATE TABLE / information_schema can reproduce the original SQL.

• strategy_definition – Parameter for specifying the tier strategy for the table and its columns when input parameter action is set_strategy_definition, replacing the existing tier strategy in its entirety.

• index_type – Type of index to create, when input parameter action is create_index; to refresh, when input parameter action is refresh_index; or to delete, when input parameter action is delete_index. Allowed values are:

  • column – Create or delete a column (attribute) index.

  • low_cardinality – Create a low-cardinality column (attribute) index.

  • chunk_skip – Create or delete a chunk skip index.

  • geospatial – Create or delete a geospatial index.

  • cagra – Create or delete a CAGRA index on a vector column.

  • hnsw – Create or delete an HNSW index on a vector column.

  The default value is ‘column’.

• index_options – Options to use when creating an index, in the format “key: value [, key: value [, …]]”. Valid options vary by index type.

The default value is an empty dict ( ).