home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

3 rows where author_association = "MEMBER", issue = 444510710 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date)

user 1

  • shoyer · 3 ✖

issue 1

  • Add fill_value for concat and auto_combine · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
496043263 https://github.com/pydata/xarray/pull/2964#issuecomment-496043263 https://api.github.com/repos/pydata/xarray/issues/2964 MDEyOklzc3VlQ29tbWVudDQ5NjA0MzI2Mw== shoyer 1217238 2019-05-27T00:21:02Z 2019-05-27T00:21:02Z MEMBER

Thanks @zdgriffith !

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add fill_value for concat and auto_combine 444510710
494514343 https://github.com/pydata/xarray/pull/2964#issuecomment-494514343 https://api.github.com/repos/pydata/xarray/issues/2964 MDEyOklzc3VlQ29tbWVudDQ5NDUxNDM0Mw== shoyer 1217238 2019-05-21T18:54:22Z 2019-05-21T18:54:22Z MEMBER

Just to be totally explicit then changing _auto_combine() obviously means that open_mfdataset() will have an implicit default kwarg fill_value='dtypes.NA', but if that's always the desired behaviour then that's fine.

This is the current default behavior for open_mfdataset. We could potentially had a fill_value option there, too.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add fill_value for concat and auto_combine 444510710
494488275 https://github.com/pydata/xarray/pull/2964#issuecomment-494488275 https://api.github.com/repos/pydata/xarray/issues/2964 MDEyOklzc3VlQ29tbWVudDQ5NDQ4ODI3NQ== shoyer 1217238 2019-05-21T17:39:48Z 2019-05-21T17:39:48Z MEMBER

This looks pretty safe to me. It's basically just threading down the fill_value argument.

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add fill_value for concat and auto_combine 444510710

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]);
Powered by Datasette · Queries took 2401.74ms · About: xarray-datasette