issue_comments

Table actions

1 row where issue = 458236359 and user = 35968931 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • TomNicholas · 1 ✖

issue 1

  • Feature Request: Additional parallel IO format support: ASDF, ph5, or similar · 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
610116325 https://github.com/pydata/xarray/issues/3035#issuecomment-610116325 https://api.github.com/repos/pydata/xarray/issues/3035 MDEyOklzc3VlQ29tbWVudDYxMDExNjMyNQ== TomNicholas 35968931 2020-04-07T01:08:24Z 2020-04-07T06:42:15Z MEMBER

It should be possible to implement a new backend in xarray now - we've already done it for multiple file formats.

However, I suspect that if we completed the project to provide a Flexible API for Storage Backends, then the path to this would become simpler. At the moment each new storage format has to be special-cased within xarray code itself (e.g. zarr), but we want to get to a position where that I/O responsibility is delegated out to other libraries, probably via an entrypoint. Then it would be much easier (and quicker) to develop the necessary interfaces for the formats you mention.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature Request: Additional parallel IO format support: ASDF, ph5, or similar 458236359

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