Repository navigation
Clarify event time formats and millisecond precision - #338
Open
claude[bot] wants to merge 5 commits into
Open
claude[bot] wants to merge 5 commits into
claude[bot] wants to merge 5 commits into
Conversation
- Import Events: document accepted `time` formats (epoch seconds/ms, RFC 3339 / ISO 8601 strings with fractional seconds and Z/offset) and millisecond storage precision. - Ingestion OpenAPI: /import `time` accepts number or date-time string. - Warehouse Connectors: add BigQuery note on Time column types (TIMESTAMP/DATETIME/DATE), ms precision, and view workaround. - Data types: note that the Date property format doesn't govern the event `time` property. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019z5vcGvyBsQEXLi3WSuj4b
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
 [Low impact] The PR appears safe to merge; no actionable new issue remains. Reviews (5) · Last reviewed commit: "Trim Time column description on warehous..." · Reviewed by Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
- openapi: drop `format: date-time` from the /import `time` string branch, since RFC 3339 date-time requires an offset but strings without one are accepted and treated as UTC. - warehouse-connectors: note that BigQuery Mirror doesn't support views, so write the converted Time column into a table to use Mirror. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019z5vcGvyBsQEXLi3WSuj4b
… BigQuery page - Revert data-type.mdx to main (date-type format section unchanged). - Remove the BigQuery note from the generic Warehouse Connectors overview. - Add an "Event Time Column" section to the BigQuery connector page with the column type table, precision, and view conversion guidance. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019z5vcGvyBsQEXLi3WSuj4b
…overview Move millisecond-precision guidance for the Time column to the warehouse-generic Events schema table and revert the BigQuery page. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019z5vcGvyBsQEXLi3WSuj4b
Drop the sub-millisecond truncation and epoch/string conversion notes, keeping only that Mixpanel keeps millisecond precision. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019z5vcGvyBsQEXLi3WSuj4b
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Kurby Chua · Slack thread
Before: The Import Events reference described
timeonly as "seconds or milliseconds since epoch", and the OpenAPI spec typed it as an integer. This suggested that an ISO string can't carry milliseconds or aZ, and that milliseconds require epoch time. The Warehouse Connectors overview described the Time column only as "the time at which the event occurred", with nothing on precision.After: Import Events has a short table of the accepted
timeformats: epoch in seconds or milliseconds, as an integer or float, and RFC 3339 / ISO 8601 strings with fractional seconds and aZor offset. It also says events are stored with millisecond precision, so a value like"2026-09-11T01:11:10.341Z"works as-is. On the Warehouse Connectors overview, theTimerow of the Events schema table now says, for every warehouse, that Mixpanel keeps millisecond precision from the column. The per-warehouse pages and the Data Types page are unchanged.How:
reference/import-events.mdx(properties.time formats table),openapi/ingestion.openapi.yaml(/importtimeis nowanyOfnumber or string, with an updated description) anddocs/tracking-methods/warehouse-connectors.mdx(expandedTimerow description in the Events schema table). The repo's docs CI scripts (frontmatter, code samples, links, redirects, OpenAPI) all pass locally.🤖 Generated with Claude Code
https://claude.ai/code/session_019z5vcGvyBsQEXLi3WSuj4b