issue_comments

Table actions

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

  • h5netcdf-engine now reads attributes with array length 1 as scalar · 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
1117276228 https://github.com/pydata/xarray/issues/6570#issuecomment-1117276228 https://api.github.com/repos/pydata/xarray/issues/6570 IC_kwDOAMm_X85CmEhE kmuehlbauer 5821660 2022-05-04T12:51:18Z 2022-05-04T12:51:18Z MEMBER

The change is somewhere between version 0.12.0 and 1.0.0 (one user says from 0.14, but I haven't verified).

It's from h5netcdf 0.14 onwards, please see https://github.com/h5netcdf/h5netcdf/blob/main/CHANGELOG.rst.

Adding the invalid_netcdf=True argument when loading does not change the behaviour.

That keyword argument is distributed verbatim to h5netcdf. It tells h5netcdf to write invalid netcdf features if there are any. This will then effectively create files which might not be readable by netcdf-c/netcdf4-python. It has no meaning for reading files.

I have tested that direct reading by h5py.File gives str, ndarray, ndarray so the change is not in the writing or h5py.

The change is in h5netcdf reading attributes, where we have aligned it with netcdf4-python.

I think updating the docs as suggested is fine.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   h5netcdf-engine now reads attributes with array length 1 as scalar 1225191984

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