issue_comments

Table actions

1 row where issue = 642832962 and user = 4338975 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • NickMortimer · 1 ✖

issue 1

  • forward fill : transpose_coords=False · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
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

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]);