issue_comments

Table actions

where issue = 1600364072 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

These facets timed out: author_association, issue

user 1

  • dcherian · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1450432902 https://github.com/pydata/xarray/issues/7560#issuecomment-1450432902 https://api.github.com/repos/pydata/xarray/issues/7560 IC_kwDOAMm_X85Wc9mG dcherian 2448579 2023-03-01T16:23:05Z 2023-03-01T16:23:27Z MEMBER

This is another case of bad defaults I think; the default is compat="no_conflicts" which for datasets with the same variables picks the first non-NaN value after first aligning them along all dimensions (with fill_value=np.nan thereby changing dtypes). This is a major increase in memory use, totally inefficient, and because it works, prevents the user from discovering concat.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xr.merge does not respect datatypes of inputs 1600364072

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