issue_comments

Table actions

1 row where issue = 146287030 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association

user 1

  • shoyer · 1 ✖

issue 1

  • N-D rolling · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
208056716 https://github.com/pydata/xarray/issues/819#issuecomment-208056716 https://api.github.com/repos/pydata/xarray/issues/819 MDEyOklzc3VlQ29tbWVudDIwODA1NjcxNg== shoyer 1217238 2016-04-10T20:05:24Z 2016-04-10T20:05:24Z MEMBER

@magonser We could add support for strides, but for builtin operations like min, max, sum and mean, the implementation could not be any more efficient than doing the rolling window calculation first and then using indexing to select out the strides afterwards -- we already use one a pass algorithm (via bottleneck) that uses each data point once.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   N-D rolling 146287030

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