> For the complete documentation index, see [llms.txt](https://upsolver.gitbook.io/content/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upsolver.gitbook.io/content/quickstarts-1/data-ingestion-wizard/using-the-wizard/target-set-up/polaris-catalog.md). # Polaris Catalog ## Polaris Catalog setup guide ### **Create a new connection** Click **Create a new connection**, if it is not already selected. Fill in the following details: **URL** Polaris catalog URL. This is the endpoint where the platform will connect to access your Polaris data. Example: https\://\.snowflakecomputing.com/polaris/api/catalog. **Catalog name** The Polaris catalog name. Note, the catalog name is case sensitive. **Client ID** Polaris Client ID. This unique identifier is provided by Polaris and is required for secure authentication. **Client secret key** Polaris Secret Key. This key works with your Client ID to securely authenticate your connection to Polaris. **Principal Role** The Polaris Catalog Principal Role name. Use ALL if you are unsure. **Additional client properties (optional)** Specify any additional properties needed for your Polaris client configuration. These optional settings can include custom parameters to enhance your connection or meet specific requirements. **Connection name** Type in the name for this connection. Please note this connection will be available to other users in your organization.

Create a new connection to Polaris Catalog to use as the target for your ingestion job.

### Use an existing connection By default, if you have already created a connection, Upsolver selects **Use an existing connection**, and your Polaris Catalog connection is populated in the list. For organizations with multiple connections, select the target connection you want to use. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://upsolver.gitbook.io/content/quickstarts-1/data-ingestion-wizard/using-the-wizard/target-set-up/polaris-catalog.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.