What/Why

What are you proposing?

We propose that the we add to the query request schema a timestamp field so that consumers of UBI data can know when the query was made. This timestamp field would mirror the existing timestamp field defined in the event schema:

https://o19s.github.io/ubi/docs/html/1.1.0/event.schema.html#timestamp

What users have asked for this feature?

We actually have in the OpenSearch UBI plugin that we track queries by a Unix Epoch field, so we capture the specific date time. But that is a different format than what we use for events. We also support a "date" but not a "datetime", so this needs fixing in the UBI plugin for OpenSearch anyway.

What problems are you trying to solve?

Consistency in the UBI specification and the UBI plugin, and moving to using ISO 8601 formatted time stamps everywhere to simplify down stream users of UBI data.

This bug was discovered by @alexeyrodriguez during his work to simulate UBI formatted data. Thanks @alexeyrodriguez!

Are there any breaking changes to the Spec

Yes, if you used Chorus for OpenSearch edition, then you would need to update. In the future this might cause a major version bump in the spec, but today, I think it's niche enough we use it as a chance to bump the minor version.

What is the user experience going to be?

Simpler consumption of the data.

Are there breaking changes to the User Experience?

Yes, if you used epoch formatted dates you need to switch to ISO 8601 format.

Why should it be built? Any reason not to?

Definitly let's change now before UBI becomes even more widespread ;-)/

What will it take to execute?

1. Update UBI Spec
2. Update UBI for OpenSearch Plugin schema defintion
3. Update Chorus for OPenSearch to change format of dates being sent.
4. Documentation and samples updates.

Any remaining open questions?

No.