home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

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

  • rabernat · 2 ✖

issue 1

  • Allow chunk_store argument when opening Zarr datasets · 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
649053064 https://github.com/pydata/xarray/pull/3804#issuecomment-649053064 https://api.github.com/repos/pydata/xarray/issues/3804 MDEyOklzc3VlQ29tbWVudDY0OTA1MzA2NA== rabernat 1197350 2020-06-24T20:27:56Z 2020-06-24T20:27:56Z MEMBER

Sorry for letting this hang so long. Now that https://github.com/zarr-developers/zarr-python/pull/557 has been merged and zarr 2.4.0 has been released, we should be able to finish this off.

The easiest thing would be to just require zarr > 2.4.0. However, we currently don't require zarr at all...it's an optional dependency. The code in this PR will fail for older versions of zarr. What's the best way to handle this? Having a bunch of internal checks for zarr versions feels clunky, but we've done it before.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Allow chunk_store argument when opening Zarr datasets 572251686
592097638 https://github.com/pydata/xarray/pull/3804#issuecomment-592097638 https://api.github.com/repos/pydata/xarray/issues/3804 MDEyOklzc3VlQ29tbWVudDU5MjA5NzYzOA== rabernat 1197350 2020-02-27T18:05:35Z 2020-03-02T14:40:30Z MEMBER

Fantastic, thanks @ajelenak so much for this contribution!

Two items come to mind: - [x] this will definitely need a test, just something simple to verify that the chunk_store argument works as expected - [ ] curious what will happen if you pass an actual Zarr storage object. I assume it will work fine, since these are all mutable mappings.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Allow chunk_store argument when opening Zarr datasets 572251686

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 2082.766ms · About: xarray-datasette