For Data Tank 2.0, the settings can be self-managed in the Management UI, which is different from Data Tank where the settings are configured by Treasure Data.
For Data Tank 2.0, Access Keys are required to access the Data Tank 2.0, while in Data Tank, there are default users, tank_user and tank_integration_user. For Data Tank 2.0, you need to create the Access Keys in the Management UI.
Learn more about Managing Access Keys.
In Data Tank 2.0, you can create multiple user-defined schemas in the Management UI, unlike Data Tank which provides only one schema called “public”.
Learn more about Creating a New Schema.
A database user (Access Key) cannot operate on objects in the schema before permission settings, called Access Policies, are applied. You can grant permissions to the Access Key for the specific schema in the Management UI.
Learn more about Managing Access Policies.
Data Tank 2.0 also only allows access from specific IP addresses. Add your IP addresses to the IP Whitelist of Data Tank 2.0 via Management UI.
"g:treasuredata-main" set by default is an alias for the IP addresses used by each function of Treasure Data (including Management UI). Do not delete it, as deleting it will make it inaccessible to Data Tank 2.0.
Learn more about Configuring your IP Whitelist.
No data is stored at the time Data Tank 2.0 is provided. Prepare any necessary data for import.
If you would like to use records stored in the tables in TD, it is recommended that you use Result Export to PostgreSQL. This feature exports the results of Hive/Presto queries to PostgreSQL.
If you would like to move records stored in Data Tank to Data Tank 2.0, you need to move them by yourself.
- Import your data from Data Tank into a TD table using Import from PostgreSQL.
- Extract the imported records with a Hive/Presto query and export the results into Data Tank 2.0 with Result Export to PostgreSQL.
This must be done on a table-by-table basis.
Exporting results to PostgreSQL only exports records. If you need any objects like indexes, you need to create them. You can use any 3rd party tools like psql client, pgAdmin, etc.
There are several methods of integrating with Data Tank. Therefore, if you replace Data Tank with Data Tank 2.0, you need to update the integrations to change the destination from Data Tank to Data Tank 2.0. Examples of such scenarios are:
- Integrations importing from Data Tank
- Integrations exporting to Data Tank
- Running queries via pg>: operator of Workflow
- Any 3rd party tools integrated such Tableau
Learn more about changing integrations from Data Tank to Data Tank 2.0.