issue_comments

Table actions

1 row where author_association = "MEMBER" and issue = 1328531407 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

  • min and max methods changing dtype to float64 · 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
1206194852 https://github.com/pydata/xarray/issues/6876#issuecomment-1206194852 https://api.github.com/repos/pydata/xarray/issues/6876 IC_kwDOAMm_X85H5RKk keewis 14808389 2022-08-05T08:37:28Z 2022-08-05T08:38:54Z MEMBER

I'm not sure about this, but I think the reason is that we're using bottleneck to speed up the computation, which returns a python float object for scalars. To be able to wrap it, xarray will convert it to a 0d array, which by default has a dtype of float64.

np.{min,max} returns np.float32 instances, so the dtype information is not lost with that.

To work around that, you can disable bottleneck: python xr.set_options(use_bottleneck=False)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   min and max methods changing dtype to float64 1328531407

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