issue_comments

Table actions

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

author_association 2

issue 1

  • Ability to Pass Dask Arrays as `data` in DataArray Creation · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
739330830 https://github.com/pydata/xarray/issues/4650#issuecomment-739330830 https://api.github.com/repos/pydata/xarray/issues/4650 MDEyOklzc3VlQ29tbWVudDczOTMzMDgzMA== AyrtonB 29051639 2020-12-05T18:23:10Z 2020-12-05T18:23:10Z CONTRIBUTOR

Have started to implement this but will continue the discussion in 3929

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Ability to Pass Dask Arrays as `data` in DataArray Creation 757660307
739322106 https://github.com/pydata/xarray/issues/4650#issuecomment-739322106 https://api.github.com/repos/pydata/xarray/issues/4650 MDEyOklzc3VlQ29tbWVudDczOTMyMjEwNg== AyrtonB 29051639 2020-12-05T17:09:23Z 2020-12-05T17:09:23Z CONTRIBUTOR

Thanks, I saw dask/dask#6058 but missed #3929.

If I'm understanding you correctly there should be no problem passing a dask array for the data parameters its just the dims/coords. If the _infer_coords_and_dims method on DataArrays was adapted to check for any dask.delayed elements and compute them would that enable this functionality or are there additional blockers? Thanks for your help with this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Ability to Pass Dask Arrays as `data` in DataArray Creation 757660307
739249450 https://github.com/pydata/xarray/issues/4650#issuecomment-739249450 https://api.github.com/repos/pydata/xarray/issues/4650 MDEyOklzc3VlQ29tbWVudDczOTI0OTQ1MA== keewis 14808389 2020-12-05T13:13:01Z 2020-12-05T13:13:01Z MEMBER

As stated there and in dask/dask#6058, we would need to add a Dataset.from_dask_dataframe method which dask.dataframe could then wrap in a to_xarray method. This is currently only partially possible because we don't allow dask.array in dimension coordinates, but I guess it would be good to at least have partial support.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Ability to Pass Dask Arrays as `data` in DataArray Creation 757660307
739249390 https://github.com/pydata/xarray/issues/4650#issuecomment-739249390 https://api.github.com/repos/pydata/xarray/issues/4650 MDEyOklzc3VlQ29tbWVudDczOTI0OTM5MA== keewis 14808389 2020-12-05T13:12:32Z 2020-12-05T13:12:51Z MEMBER

Duplicate of #3929

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Ability to Pass Dask Arrays as `data` in DataArray Creation 757660307

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