issue_comments

Table actions

2 rows where issue = 329251342 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 2

issue 1

  • Simplify graph of DataArray.chunk() · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
552161968 https://github.com/pydata/xarray/issues/2214#issuecomment-552161968 https://api.github.com/repos/pydata/xarray/issues/2214 MDEyOklzc3VlQ29tbWVudDU1MjE2MTk2OA== dcherian 2448579 2019-11-10T04:34:58Z 2019-11-10T04:34:58Z MEMBER

fixed on master.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Simplify graph of DataArray.chunk() 329251342
394757138 https://github.com/pydata/xarray/issues/2214#issuecomment-394757138 https://api.github.com/repos/pydata/xarray/issues/2214 MDEyOklzc3VlQ29tbWVudDM5NDc1NzEzOA== shoyer 1217238 2018-06-05T15:38:05Z 2018-06-05T15:38:36Z MEMBER

The different is ImplicitToExplicitIndexingAdapter(array=NumpyIndexingAdapter(array=array([1, 2]))) vs array([1, 2]).

The challenge here is that xarray, unlike dask, keep very careful track of what types of indexing an array supports. This is important for working with various array storage systems, some of which support many types of indexing and some of which do not.

We should certainly add a short-cut that skips applying ImplicitToExplicitIndexingAdapter if data is a numpy.ndarray, on these lines in Variable.chunk(): https://github.com/pydata/xarray/blob/bc52f8aa64833d8c97f9ef5253b6a78c7033f521/xarray/core/variable.py#L816-L822

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Simplify graph of DataArray.chunk() 329251342

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