issue_comments

Table actions

1 row where issue = 382043672 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

issue 1

  • how to incorporate zarr's new open_consolidated method? · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
440163737 https://github.com/pydata/xarray/issues/2558#issuecomment-440163737 https://api.github.com/repos/pydata/xarray/issues/2558 MDEyOklzc3VlQ29tbWVudDQ0MDE2MzczNw== shoyer 1217238 2018-11-20T06:51:23Z 2018-11-20T06:51:23Z MEMBER

My proposal is to add a new keyword argument to xarray.open_zarr called consolidated (default = False)

This sounds like a pretty safe approach to me. (We could imagine later changing this to be the default behavior, if we end up deciding that we usually want to write Zarr datasets with consolidated metadata.)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   how to incorporate zarr's new open_consolidated method? 382043672

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