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

SNOW-1677892, SNOW-1677897: Add support for DataFrame.tz_localize and Series.tz_localize #2398

Merged
merged 3 commits into from
Oct 4, 2024

Conversation

sfc-gh-helmeleegy
Copy link
Contributor

  1. Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

    Fixes SNOW-1677892, SNOW-1677897

  2. Fill out the following pre-review checklist:

    • I am adding a new automated test(s) to verify correctness of my new code
      • If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing
    • I am adding new logging messages
    • I am adding a new telemetry message
    • I am adding new credentials
    • I am adding a new dependency
    • If this is a new feature/behavior, I'm adding the Local Testing parity changes.
  3. Please describe how your code solves the related issue.

    Add support for DataFrame.tz_localize and Series.tz_localize.

Copy link
Contributor

@sfc-gh-nkrishna sfc-gh-nkrishna left a comment

Choose a reason for hiding this comment

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

Left some small suggestions/typo nits, but LGTM otherwise!

@@ -483,7 +483,8 @@ Methods
+-----------------------------+---------------------------------+----------------------------------+----------------------------------------------------+
| ``tz_convert`` | N | | |
+-----------------------------+---------------------------------+----------------------------------+----------------------------------------------------+
| ``tz_localize`` | N | | |
| ``tz_localize`` | P | ``axis``, ``level``, ``copy``, | |
| | | ``ambiguous``, ``nonexistent`` | |
Copy link
Contributor

Choose a reason for hiding this comment

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

qq: how did we determine what parameters are going to be skipped (not implemented)? what's the process / criteria?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good question. Initially, we want to make sure we are supporting all the default values (for parameters that do have default values). The parameter tz here for instance does not have a default value, so it has to be fully supported.

We can later add more parameter coverage, which usually happens based on customer requests. The rationale is that default values are typically the most commonly used by users.

Copy link
Contributor

@sfc-gh-jkew sfc-gh-jkew left a comment

Choose a reason for hiding this comment

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

Looks good

@sfc-gh-helmeleegy sfc-gh-helmeleegy enabled auto-merge (squash) October 4, 2024 19:31
@sfc-gh-helmeleegy sfc-gh-helmeleegy merged commit d5989d0 into main Oct 4, 2024
36 of 37 checks passed
@sfc-gh-helmeleegy sfc-gh-helmeleegy deleted the helmeleegy-SNOW-1677892 branch October 4, 2024 20:02
@github-actions github-actions bot locked and limited conversation to collaborators Oct 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants