issue_comments

Table actions

3 rows where issue = 642832962 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

author_association 2

issue 1

  • forward fill : transpose_coords=False · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
782936813 https://github.com/pydata/xarray/issues/4167#issuecomment-782936813 https://api.github.com/repos/pydata/xarray/issues/4167 MDEyOklzc3VlQ29tbWVudDc4MjkzNjgxMw== keewis 14808389 2021-02-21T22:12:51Z 2021-02-21T22:12:51Z MEMBER

we had a few releases since then so I assume we can close this. If you disagree, feel free to reopen.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   forward fill : transpose_coords=False 642832962
647900586 https://github.com/pydata/xarray/issues/4167#issuecomment-647900586 https://api.github.com/repos/pydata/xarray/issues/4167 MDEyOklzc3VlQ29tbWVudDY0NzkwMDU4Ng== NickMortimer 4338975 2020-06-23T04:31:10Z 2020-06-23T04:31:10Z NONE

The warning asked me to set transpose_coords=False to keep the current behavior so my default position is to do that so my code keeps working as is but ffill doesn't take transpose_coords as a parameter or does it in (#3824)?

I'm doing this inside a map_blocks call, and have already established a template and if the dims are swapped on the returned object the process fails as it cannot be combined as it doesn't match the expected template, so yes I added a transpose after the fill, but this does make things more complex as depending on how the user has subset the data the dimensions will change so that will require extra code to get the dimensions before and then to transpose after.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   forward fill : transpose_coords=False 642832962
647585666 https://github.com/pydata/xarray/issues/4167#issuecomment-647585666 https://api.github.com/repos/pydata/xarray/issues/4167 MDEyOklzc3VlQ29tbWVudDY0NzU4NTY2Ng== dcherian 2448579 2020-06-22T15:20:21Z 2020-06-22T15:20:21Z MEMBER

Thanks for filing an issue @NickMortimer .

The transpose call is here and is used because apply_ufunc moves dimensions around so that the "core dimensions" are the last. The explicit transpose then moves the dimensions back to the original order: https://github.com/pydata/xarray/blob/b9e6a36ff7a0ca3593165cf191f4152666fa4a66/xarray/core/missing.py#L405-L421

Now transpose_coords=True is the default in our next release (#3824) so this warning will disappear.

Is there a reason why you want the coordinates to not have the same dimension order as the data? In that case, I would add another transpose call after ffill in your code.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   forward fill : transpose_coords=False 642832962

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);