issue_comments
4 rows where issue = 33637243 and user = 2443309 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Dataset summary methods · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
43359850 | https://github.com/pydata/xarray/issues/131#issuecomment-43359850 | https://api.github.com/repos/pydata/xarray/issues/131 | MDEyOklzc3VlQ29tbWVudDQzMzU5ODUw | jhamman 2443309 | 2014-05-16T17:49:14Z | 2014-05-16T17:49:14Z | MEMBER | Both NCO and CDO keep all attributes, and as you mention, maintain a history attribute. Even for operations like "variance" where the units are no longer accurate. Maybe we're headed to a user specified option to keep the attributes around with the default being option 1. I can see this existing at any (but probably not all) of these levels:
- module ( This approach would put the onus on the user to specify they want to keep metadata around. My preference would be to apply this at the module level. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset summary methods 33637243 | |
43351948 | https://github.com/pydata/xarray/issues/131#issuecomment-43351948 | https://api.github.com/repos/pydata/xarray/issues/131 | MDEyOklzc3VlQ29tbWVudDQzMzUxOTQ4 | jhamman 2443309 | 2014-05-16T16:32:44Z | 2014-05-16T16:32:44Z | MEMBER | A couple more thoughts. I agree that staying metatdata unaware is the best course of action. However, I think you can do that but still carry the dataset and variable attributes (in the same manor that NCO and CDO do). You just want to be explicit in the documentation by saying that the attributes are from the original dataset and that xray is not attribute aware or a units system (except for the time variable I guess). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset summary methods 33637243 | |
43300537 | https://github.com/pydata/xarray/issues/131#issuecomment-43300537 | https://api.github.com/repos/pydata/xarray/issues/131 | MDEyOklzc3VlQ29tbWVudDQzMzAwNTM3 | jhamman 2443309 | 2014-05-16T06:15:03Z | 2014-05-16T06:15:03Z | MEMBER | I'm willing to take a crack at it but I'm guessing I'll be requesting some assistance along the way. Let me look into a bit and I'll report back with how I see it going together. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset summary methods 33637243 | |
43291229 | https://github.com/pydata/xarray/issues/131#issuecomment-43291229 | https://api.github.com/repos/pydata/xarray/issues/131 | MDEyOklzc3VlQ29tbWVudDQzMjkxMjI5 | jhamman 2443309 | 2014-05-16T03:06:41Z | 2014-05-16T03:07:16Z | MEMBER | I'm not sure we need to worry about the string representation too much. The To flush out some of the desired functionality a bit more:
(I'm going to use |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Dataset summary methods 33637243 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 1