---
name: watsonxdata-reg_bucket
title: Adding storage
description: ''
last-updated: 2026-05-11
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/watsonxdata?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

{:javascript: #javascript .ph data-hd-programlang='javascript'}
{:java: #java .ph data-hd-programlang='java'}
{:ruby: #ruby .ph data-hd-programlang='ruby'}
{:php: #php .ph data-hd-programlang='php'}
{:python: #python .ph data-hd-programlang='python'}
{:external: target="_blank" .external}
{:shortdesc: .shortdesc}
{:codeblock: .codeblock}
{:screen: .screen}
{:tip: .tip}
{:important: .important}
{:note: .note}
{:deprecated: .deprecated}
{:pre: .pre}
{:video: .video}

# Adding storage
{: #reg_bucket}

In IBM® watsonx.data, the data is stored either in an internal storage created during instance provisioning or in an externally managed storage. You can associate a catalog with a storage. A catalog defines the schemas and metadata for a storage.

When you add your own storage bucket or data source, or query the data in these data sources through the query engines of watsonx.data, egress charges for pulling data out of these sources might apply depending on your service provider. If you are using managed services, consult your service provider's documentation or support for details about these charges.
{: important}

To reduce the latency issues, it is recommended to colocate your additional storage buckets or databases in the region where watsonx.data instance is provisioned.
{: important}


To add a storage, complete the following steps:

1. Log in to the watsonx.data console.
2. From the navigation menu, select **Infrastructure manager**.
3. To define and connect a storage, click **Add component**.
4. In the **Add component** window, select a storage from the **Storage** section and provide the details to establish the connection.

Hadoop Distributed File System (HDFS) is not supported in Milvus.
{: note}

watsonx.data supports the following data storage options:
   * [IBM Cloud Object Storage](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-cos_storage&format=markdown)
   * [Amazon S3](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-amazons_storage&format=markdown)
   * [IBM Storage Ceph](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-ceph_storage&format=markdown)
   * [MinIO](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-minio_storage&format=markdown)
   * [Hadoop Distributed File System](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-hdfs_storage&format=markdown)
   * [Google Cloud Storage](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-gcs_storage&format=markdown)
   * [Azure Data Lake Storage](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-adls_genblob_storage&format=markdown)
   * [Apache Ozone](https://cloud.ibm.com/docs/watsonxdata?topic=watsonxdata-ozone_storage&format=markdown)

     You can modify the endpoint, access key and secret key of a user-registered bucket for a storage. This feature is only available for user-registered buckets and is not applicable to default buckets, ADLS, or Google Cloud Storage. This feature can be used if the new credentials successfully pass the test connection. You must disassociate the storage from the engine to modify the details.
     {: note}

   **Important information**{: #important_info}
   * The storage bucket name must be unique and must contain only the characters A–Z, a–z, 0–9, and hypen (-).
   * You must use a service credential with `Writer` role because the schema is written to the storage bucket. Make sure that you choose the endpoint that matches the type of access that the bucket allows. That is, if no public access is allowed (**Public access** is **No**) to the bucket, choose the **Direct** endpoint.

## Additional information about connector
{: #connector_features}

* For **Iceberg** connector:
    * You can delete data from tables by using `DELETE FROM` statement for **Iceberg** connector.
    * You can specify the table property delete_mode for new tables by using either copy-on-write mode or merge-on-read mode (default).
* For `DELETE FROM` statement for **Iceberg** connector:
    * Filtered columns only support comparison operators, such as EQUALS, LESS THAN, or LESS THAN EQUALS.
    * Deletes must only occur on the latest snapshot.
    * For V1 tables, the **Iceberg** connector can delete data only in one or more entire partitions. Columns in the filter must all be identity-transformed partition columns of the target table.
* For `CREATE TABLE`, **Iceberg** connector supports `sorted_by` table property.
    * When you create the table, specify an array of one or more columns that are involved.
* For **Iceberg** connector, `ALTER TABLE` operations on a column support data type conversions from:
    * `INT` to `BIGINT`
    * `FLOAT` to `DOUBLE`
    * `DECIMAL` (num1, dec_digits) to `DECIMAL` (num2, dec_digits), where num2>num1.

## Limitations for SQL statements
{: #sql_limitations}

* For **Iceberg** connector, `UPDATE` query with sub-query is not supported.
* For **Iceberg** connector, `UPDATE` query with mixed-case column is not supported.
* For **Iceberg**, **Memory** and **Hive** connectors, `DROP SCHEMA` can do `RESTRICT` by default.
* For database-based catalogs the `CREATE SCHEMA`, `CREATE TABLE`, `DROP SCHEMA`, `DROP TABLE`, `DELETE`, `DROP VIEW`, `ALTER TABLE`, and `ALTER SCHEMA` statements are not available in the **Data Manager** UI.

## Limitations for data types
{: #datatypes_limitations}

* For **Iceberg** connector, the maximum number of digits that can be accommodated in a column of data type FLOAT and DOUBLE is 37. Trying to insert anything larger ends up in a decimal overflow error.
* When the fields of data type `REAL` have 6 digits or more in the decimal part with the digits being predominately zero, the values when queried are rounded off. It is observed that the rounding off occurs differently based on the precision of the values. For example, a decimal number 1.654 when rounded to 3-digits after decimal point are the same. Another example, is 10.890009 and 10.89000. It is noticed that 10.89000 is rounded to 10.89, whereas 10.89009 is not rounded off. This is an inherent issue because of the representational limitations of binary floating point formats. This might have a significant impact when querying involves sorting.

For more information on mixed-case feature flag behavior, supported SQL statements and supported data types matrices, see [Support content](https://www.ibm.com/support/pages/node/7157339){: external}.

## Related API
{: #storage_api}

For information on related API, see
* [Get bucket registrations](https://cloud.ibm.com/apidocs/watsonxdata#list-bucket-registrations)
* [Register bucket](https://cloud.ibm.com/apidocs/watsonxdata#create-bucket-registration)