issue_comments

Table actions

1 row where issue = 621451930 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

issue 1

  • write/read to zarr subtly changes array with non-dim coord · 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
775464667 https://github.com/pydata/xarray/issues/4084#issuecomment-775464667 https://api.github.com/repos/pydata/xarray/issues/4084 MDEyOklzc3VlQ29tbWVudDc3NTQ2NDY2Nw== jbusecke 14314623 2021-02-08T21:11:39Z 2021-02-08T21:11:39Z CONTRIBUTOR

I encountered a similar problem, which I could solve by dropping all scalar non-dim coords in my dataset (works in this particular workflow of mine, but is generally not ideal). Is the solution proposed by @chrisroat general enough to be implemented? Or is there another way to avoid this situation (besides dropping the coordintates?). 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   write/read to zarr subtly changes array with non-dim coord 621451930

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