issue_comments

Table actions

1 row where issue = 146287030 and user = 2443309 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

  • jhamman · 1 ✖

issue 1

  • N-D rolling · 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
206417958 https://github.com/pydata/xarray/issues/819#issuecomment-206417958 https://api.github.com/repos/pydata/xarray/issues/819 MDEyOklzc3VlQ29tbWVudDIwNjQxNzk1OA== jhamman 2443309 2016-04-06T15:04:55Z 2016-04-06T15:04:55Z MEMBER

@forman -

The main reason this isn't supported yet is that we haven't implemented it yet. I recently added the Rolling object to xarray and our initial application aimed to wrap the bottleneck moving window functions. Because the bottleneck moving window functions only supports one windowing axis, we have also adopted that constraint for now.

At this point, I don't know of any plans to extend this functionality although we could discuss further. The complexity of N-D rolling aggregations does increase a fair bit and we would ideally like to let a lower level package (e.g. bottleneck) handle most of that. Since you seem to have a tangible application for the N-D rolling feature, maybe this is something you want to contribute to?

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