> 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/support-1/faqs/basic-elements-of-upsolver.md).

# Basic Elements of Upsolver

Upsolver has been designed to help you build pipelines quickly and easily. Read the following FAQs to discover the basic elements of Upsolver.

### Should I code pipelines from scratch?&#x20;

Upsolver includes pipeline templates to help you get started with popular use cases, however, you can also use SQL snippets to build your own pipelines if you prefer. Templates are available under the Worksheets section, or you create a blank worksheet to write your own code. &#x20;

***

### **What are Templates?**

Pre-built templates help you to jump-start your Upsolver journey. Use templates with sample data to create a worksheet and start ingesting data. Templates include code to create data sources and target connections, tables, and jobs.&#x20;

***

### What are Worksheets?

Worksheets provide an interface for creating and submitting SQL queries, as well as performing most other DML and all DDL operations, and viewing the results as your statements complete.

***

### What's the difference between private and public Worksheets?&#x20;

In Upsolver, you will find worksheets that are:&#x20;

* **Private** - only accessible to you.&#x20;
* **Public** - visible and accessible to all users within your organization.

***

### What elements are in a Worksheet?&#x20;

The worksheet contains data source and target connections, tables, and jobs, written in familiar SQL syntax.

***

### What is the Jobs section?&#x20;

The Jobs section in Upsolver provides insights into each job and its progress. The Jobs page is helpful for monitoring and troubleshooting your jobs.&#x20;

***

### What is a Job?&#x20;

Jobs enable you to copy and transform your data. They can read from external sources and write the data into a table, or read from a table and write to another table or an external target.

***

### What is the Clusters section?&#x20;

The clusters section in the Upsolver UI provides a list of the clusters in your Upsolver environment.

***

### What is Upsolver's compute cluster?&#x20;

The compute cluster is the group of servers that provide the computing power for transforming, aggregating, and enriching the data in Upsolver. They don’t interact with outside processes.

***

### What is Upsolver's API server?&#x20;

Every time a user triggers an action that requires a response, the request interacts with the API Server.

***

### Where can I learn more about using Upsolver?&#x20;

We have a library of resources, including articles, videos, blogs, and whitepapers on our website: <https://www.upsolver.com/resources>.

***

### What is stream ordering in Upsolver pipelines?&#x20;

Upsolver handles data stream ordering based on the following rules:&#x20;

* The **ordering within each partition or shard is preserved**, as long as the number of output shards is equal to or lower than the number of input shards&#x20;
* Data is **read based on the Select statement**&#x20;
  * If a Union operator is used in the statement, the data sources will be processed based on the order in which they appear within the Union (standard ANSI SQL behavior).


---

# 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/support-1/faqs/basic-elements-of-upsolver.md?ask=<question>&goal=<endgoal>
```

`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.
