# Tasks

In its most basic form, any data pipeline can be thought of as a series of discrete steps that run in some sort of sequence. For example, ETL pipelines generally have three steps: extract --> transform --> load.

Prism projects are no different. A Prism project is composed of a set of tasks, and these tasks contain the brunt of the project's core logic.

## What are tasks?

In Prism, tasks can be either classes or functions. Here what they look like:

{% tabs %}
{% tab title="Class-based tasks" %}

```python
# tasks/hello_world.py

import prism.task
import prism.target

class HelloWorld(prism.task.PrismTask):
        
    def run(self, tasks, hooks):
        test_str = "Hello, world!"
        return test_str
```

{% endtab %}

{% tab title="Function-based tasks" %}

```python
# tasks/hello_world.py

from prism.decorators import task

@task()
def hello_world(tasks, hooks):
    test_str = "Hello, world!"
    return test_str
```

{% endtab %}
{% endtabs %}

We'll go into the technical details of both next.

### Class-based tasks

Tasks are classes that inherit an abstract class called `PrismTask`. There are two requirements to which all tasks must adhere:

1. Each task ***must*** have method called `run`. This method should contain all the business logic for the task, and it should return a non-null output.
2. Tasks must live in a `*.py` file in the `tasks` directory.

{% hint style="warning" %}
**Important:** the output of a task's `run` function is what's used by downstream tasks in your pipeline. The return value can be anything – a Pandas or Spark DataFrame, a Numpy array, a string, a dictionary, whatever – but *it cannot be null*. Prism will throw an error if it is.
{% endhint %}

Apart from these two conditions, feel free to structure and define your tasks however you'd like, i.e., add other class methods, class attributes, etc:

```python
# tasks/hello_world.py

from prism.task import PrismTask

class HelloWorld(PrismTask):

    def some_other_function(*args, **kwargs):
        # do something
        
    def run(self, tasks, hooks):
        test_str = "Hello, world!"
        _ = some_other_function()
        return test_str
```

As you can see, our `HelloWorld` task is lives in the `tasks` directory. It inherits the `PrismTask` class, and it contains a `run` function that returns a non-null string.

{% hint style="warning" %}
**Critical:** The `run` function has two mandatory parameters: [tasks](https://docs.runprism.com/v0.2.5/fundamentals/tasks/tasks), and [hooks](https://docs.runprism.com/v0.2.5/fundamentals/tasks/hooks). Both are critical, and Prism will throw an error if it finds a `run` function without these two parameters.
{% endhint %}

And that's it! Create a class that inherits the `PrismTask` class and implement the `run` method. Prism will take care of the rest.

{% hint style="info" %}
**Good to know:** Although user-defined tasks can be arbitrarily long or complex, it is helpful to think of them as discrete steps or objectives in your pipeline. For example, if you are creating an ETL pipeline, then you may want to split your code into three tasks: an extract task, a transform task, and a load task. 
{% endhint %}

For additional information, consult the [API reference](https://docs.runprism.com/v0.2.5/api-reference/prism.task.prismtask).

### Function-based tasks

You can also define tasks using functions rather than entire classes. There's no real difference between a function-based task and a class-based task — we created the feature so that you could work with what you're most comfortable with.

In order for a function to be a task, it must:

1. Be decorated with the `prism.decorators.task` function
2. Take two positional arguments: [tasks](https://docs.runprism.com/v0.2.5/fundamentals/tasks/tasks), and [hooks](https://docs.runprism.com/v0.2.5/fundamentals/tasks/hooks). Both are critical, and Prism will throw an error if it finds a task function without these two parameters.

As with class-based tasks, the functions must return a non-null output and tasks and must live in a `*.py` file in the `tasks` directory.

Let's take a look at our original example:

```python
# tasks/hello_world.py

from prism.decorators import task

@task()
def hello_world(tasks, hooks):
    test_str = "Hello, world!"
    return test_str 
```

The technical specifications for the `@task` decorator can be found in the [API reference](https://docs.runprism.com/v0.2.5/api-reference/task-...).