-
Notifications
You must be signed in to change notification settings - Fork 48
Rolling function not working as described in the docs #1375
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
Comments
Thanks for the report! Assigning to @chelsea-lin as this week's oncall to investigate. Also, CC @sycai who I believe has been assigned a similar issue. |
Thank you. I've reassigned this to @sycai, who are already assigned on a related internal issue, 388916840. |
Any update on this? |
Hello, @wesselhuising ! We are actively filling the gaps between BigQuery Dataframe and Pandas. So far, the You can get notification via our CHANGELOG https://cloud.google.com/python/docs/reference/bigframes/latest/changelog and GitHub repository (https://github.com/googleapis/python-bigquery-dataframes). Thank you very much! |
Hey @wesselhuising ! Just want you to know that I have merged the PR: #1605 that enables time range rolling on dataframes and series. The change is expected to be shipped in our next release. Thank you very much! |
Thank you very much, that is some great news! Looking forward to the next release. |
In the docs, there is the same explanation for using rolling windows as when using Pandas. Although, in the case of BigFrames only a
int
is accepted while the docs state different. In this way, I can't use something like astr
(7d
) or atimedelta
. These options are pretty vital to the rolling method in Pandas. Is there something I am overlooking (I looked in the source code of BigFrames and it seems that only anint
is accepted as its arguments).The text was updated successfully, but these errors were encountered: