issue_comments

Table actions

1 row where issue = 614149170 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 · 1 ✖

issue 1

  • open_mfdataset(paths, combine='nested') with and without concat_dim=None · 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
625523538 https://github.com/pydata/xarray/issues/4044#issuecomment-625523538 https://api.github.com/repos/pydata/xarray/issues/4044 MDEyOklzc3VlQ29tbWVudDYyNTUyMzUzOA== TomNicholas 35968931 2020-05-07T22:13:08Z 2020-05-07T22:13:08Z MEMBER

Hi @seth-p ,

Just to be sure I understand your question, are you asking why concat_dim doesn't default to None in open_mfdataset?

If so, that behaviour is there currently because it's being adapted from a previous, different behaviour, which requires a special placeholder value to give certain backwards-compatible behaviour by default.

But you raise a good point that in future, when combine='nested', the default value of concat_dim should be None, so I've pushed a commit to #3926 to ensure it will, and you should see that behaviour in the next major release.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   open_mfdataset(paths, combine='nested') with and without concat_dim=None 614149170

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