issue_comments

Table actions

2 rows where author_association = "MEMBER", issue = 702646191 and user = 2448579 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

  • dcherian · 2 ✖

issue 1

  • Behaviour change in xarray.Dataset.sortby/sel between dask==2.25.0 and dask==2.26.0 · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
710683863 https://github.com/pydata/xarray/issues/4428#issuecomment-710683863 https://api.github.com/repos/pydata/xarray/issues/4428 MDEyOklzc3VlQ29tbWVudDcxMDY4Mzg2Mw== dcherian 2448579 2020-10-16T22:40:50Z 2020-10-16T22:40:50Z MEMBER

@TomAugspurger @jbusecke is seeing some funny behaviour in https://github.com/jbusecke/cmip6_preprocessing/issues/58

Here's a reproducer ``` python import dask import numpy as np import xarray as xr

dask.config.set( **{ "array.slicing.split_large_chunks": True, "array.chunk-size": "24 MiB", } )

da = xr.DataArray( dask.array.random.random((10, 1000, 2000), chunks=(-1, -1, 200)), dims=["x", "y", "time"], coords={"x": [3, 4, 5, 6, 7, 9, 8, 0, 2, 1]}, ) da ```

Which is basically

python da.data[np.argsort(da.x.data), ...]

I don't understand why its rechunking when we are indexing with a list along a dimension with a single chunk...

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Behaviour change in xarray.Dataset.sortby/sel between dask==2.25.0 and dask==2.26.0 702646191
693475844 https://github.com/pydata/xarray/issues/4428#issuecomment-693475844 https://api.github.com/repos/pydata/xarray/issues/4428 MDEyOklzc3VlQ29tbWVudDY5MzQ3NTg0NA== dcherian 2448579 2020-09-16T15:17:44Z 2020-09-16T15:17:44Z MEMBER

This looks like a consequence of https://github.com/dask/dask/pull/6514 . That change helps with cases like https://github.com/pydata/xarray/issues/4112

sortby is basically an isel indexing operation; so dask is automatically rechunking to make chunks with size < the default. You could fix this by setting an appropriate value in array.chunk-size either temporarily or permanently

python with dask.config.set({"array.chunk-size": "256MiB"}): # or appropriate value ...

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Behaviour change in xarray.Dataset.sortby/sel between dask==2.25.0 and dask==2.26.0 702646191

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