issue_comments

Table actions

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

  • xr.concat changes dtype · 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
480639727 https://github.com/pydata/xarray/issues/2870#issuecomment-480639727 https://api.github.com/repos/pydata/xarray/issues/2870 MDEyOklzc3VlQ29tbWVudDQ4MDYzOTcyNw== shoyer 1217238 2019-04-07T23:11:12Z 2019-04-07T23:11:12Z MEMBER

I suppose that this behavior has to do with NaN not available in int64 and the Datasets are not completely overlapping in the altitude dimension.

This is correct.

Alternatively, you could pre-align your data to have the same coordinate labels. Someone could pretty easily add a fill_value to xarray.align(), but this hasn't been done yet: https://github.com/pydata/xarray/issues/2876

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   xr.concat changes dtype 429835266

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