issue_comments

Table actions

4 rows where issue = 373955021 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

issue 1

  • Dataset-wide _FillValue · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
433141457 https://github.com/pydata/xarray/issues/2510#issuecomment-433141457 https://api.github.com/repos/pydata/xarray/issues/2510 MDEyOklzc3VlQ29tbWVudDQzMzE0MTQ1Nw== jhamman 2443309 2018-10-25T17:39:35Z 2018-10-25T17:39:35Z MEMBER

Hmmm, my notifications are coming though with quite the lag today. I just saw @shoyer's comment. Sounds like we're all on the same page.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset-wide _FillValue 373955021
433141049 https://github.com/pydata/xarray/issues/2510#issuecomment-433141049 https://api.github.com/repos/pydata/xarray/issues/2510 MDEyOklzc3VlQ29tbWVudDQzMzE0MTA0OQ== jhamman 2443309 2018-10-25T17:38:17Z 2018-10-25T17:38:17Z MEMBER

AFAIK, storing the fill value in the global attributes does not follow any widely adopted convention (e.g. CF). Certainly possible to support but since we decode one variable at a time, I'm not sure our current approach would work. I think we'd need to know if there is a convention for this or if this particular dataset is just improperly formatted.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset-wide _FillValue 373955021
433140751 https://github.com/pydata/xarray/issues/2510#issuecomment-433140751 https://api.github.com/repos/pydata/xarray/issues/2510 MDEyOklzc3VlQ29tbWVudDQzMzE0MDc1MQ== dcherian 2448579 2018-10-25T17:37:26Z 2018-10-25T17:37:26Z MEMBER

That's an easy enough solution. Thanks.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset-wide _FillValue 373955021
433129181 https://github.com/pydata/xarray/issues/2510#issuecomment-433129181 https://api.github.com/repos/pydata/xarray/issues/2510 MDEyOklzc3VlQ29tbWVudDQzMzEyOTE4MQ== shoyer 1217238 2018-10-25T17:01:15Z 2018-10-25T17:01:15Z MEMBER

I'm pretty sure this isn't CF conventions compliant :). We could definitely do this in theory but I'm not sure it's worth the trouble. You could also fix this in a preprocessing step (i.e., by setting decode_cf=False, manually copying the attributes and then using xarray.decode_cf()).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset-wide _FillValue 373955021

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