issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 308030789 and user = 5635139 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • max-sixty · 1 ✖

issue 1

  • rolling.mean vs rolling.construct.mean · 1 ✖

author_association 1

  • MEMBER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
375750884 https://github.com/pydata/xarray/issues/2010#issuecomment-375750884 https://api.github.com/repos/pydata/xarray/issues/2010 MDEyOklzc3VlQ29tbWVudDM3NTc1MDg4NA== max-sixty 5635139 2018-03-23T17:57:11Z 2018-03-23T17:57:11Z MEMBER

I think we need to document more clearly that min_periods option is just neglected if using construct method.

I also think we could label construct as advanced / experimental. It's extremely cool, but for traditional cases, it's probably more cool than required, and less well tested than the standard methods.

At the moment we say "You can use this for more advanced rolling operations, such as strided rolling, windowed rolling, convolution, short-time FFT, etc."; I'm imagining adding something like "For standard operations above, there is no need to use construct". Or adding an Experimental marker

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   rolling.mean vs rolling.construct.mean 308030789

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