issue_comments

Table actions

1 row where issue = 433916353 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

issue 1

  • DataArray sum().values depends on chunk size · 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
483880786 https://github.com/pydata/xarray/issues/2902#issuecomment-483880786 https://api.github.com/repos/pydata/xarray/issues/2902 MDEyOklzc3VlQ29tbWVudDQ4Mzg4MDc4Ng== shoyer 1217238 2019-04-16T23:31:06Z 2019-04-16T23:31:06Z MEMBER

I think this would qualify as expected behavior. It is not a feature per-se, but is basically inevitable given the error inherent in floating point computation.

I'm not entirely sure it makes sense to document this in xarray -- it's really an upstream issue from dask.array. (But again, it's totally expected for dask.)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   DataArray sum().values depends on chunk size 433916353

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