issue_comments

Table actions

2 rows where issue = 444510710 and user = 35968931 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

  • TomNicholas · 2 ✖

issue 1

  • Add fill_value for concat and auto_combine · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
494512015 https://github.com/pydata/xarray/pull/2964#issuecomment-494512015 https://api.github.com/repos/pydata/xarray/issues/2964 MDEyOklzc3VlQ29tbWVudDQ5NDUxMjAxNQ== TomNicholas 35968931 2019-05-21T18:47:38Z 2019-05-21T18:47:53Z MEMBER

Yeah this looks fine to me - it basically bypasses all the complicated combining logic anyway.

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.

 
{
    "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
494468833 https://github.com/pydata/xarray/pull/2964#issuecomment-494468833 https://api.github.com/repos/pydata/xarray/issues/2964 MDEyOklzc3VlQ29tbWVudDQ5NDQ2ODgzMw== TomNicholas 35968931 2019-05-21T16:43:56Z 2019-05-21T16:43:56Z MEMBER

Yeah I saw this - that's fine. Probably best to do them as separate commits though no? Just depends which one gets merged first. If we merge mine first then I'm happy to review/adapt this PR to be compatible. 

{
    "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

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