Documentation bug: Batch.Client.list_jobs

0

The documentation for list_jobs claims the following:

createdAt (integer) – The Unix timestamp (in milliseconds) for when the job was created.

But in fact, observation shows, the time is actually delivered in microseconds. Dividing by 1000 gets the kind of answer that other software expects for a timestamp.

asked 6 months ago181 views
1 Answer
0

Greetings!

As mentioned in the documentations [1], the createdAt shows an integer which shows the Unix timestamp (in milliseconds) for when the job was created. For non-array jobs and parent array jobs, this is when the job entered the SUBMITTED state (at the time SubmitJob was called). For array child jobs, this is when the child job was spawned by its parent and entered the PENDING state.

Thank You!

Reference:

[1] https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/batch/client/list_jobs.html

AWS
Asha_O
answered 6 months ago
  • Yes, but OBSERVATION shows that the time is actually being delivered in MICROSECONDS, not MILLISECONDS as stated in the paragraph above. I believe the paragraph above needs to be corrected because in fact createdAt does NOT adhere to the UNIX timestamp standard.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions