issue_comments

Table actions

4 rows where author_association = "MEMBER" and issue = 502149236 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

issue 1

  • Add xr.unify_chunks top level method · 4 ✖

author_association 1

  • MEMBER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
538451663 https://github.com/pydata/xarray/issues/3371#issuecomment-538451663 https://api.github.com/repos/pydata/xarray/issues/3371 MDEyOklzc3VlQ29tbWVudDUzODQ1MTY2Mw== dcherian 2448579 2019-10-04T15:41:21Z 2019-10-04T15:41:21Z MEMBER

But unlike align it makes sense to unify chunks of a dataset or dataarray because two variables may be chunked differently along the same dimension.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add xr.unify_chunks top level method 502149236
538230541 https://github.com/pydata/xarray/issues/3371#issuecomment-538230541 https://api.github.com/repos/pydata/xarray/issues/3371 MDEyOklzc3VlQ29tbWVudDUzODIzMDU0MQ== shoyer 1217238 2019-10-04T04:43:36Z 2019-10-04T04:43:36Z MEMBER

I think we are coupled enough to dask that we may as well add a top-level method/function.

I would lean towards xarray.unify_chunks rather than Dataset/DataArray methods for consistency with xarray.align and xarray.broadcast.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add xr.unify_chunks top level method 502149236
538014369 https://github.com/pydata/xarray/issues/3371#issuecomment-538014369 https://api.github.com/repos/pydata/xarray/issues/3371 MDEyOklzc3VlQ29tbWVudDUzODAxNDM2OQ== dcherian 2448579 2019-10-03T16:12:04Z 2019-10-03T16:12:04Z MEMBER

OK with either

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add xr.unify_chunks top level method 502149236
538013121 https://github.com/pydata/xarray/issues/3371#issuecomment-538013121 https://api.github.com/repos/pydata/xarray/issues/3371 MDEyOklzc3VlQ29tbWVudDUzODAxMzEyMQ== max-sixty 5635139 2019-10-03T16:09:07Z 2019-10-03T16:09:07Z MEMBER

Should we have a separate namespace for backend-specific functions? Or we're coupled to dask enough that we may as well add to the top level?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Add xr.unify_chunks top level method 502149236

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