issue_comments

Table actions

where author_association = "MEMBER", issue = 642832962 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association, issue

user 1

  • dcherian · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
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]);