Skip to content

Commit

Permalink
fixup! rfc43: add new RFC for job list service
Browse files Browse the repository at this point in the history
  • Loading branch information
chu11 committed Jan 11, 2024
1 parent 2bc3287 commit 5a635d5
Showing 1 changed file with 18 additions and 22 deletions.
40 changes: 18 additions & 22 deletions spec_43.rst
Original file line number Diff line number Diff line change
Expand Up @@ -197,36 +197,32 @@ Constraint Operators
Using the constraint syntax described by RFC31, jobs can be filtered
based on the following constraint operators.

- ``userid``: Designate one or more userids (*integer*) and match jobs
submitted by those userids.
``userid``
Designate one or more userids (*integer*) and match jobs submitted by those userids.

- ``name``: Designate one or more job names (*string) and match jobs
with those job names.
``name``
Designate one or more job names (*string) and match jobs with those job names.
- ``queue``: Designate one or more queues (*string*) and match jobs
with those job queues.
``queue``
Designate one or more queues (*string*) and match jobs with those job queues.

- ``states``: Designate one or more job states (*string* or *integer*)
and match jobs in those job states. Both bitmasks (including
multiple states) and string names of the states SHALL be accepted.
``states``
Designate one or more job states (*string* or *integer*) and match jobs in those job states. Both bitmasks (including multiple states) and string names of the states SHALL be accepted.

- ``results``: Designate one or more job results (*string* or *integer*)
and match jobs with those results. Both bitmasks (including
multiple results) and string names of the results SHALL be accepted.
``results``
Designate one or more job results (*string* or *integer*) and match jobs with those results. Both bitmasks (including multiple results) and string names of the results SHALL be accepted.

- ``t_submit``, ``t_depend``, ``t_run``, ``t_cleanup``,
``t_inactive``: Designate one timestamp with a prefixed comparison
operator (*string*). The accepted comparison operators SHALL be
`>`, `<`, `>=`, and `<=`, for greater than, less than, greater than
or equal, or less than or equal. Match jobs where the respective
timestamp matches against the submitted timestamp and comparison
operator.
``t_submit``, ``t_depend``, ``t_run``, ``t_cleanup``, ``t_inactive``
Designate one timestamp with a prefixed comparison operator (*string*). The accepted comparison operators SHALL be `>`, `<`, `>=`, and `<=`, for greater than, less than, greater than or equal, or less than or equal. Match jobs where the respective timestamp matches against the submitted timestamp and comparison operator.

- ``not``: Logical negation of one constraint object.
``not``
Logical negation of one constraint object.

- ``or``: Logical or of one or more constraint objects.
``or``
Logical or of one or more constraint objects.

- ``and``: Logical and of one or more constraint objects..
``and``
Logical and of one or more constraint objects..

The following are several constraints examples.

Expand Down

0 comments on commit 5a635d5

Please sign in to comment.