issue_comments

Table actions

4 rows where issue = 48301141 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • shoyer · 4 ✖

issue 1

  • Creation of an empty DataArray · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
472176709 https://github.com/pydata/xarray/issues/277#issuecomment-472176709 https://api.github.com/repos/pydata/xarray/issues/277 MDEyOklzc3VlQ29tbWVudDQ3MjE3NjcwOQ== shoyer 1217238 2019-03-12T20:53:40Z 2019-03-12T20:53:40Z MEMBER

This hasn't been implemented yet (but would still be welcome!)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Creation of an empty DataArray 48301141
275958974 https://github.com/pydata/xarray/issues/277#issuecomment-275958974 https://api.github.com/repos/pydata/xarray/issues/277 MDEyOklzc3VlQ29tbWVudDI3NTk1ODk3NA== shoyer 1217238 2017-01-30T00:29:51Z 2017-01-30T00:29:51Z MEMBER

Given the dask integration, being able to initialize DataArrays that are chunked would be very helpful. I want to map from an old x-y-z grid to a new one, and theoretically it could be too memory intensive to keep the new grid in memory, so it would be nice to initialize an empty one and then fill it.

Dask Array recently added support for modifying arrays in place but generally this isn't recommended -- you want to create new arrays, e.g., with dask.array.atop or map_blocks.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Creation of an empty DataArray 48301141
67812697 https://github.com/pydata/xarray/issues/277#issuecomment-67812697 https://api.github.com/repos/pydata/xarray/issues/277 MDEyOklzc3VlQ29tbWVudDY3ODEyNjk3 shoyer 1217238 2014-12-22T08:26:09Z 2014-12-22T08:26:09Z MEMBER

Fixed the doc string for now, but this would still be a nice feature to add at some point.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Creation of an empty DataArray 48301141
62440542 https://github.com/pydata/xarray/issues/277#issuecomment-62440542 https://api.github.com/repos/pydata/xarray/issues/277 MDEyOklzc3VlQ29tbWVudDYyNDQwNTQy shoyer 1217238 2014-11-10T19:33:50Z 2014-11-10T19:33:50Z MEMBER

This is definitely a case where the documentation has gotten out of sync with the implementation (I used to abuse a dataset argument in DataArray.__init__ for a fastpath constructor, but now I have another method for that). The data argument is not really optional right now (unless you want a scalar DataArray containing the value None).

Your proposed functionality does sound useful. Do you want to take a crack at the implementation? The init logic for DataArray is pretty self contained, and it's all at the top of xray/core/dataarray.py. It will require a small amount of reorganization because _infer_coords_and_dims currently assumes it already knows the shape of the data.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Creation of an empty DataArray 48301141

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