issue_comments

Table actions

3 rows where issue = 278389733 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 3

author_association 3

issue 1

  • Opposite of `drop_variables` option in `open_dataset()` · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
554054228 https://github.com/pydata/xarray/issues/1754#issuecomment-554054228 https://api.github.com/repos/pydata/xarray/issues/1754 MDEyOklzc3VlQ29tbWVudDU1NDA1NDIyOA== stale[bot] 26384082 2019-11-14T19:58:51Z 2019-11-14T19:58:51Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opposite of `drop_variables` option in `open_dataset()` 278389733
351787267 https://github.com/pydata/xarray/issues/1754#issuecomment-351787267 https://api.github.com/repos/pydata/xarray/issues/1754 MDEyOklzc3VlQ29tbWVudDM1MTc4NzI2Nw== shoyer 1217238 2017-12-14T17:53:57Z 2017-12-14T17:53:57Z MEMBER

I'm reluctant to add yet another keyword argument to open_dataset, but we're started refactoring xarray's internal system for decoding metadata netCDF files (https://github.com/pydata/xarray/pull/1752), and with any luck that would provide a natural way to custom this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opposite of `drop_variables` option in `open_dataset()` 278389733
351590950 https://github.com/pydata/xarray/issues/1754#issuecomment-351590950 https://api.github.com/repos/pydata/xarray/issues/1754 MDEyOklzc3VlQ29tbWVudDM1MTU5MDk1MA== snowman2 8699967 2017-12-14T02:37:19Z 2017-12-14T02:37:19Z CONTRIBUTOR

I second this request. I have had this same need before where I don't always know what variables I don't want, but I do know the variables that I do want.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Opposite of `drop_variables` option in `open_dataset()` 278389733

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