issue_comments

Table actions

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

  • Feature proposal: DataArray.to_zarr() · 5 ✖

author_association 1

  • MEMBER · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1487909969 https://github.com/pydata/xarray/issues/7692#issuecomment-1487909969 https://api.github.com/repos/pydata/xarray/issues/7692 IC_kwDOAMm_X85Yr7RR TomNicholas 35968931 2023-03-29T03:57:40Z 2023-03-29T03:57:40Z MEMBER

:+1: to not having to write to_dataset before saving things.

I think the .to_X vs e.g. .save(engine='X') is important enough that we should think about it a bit more. The response to #7496 doesn't seem conclusive to me (yet).

A twitter poll? Then a discussion in a meeting?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature proposal: DataArray.to_zarr() 1644429340
1487709306 https://github.com/pydata/xarray/issues/7692#issuecomment-1487709306 https://api.github.com/repos/pydata/xarray/issues/7692 IC_kwDOAMm_X85YrKR6 jhamman 2443309 2023-03-28T22:58:30Z 2023-03-28T22:58:30Z MEMBER

Fair enough. I was extrapolating a bit based on the response to #7496. If someone wants to bite off the writable backends task, I'm all for it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature proposal: DataArray.to_zarr() 1644429340
1487609291 https://github.com/pydata/xarray/issues/7692#issuecomment-1487609291 https://api.github.com/repos/pydata/xarray/issues/7692 IC_kwDOAMm_X85Yqx3L keewis 14808389 2023-03-28T21:21:47Z 2023-03-28T21:21:47Z MEMBER

As far as I understand #5954 and the meeting notes, we didn't decide anything about that yet (I might be wrong, though). So I assume the only reason we don't have write backends and save_dataset / save_dataarray right now is that nobody got around to doing that yet.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature proposal: DataArray.to_zarr() 1644429340
1487524043 https://github.com/pydata/xarray/issues/7692#issuecomment-1487524043 https://api.github.com/repos/pydata/xarray/issues/7692 IC_kwDOAMm_X85YqdDL jhamman 2443309 2023-03-28T20:04:35Z 2023-03-28T20:04:35Z MEMBER

I was once a fan of the save_dataset route but I think we've opted to stick with the format specific to_ methods. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature proposal: DataArray.to_zarr() 1644429340
1487433218 https://github.com/pydata/xarray/issues/7692#issuecomment-1487433218 https://api.github.com/repos/pydata/xarray/issues/7692 IC_kwDOAMm_X85YqG4C keewis 14808389 2023-03-28T18:44:39Z 2023-03-28T18:44:39Z MEMBER

I guess the alternative would be to go with xr.save_dataset / xr.save_dataarray, but that seems like a lot of work (and I agree that since we already have Dataset.to_zarr we can also have DataArray.to_zarr)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature proposal: DataArray.to_zarr() 1644429340

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