Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

Several REST responses contain a timestamp field of the current time. There is no known use-case for said timestamp, makes caching of responses technically sketchy (since they differ on each call) and complicates testing since the timestamp field can't be easily predicted.

Public Interfaces

Modify the response of the following endpoints to no longer contain the "now" timestamp field:

• /jobs/:jobid
• /jobs/:jobid/vertices/:vertexid

• /jobs/:jobid/vertices/:vertexid/taskmanagers

• /jobs/:jobid/vertices/:vertexid/subtasktimes

Compatibility, Deprecation, and Migration Plan

• What impact (if any) will there be on existing users?
• It is unlikely that any business logic relies on said field. However, generated 1.x clients may reject responses due to the missing field.