issue_comments

Table actions

2 rows where issue = 148765426 and user = 4295853 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

  • pwolfram · 2 ✖

issue 1

  • keep_attrs for Dataset.resample and DataArray.resample · 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
210685190 https://github.com/pydata/xarray/issues/825#issuecomment-210685190 https://api.github.com/repos/pydata/xarray/issues/825 MDEyOklzc3VlQ29tbWVudDIxMDY4NTE5MA== pwolfram 4295853 2016-04-15T23:36:54Z 2016-04-15T23:36:54Z CONTRIBUTOR

Thanks @jhamman. You are correct that this could get challenging without proper notions of units. Do we have a utility to transfer attributes from one Dataset to another? If not, perhaps that is the simplest, short term resolution to this issue that is even more general than addition of a keep_attrs flag. I don't think it would be to hard to write although it may be out of xarray scope. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   keep_attrs for Dataset.resample and DataArray.resample 148765426
210647514 https://github.com/pydata/xarray/issues/825#issuecomment-210647514 https://api.github.com/repos/pydata/xarray/issues/825 MDEyOklzc3VlQ29tbWVudDIxMDY0NzUxNA== pwolfram 4295853 2016-04-15T21:10:36Z 2016-04-15T21:10:36Z CONTRIBUTOR

@mcgibbon, I would agree that in general attributes should be preserved to maintain provenance of DataArrays or Datasets unless there is a really good reason to drop them. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   keep_attrs for Dataset.resample and DataArray.resample 148765426

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