Follow these steps to use Tabular as your target.

Step 1 - Connect to Tabular

Create a new connection

Click Create a new connection, if it is not already selected.

In the Name your connection field, type in the name for this connection. Please note this connection will be available to other users in your organization.

For the Warehouse Name field, specify the name of a Tabular warehouse you'd like to write your data to, as it appears in Tabular's UI. In Tabular, warehouses are the top-level data storage resource comprised of a set of databases and tables. A warehouse is associated with a single S3 bucket which provides the storage location for all of its tables.

In Tabular, go to connectionssecurity. Define a new entry under Service Accounts. Copy the credential generated by Tabular and past it in the Credentials field.

Set the storage location where target tables will be stored in the S3 Target Bucket field using the format:


Use an existing connection

By default, if you have already created a connection, Upsolver selects Use an existing connection, and your Tabular connection is populated in the list.

For organizations with multiple connections, select the target connection you want to use.

Step 2 - Configure AWS access

In order for Upsolver to access the catalog and write to the target bucket, follow the AWS configuration assistant link.

For the Authentication Method, we recommend to use Role-based access. Paste the ARN from the role you created in AWS IAM into the Role ARN field, as explained in the configuration guide.

If using AccessKey/Secret Key, ensure the user provided to Upsolver has the necessary permissions to access AWS Glue Data Catalog and Amazon S3, as explained in the configuration guide.

Step 3 - Select where to ingest the data

Next, configure the mapping of your source schemas to your target Tabular databases. Upsolver automatically creates new tables in the selected target databases.

Firstly, define a default target database. This will be the database to which all tables from all schemas will be replicated, unless specific manual mappings are defined.

When ingesting multiple source schemas into Tabular, you have the following options:

  1. Ingest all tables into a single Tabular database and prepend the source schema name to every new table created in the Tabular Catalog. Use the prefix {source\_schema}\_ for this purpose.

  2. Map each source schema to a corresponding target database in Tabular.