issue_comments

Table actions

1 row where author_association = "MEMBER", issue = 812692450 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • ImplicitToExplicitIndexingAdapter being returned with dask unstable version · 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
784348321 https://github.com/pydata/xarray/issues/4934#issuecomment-784348321 https://api.github.com/repos/pydata/xarray/issues/4934 MDEyOklzc3VlQ29tbWVudDc4NDM0ODMyMQ== shoyer 1217238 2021-02-23T16:56:21Z 2021-02-23T16:56:21Z MEMBER

Should I make an issue with dask so this gets more eyes before they make their release (I'm told later this week)?

Yes, please!

ImplicitToExplicitIndexingAdapter is an example of an "input array" rather than a full "duck array." It's true that we don't want to eagerly convert these into NumPy arrays, since they can be lazily indexed, but on the other hand it's not an array type that users know what to deal with, so it's weird to get them back from compute().

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   ImplicitToExplicitIndexingAdapter being returned with dask unstable version 812692450

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