Skip to content

Conversation

@rok
Copy link
Member

@rok rok commented Jan 12, 2022

@github-actions
Copy link

Copy link
Member

@lidavidm lidavidm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed on other PRs we probably need to add more implicit casts for this (e.g. date32 - duration[ns] => timestamp[ns] - duration[ns] perhaps)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we add a note about temporal casting here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now that I think about it, this is kind of weird to use CommonTemporal since there isn't actually a "common" type between date32 and duration (for instance) and what we actually care about here is the common unit - maybe it's worth splitting that off separately? Since future/other uses of CommonTemporal might be 'surprised' to find that CommonTemporal(date, duration) => date instead of nullptr.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about renaming CommonTemporal to CommonResolution and returning finest time unit resolution?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

CommonTemporal is used elsewhere, but having CommonResolution alongside it makes sense.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added CommonTemporalResolution and refactored ReplaceTemporalTypes. This PR should hopefully cover all temporal casts needed for ARROW-11901.

@rok rok force-pushed the ARROW-14092 branch 2 times, most recently from bc71a08 to 7e7b417 Compare January 25, 2022 13:32
@rok
Copy link
Member Author

rok commented Jan 25, 2022

@lidavidm rebased one more time and changed back to checked_cast. Should be good to go now.

@rok rok requested a review from lidavidm January 26, 2022 14:01
@lidavidm lidavidm closed this in c4eb8dc Jan 26, 2022
@lidavidm
Copy link
Member

Sorry for the delay - time to rebase the other PRs now :) (feel free to ping me on anything that needs looking at)

@ursabot
Copy link

ursabot commented Jan 26, 2022

Benchmark runs are scheduled for baseline = 9e69ccf and contender = c4eb8dc. c4eb8dc is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️2.03% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.35% ⬆️0.3%] ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python. Runs only benchmarks with cloud = True
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants