NAME
    gcloud alpha dataproc jobs list - list jobs in a project

SYNOPSIS
    gcloud alpha dataproc jobs list [--cluster=CLUSTER] [--region=REGION]
        [--state-filter=STATE_FILTER] [--filter=EXPRESSION] [--limit=LIMIT]
        [--page-size=PAGE_SIZE; default=100] [--sort-by=[FIELD,...]]
        [GCLOUD_WIDE_FLAG ...]

DESCRIPTION
    (ALPHA) List jobs in a project. An optional filter can be used to constrain
    the jobs returned. Filters are case-sensitive and have the following
    syntax:

        [field = value] AND [field [= value]] ...

    where field is status.state or labels.[KEY], and [KEY] is a label key.
    value can be * to match all values. status.state can be either ACTIVE or
    INACTIVE. Only the logical AND operator is supported; space-separated items
    are treated as having an implicit AND operator.

EXAMPLES
    To see the list of all jobs in Dataproc's 'us-central1' region, run:

        $ gcloud alpha dataproc jobs list --region=us-central1

    To see a list of all active jobs in cluster 'mycluster' with a label
    env=staging located in 'us-central1', run:

        $ gcloud alpha dataproc jobs list --region=us-central1 \
            --filter='status.state = ACTIVE AND
            placement.clusterName = 'mycluster' AND labels.env = staging'

FLAGS
     --cluster=CLUSTER
        Restrict to the jobs of this Dataproc cluster.

     --region=REGION
        Dataproc region to use. Each Dataproc region constitutes an independent
        resource namespace constrained to deploying instances into Compute
        Engine zones inside the region. Overrides the default dataproc/region
        property value for this command invocation.

     --state-filter=STATE_FILTER
        Filter by job state. STATE_FILTER must be one of: active, inactive.

LIST COMMAND FLAGS
     --filter=EXPRESSION
        Apply a Boolean filter EXPRESSION to each resource item to be listed.
        If the expression evaluates True, then that item is listed. For more
        details and examples of filter expressions, run $ gcloud topic filters.
        This flag interacts with other flags that are applied in this order:
        --flatten, --sort-by, --filter, --limit.

     --limit=LIMIT
        Maximum number of resources to list. The default is unlimited. This
        flag interacts with other flags that are applied in this order:
        --flatten, --sort-by, --filter, --limit.

     --page-size=PAGE_SIZE; default=100
        Some services group resource list output into pages. This flag
        specifies the maximum number of resources per page. The default is 100.
        Paging may be applied before or after --filter and --limit depending on
        the service.

     --sort-by=[FIELD,...]
        Comma-separated list of resource field key names to sort by. The
        default order is ascending. Prefix a field with ``~'' for descending
        order on that field. This flag interacts with other flags that are
        applied in this order: --flatten, --sort-by, --filter, --limit.

GCLOUD WIDE FLAGS
    These flags are available to all commands: --access-token-file, --account,
    --billing-project, --configuration, --flags-file, --flatten, --format,
    --help, --impersonate-service-account, --log-http, --project, --quiet,
    --trace-token, --user-output-enabled, --verbosity.

    Run $ gcloud help for details.

NOTES
    This command is currently in alpha and might change without notice. If this
    command fails with API permission errors despite specifying the correct
    project, you might be trying to access an API with an invitation-only early
    access allowlist. These variants are also available:

        $ gcloud dataproc jobs list

        $ gcloud beta dataproc jobs list

