issue_comments

Table actions

2 rows where issue = 991144834 and user = 25172489 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

  • derhintze · 2 ✖

issue 1

  • Coordinates have wrong number of elements after a Dataset/DataArray is split by np.split() · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
917833440 https://github.com/pydata/xarray/issues/5779#issuecomment-917833440 https://api.github.com/repos/pydata/xarray/issues/5779 IC_kwDOAMm_X842tQbg derhintze 25172489 2021-09-13T04:34:02Z 2021-09-13T04:34:02Z NONE

Yes, aux_1 (dim_1) should be split into chunks of two elements. At the same time, the coordinates aux_0 (dim_0) and * dim_0 (dim_0) should not be split at all. Even if it is not part of the API, it still is surprising that such DataArrays are created without warning or error. In other words, there isn't any check for self-consistency. I have to admit, though, that I'm not familiar with the internals of how xarray and numpy interact for these numpy array manipulation routines.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Coordinates have wrong number of elements after a Dataset/DataArray is split by np.split() 991144834
917699896 https://github.com/pydata/xarray/issues/5779#issuecomment-917699896 https://api.github.com/repos/pydata/xarray/issues/5779 IC_kwDOAMm_X842sv04 derhintze 25172489 2021-09-12T19:54:59Z 2021-09-12T19:55:30Z NONE

Thanks for asking this question to clarify! My example probably wasn't as concise as it could've been. In an attempt to improve here, I've shortened the example output a bit.

The issue isn't with the data variable content of the three split arrays, it's with the coordinates. It appears that coordinates along dim_0 have been split instead of those along dim_1. This leaves the resulting DataArrays malformed. Their coordinates do not match their corresponding dimensions in length.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Coordinates have wrong number of elements after a Dataset/DataArray is split by np.split() 991144834

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