home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

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

  • shoyer 3
  • dcherian 1
  • crusaderky 1

issue 1

  • Add writing complex data to docs · 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
530682427 https://github.com/pydata/xarray/issues/3297#issuecomment-530682427 https://api.github.com/repos/pydata/xarray/issues/3297 MDEyOklzc3VlQ29tbWVudDUzMDY4MjQyNw== shoyer 1217238 2019-09-12T06:18:10Z 2019-09-12T06:18:10Z MEMBER

Yes, this will be in the next release. (Which will hopefully be very soon!)

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add writing complex data to docs 491215043
530022780 https://github.com/pydata/xarray/issues/3297#issuecomment-530022780 https://api.github.com/repos/pydata/xarray/issues/3297 MDEyOklzc3VlQ29tbWVudDUzMDAyMjc4MA== shoyer 1217238 2019-09-10T16:44:40Z 2019-09-10T16:44:40Z MEMBER

I opened an issue to discuss this in the CF convention issue tracker -- let's see what they think: https://github.com/cf-convention/cf-conventions/issues/204

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add writing complex data to docs 491215043
529778210 https://github.com/pydata/xarray/issues/3297#issuecomment-529778210 https://api.github.com/repos/pydata/xarray/issues/3297 MDEyOklzc3VlQ29tbWVudDUyOTc3ODIxMA== shoyer 1217238 2019-09-10T05:37:41Z 2019-09-10T05:37:41Z MEMBER

It might make sense to implement engine=“hdf5” as an alias for engine=“h5netcdf” with invalid_netcdf=True. It would certainly be a more ergonomic API.

{
    "total_count": 3,
    "+1": 3,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add writing complex data to docs 491215043
529709555 https://github.com/pydata/xarray/issues/3297#issuecomment-529709555 https://api.github.com/repos/pydata/xarray/issues/3297 MDEyOklzc3VlQ29tbWVudDUyOTcwOTU1NQ== dcherian 2448579 2019-09-09T23:47:20Z 2019-09-09T23:47:20Z MEMBER

I think the answer here is to use h5netcdf until a proper hdf5 backend is created.

It would be nice to add this to the documentation and mention h5netcdf more generally under https://xarray.pydata.org/en/stable/io.html . @DerWeh Are you up for sending in a PR?

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add writing complex data to docs 491215043
529588103 https://github.com/pydata/xarray/issues/3297#issuecomment-529588103 https://api.github.com/repos/pydata/xarray/issues/3297 MDEyOklzc3VlQ29tbWVudDUyOTU4ODEwMw== crusaderky 6213168 2019-09-09T17:38:35Z 2019-09-09T17:38:35Z MEMBER

My 2 cents:

For a proper resolution, I'd rather have the topic discussed with the NetCDF specs maintainers, so that NetCDF can just be expanded to support the same structure like HDF5. Once the format is standard, it would then be a trivial PR to h5netcdf to suppress the warning. We've already gone through the exact same process for compression algorithms other than gzip. Adding the functionality to the NetCDF C library and the python wrapper would be a completely different order of magnitude of work.

Another good alternative is to use h5netcdf forcing the malformation through, and just call the file .h5 instead of .nc 😉

If you really need to interact with (non-Python) people that are stuck on the NetCDF C library, and who for reasons I can't imagine can't switch to the HDF5 C library, I think writing two bespoke pre/postprocess functions in your code to add a dimension is the best approach.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add writing complex data to docs 491215043

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]);
Powered by Datasette · Queries took 19.053ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows