issue_comments

Table actions

1 row where issue = 1397532790 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • Saving a DataArray of datetime objects as zarr is not a lazy operation despite compute=False · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1288188522 https://github.com/pydata/xarray/issues/7132#issuecomment-1288188522 https://api.github.com/repos/pydata/xarray/issues/7132 IC_kwDOAMm_X85MyDJq shoyer 1217238 2022-10-23T19:59:28Z 2022-10-23T19:59:28Z MEMBER

This is correct -- CFDatetimeCoder.encode is not lazy, even if the inputs are Dask arrays.

We would welcome contributions to fix this. This would entail making the encode look similar to the decode method (using lazy_elemwise_func).

We would also need a fall-back method for determining appropriate time units without looking at the array values. Something like seconds since 1900-01-01T00:00:00 would probably be a reasonable choice.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Saving a DataArray of datetime objects as zarr is not a lazy operation despite compute=False 1397532790

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