Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support configurable output timezone in pre_transform_spec #116

Merged
merged 37 commits into from
May 28, 2022

Conversation

jonmmease
Copy link
Collaborator

@jonmmease jonmmease commented May 27, 2022

This PR adds a new argument to pre_transform_spec called output_tz. This argument overrides the timezone that local datetime values are converted to before being stored in the pre-transformed spec as naive date strings. When not provided, output_tz defaults to local_tz, which matches the existing behavior.

Along the way, i needed to update the DataFusion revision to capture the fix in apache/datafusion#2463.

I also ran into windows CI issues that seem to have boiled down to the builds running out of space. What finally solved it was moving the build target directories to the large C:\ drive.

When true, datasets with inline values are extracted onto the server spec.
When false, these datasets are left in the client spec.

When performing pre_transform_spec on the server, it's preferable to set this
to true. But if planning is done on the client, then the past default of false
is more appropriate.
This format is found throughout the vega-lite examples
Vega skips over the bad values since each row can have a different type.
When arrow reads this the values column is inferred as String type,
and all of the numeric values are read as null.
Explanation: The way arrow parses this is for the datum.options.price to be null,
but not datum.options.
Vega fails when this is present in the pre-transformed version
of the spec.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant