home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

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

  • shoyer 1
  • dcherian 1

issue 1

  • Refactor `xr.save_mfdataset()` to automatically save an xarray object backed by dask arrays to multiple files · 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
714633238 https://github.com/pydata/xarray/issues/4527#issuecomment-714633238 https://api.github.com/repos/pydata/xarray/issues/4527 MDEyOklzc3VlQ29tbWVudDcxNDYzMzIzOA== dcherian 2448579 2020-10-22T17:06:46Z 2020-10-22T17:06:46Z MEMBER

Perhaps split_chunks()?

There was a proposal for .blocks (https://github.com/pydata/xarray/issues/3147#issuecomment-513044413) I agree that 'chunk id' would be useful. Does dask expose that somehow?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Refactor `xr.save_mfdataset()` to automatically save an xarray object backed by dask arrays to multiple files 726020233
714625909 https://github.com/pydata/xarray/issues/4527#issuecomment-714625909 https://api.github.com/repos/pydata/xarray/issues/4527 MDEyOklzc3VlQ29tbWVudDcxNDYyNTkwOQ== shoyer 1217238 2020-10-22T16:53:45Z 2020-10-22T16:53:45Z MEMBER

I agree, this does sound useful!

It might make sense to split this into a few pieces of functionality:

  1. A new helper function that splits an xarray object into separate objects for each chunk, including some representation of the "chunk id". Perhaps split_chunks()?
  2. A new higher level function that combines (1) and the existing save_mfdataset to automatically save an xarray object into multiple files. This probably should be a new function rather than using the existing save_mfdataset because the API is different.
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Refactor `xr.save_mfdataset()` to automatically save an xarray object backed by dask arrays to multiple files 726020233

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]);
Powered by Datasette · Queries took 2239.693ms · About: xarray-datasette