issue_comments

Table actions

1 row where issue = 675482176 and user = 6815844 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

  • fujiisoup · 1 ✖

issue 1

  • Optimize ndrolling nanreduce · 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
717572036 https://github.com/pydata/xarray/issues/4325#issuecomment-717572036 https://api.github.com/repos/pydata/xarray/issues/4325 MDEyOklzc3VlQ29tbWVudDcxNzU3MjAzNg== fujiisoup 6815844 2020-10-27T22:14:41Z 2020-10-27T22:14:41Z MEMBER

@mathause Oh, I missed this issue. Yes, this is implemented only for count.

the thing is that rolling itself is already quite complicated

Agreed. We need to clean this up.

One possible option would be to drop support of bottleneck. This does not work for nd-rolling and if we implement the nd-nanreduce, the speed should be comparable with bottleneck.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Optimize ndrolling nanreduce 675482176

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