issue_comments

Table actions

1 row where issue = 406178487 and user = 6042212 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

  • martindurant · 1 ✖

issue 1

  • `open_zarr` hangs if 's3://' at front of root s3fs string · 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
460257484 https://github.com/pydata/xarray/issues/2740#issuecomment-460257484 https://api.github.com/repos/pydata/xarray/issues/2740 MDEyOklzc3VlQ29tbWVudDQ2MDI1NzQ4NA== martindurant 6042212 2019-02-04T13:54:31Z 2019-02-04T13:54:31Z CONTRIBUTOR

Do you have any idea what is taking the extra time? s3fs ought to, in theory, treat URLs with and with the s3:// the same, but this may not have been tested with tea mapping.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `open_zarr` hangs if 's3://' at front of root s3fs string 406178487

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