issue_comments

Table actions

4 rows where author_association = "CONTRIBUTOR", issue = 199188476 and user = 500246 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 1

  • gerritholl · 4 ✖

issue 1

  • Use masked arrays while preserving int · 4 ✖

author_association 1

  • CONTRIBUTOR · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
580761178 https://github.com/pydata/xarray/issues/1194#issuecomment-580761178 https://api.github.com/repos/pydata/xarray/issues/1194 MDEyOklzc3VlQ29tbWVudDU4MDc2MTE3OA== gerritholl 500246 2020-01-31T14:42:36Z 2020-01-31T14:42:36Z CONTRIBUTOR 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use masked arrays while preserving int 199188476
457220076 https://github.com/pydata/xarray/issues/1194#issuecomment-457220076 https://api.github.com/repos/pydata/xarray/issues/1194 MDEyOklzc3VlQ29tbWVudDQ1NzIyMDA3Ng== gerritholl 500246 2019-01-24T14:40:33Z 2019-01-24T14:40:33Z CONTRIBUTOR

@max-sixty Interesting! I wonder what it would take to make use of this "nullable integer data type" in xarray. It wouldn't work to convert it to a standard numpy array (da.values) retaining the dtype, but one could make a new .to_maskedarray() method returning a numpy masked array; that would probably be easier than to add full support for masked arrays.

 
{
    "total_count": 4,
    "+1": 4,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use masked arrays while preserving int 199188476
457159560 https://github.com/pydata/xarray/issues/1194#issuecomment-457159560 https://api.github.com/repos/pydata/xarray/issues/1194 MDEyOklzc3VlQ29tbWVudDQ1NzE1OTU2MA== gerritholl 500246 2019-01-24T11:10:46Z 2019-01-24T11:10:46Z CONTRIBUTOR

I think this issue should remain open. I think it would still be highly desirable to implement support for true masked arrays, such that any value can be masked without throwing away the original value. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use masked arrays while preserving int 199188476
271077863 https://github.com/pydata/xarray/issues/1194#issuecomment-271077863 https://api.github.com/repos/pydata/xarray/issues/1194 MDEyOklzc3VlQ29tbWVudDI3MTA3Nzg2Mw== gerritholl 500246 2017-01-07T11:24:49Z 2017-01-07T11:32:06Z CONTRIBUTOR

I don't see how an integer dtype could ever support missing values; float missing values are specifically defined by IEEE 754 but for ints, every sequence of bits corresponds to a valid value. OTOH, NetCDF does have a _FillValue attribute that works for any type including int. If we view xarray as "NetCDF in memory" that could be an approach to follow, but for numpy in general it would fairly heavily break existing code (see also http://www.numpy.org/NA-overview.html) in particular for 8-bit types. If i understand correctly, R uses INT_MAX which would be 127 for 'int8… Apparently, R ints are always 32 bits. I'm new to xarray so I don't have a good idea on how much work adding support for masked arrays would be, but I'll take your word that it's not straightforward.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Use masked arrays while preserving int 199188476

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