Skip to content
This repository has been archived by the owner on Apr 25, 2024. It is now read-only.

Hourly aggregation TimePeriod format is broken in so many ways #365

Closed
huss01 opened this issue Aug 31, 2018 — with docs.microsoft.com · 1 comment
Closed

Hourly aggregation TimePeriod format is broken in so many ways #365

huss01 opened this issue Aug 31, 2018 — with docs.microsoft.com · 1 comment

Comments

Copy link

huss01 commented Aug 31, 2018

  1. Date format is inconsistent with all other aggregation types which use YYYY-MM-DD
  2. Documented format is incorrect, the actual format is "m/d/y 12:00:00 AM|h"
  3. According to the description,"12:00:00" can be ignored. Why is it included?
  4. If a click was received between 23:00 and 23:59 on March 14, 2018 the documentation states that the TimePeriod for that would be "3/15/2018 12:00:00 AM|0". But then the date in the TimePeriod is not the date of the click. Is this really correct?

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@eric-urban
Copy link
Collaborator

@huss01 thanks for the feedback. We have updated the documentation to clarify 2) and correct 4). I agree the format issues you mentioned per 1) and 3) should be fixed in a future API version e.g., YYYY-MM-DD|h. Our team is tracking this request. Please let me know if you have any follow up questions or concerns.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants