issue_comments

Table actions

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

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • shoyer · 1 ✖

issue 1

  • LazilyOuterIndexedArray doesn't support slicing with slice objects · 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
502289427 https://github.com/pydata/xarray/issues/3022#issuecomment-502289427 https://api.github.com/repos/pydata/xarray/issues/3022 MDEyOklzc3VlQ29tbWVudDUwMjI4OTQyNw== shoyer 1217238 2019-06-14T21:42:10Z 2019-06-14T21:42:10Z MEMBER

How does this end up getting called with dask? I don't think we pass LazilyOuterIndexedArray into dask.array.from_array() directly. For example, in xarray.Variable.chunk(), we always wrap it with ImplicitToExplicitIndexingAdapter, which should be the only object seen directly by dask: https://github.com/pydata/xarray/blob/7e4bf8623891c4e564bbaede706e1d69c614b74b/xarray/core/variable.py#L893-L895

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   LazilyOuterIndexedArray doesn't support slicing with slice objects 456239422

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