issue_comments

Table actions

4 rows where issue = 851391441 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

author_association 2

issue 1

  • `to_zarr()` dramatically alters dask graph · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1102354051 https://github.com/pydata/xarray/issues/5115#issuecomment-1102354051 https://api.github.com/repos/pydata/xarray/issues/5115 IC_kwDOAMm_X85BtJaD JSKenyon 6582745 2022-04-19T09:09:57Z 2022-04-19T09:09:57Z NONE

No problem!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `to_zarr()` dramatically alters dask graph 851391441
1101963912 https://github.com/pydata/xarray/issues/5115#issuecomment-1101963912 https://api.github.com/repos/pydata/xarray/issues/5115 IC_kwDOAMm_X85BrqKI max-sixty 5635139 2022-04-19T03:46:55Z 2022-04-19T03:46:55Z MEMBER

I think so.

Sorry we didn't respond in a better way @JSKenyon — our fault.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `to_zarr()` dramatically alters dask graph 851391441
1101938491 https://github.com/pydata/xarray/issues/5115#issuecomment-1101938491 https://api.github.com/repos/pydata/xarray/issues/5115 IC_kwDOAMm_X85Brj87 dcherian 2448579 2022-04-19T02:46:11Z 2022-04-19T02:46:11Z MEMBER

This seems like an upstream issue/clarification. Shall we close?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `to_zarr()` dramatically alters dask graph 851391441
814132352 https://github.com/pydata/xarray/issues/5115#issuecomment-814132352 https://api.github.com/repos/pydata/xarray/issues/5115 MDEyOklzc3VlQ29tbWVudDgxNDEzMjM1Mg== JSKenyon 6582745 2021-04-06T13:45:55Z 2021-04-06T13:45:55Z NONE

Having done some digging, this seems to be a result of using the dask store function. It does some graph optimisation and ultimately leads to the changes to the dask graph. I am not sure if it is worth moving this discussion to dask - it seems to me that having graph optimizations happen outside a compute call is a little dangerous.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   `to_zarr()` dramatically alters dask graph 851391441

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