issue_comments
4 rows where issue = 653442225 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- `xr.save_mfdataset()` doesn't honor `compute=False` argument · 4 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | performed_via_github_app | issue |
---|---|---|---|---|---|---|---|---|---|---|---|
656403217 | https://github.com/pydata/xarray/issues/4209#issuecomment-656403217 | https://api.github.com/repos/pydata/xarray/issues/4209 | MDEyOklzc3VlQ29tbWVudDY1NjQwMzIxNw== | dcherian 2448579 | 2020-07-09T23:43:17Z | 2020-07-09T23:43:17Z | MEMBER | Here's an alternative ``` python def write_block(ds, t0): if len(ds.time) > 0: fname = (ds.time[0] - t0).values.astype("timedelta64[h]").astype(int) ds.to_netcdf(f"temp/file-{fname:06d}.nc")
ds = xr.tutorial.open_dataset("air_temperature", chunks={"time": 100}) ds.map_blocks(write_block, kwargs=dict(t0=ds.time[0])).compute(scheduler="processes") ``` There are two workarounds here though.
1. The user function always has to return something.
2. We can't provide I think a cleaner API may be to have |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`xr.save_mfdataset()` doesn't honor `compute=False` argument 653442225 | |
656399210 | https://github.com/pydata/xarray/issues/4209#issuecomment-656399210 | https://api.github.com/repos/pydata/xarray/issues/4209 | MDEyOklzc3VlQ29tbWVudDY1NjM5OTIxMA== | shoyer 1217238 | 2020-07-09T23:28:30Z | 2020-07-09T23:28:30Z | MEMBER |
Well, there is certainly a case for file creation also being lazy -- it definitely is more intuitive! This was more of an oversight than an intentional omission. Metadata generally needs to be written from a single process, anyways, so we never got around to doing it with Dask. That said, there are also some legitimate use cases where it is nice to be able to eagerly write metadata only without any array data. This is what we were proposing to do with |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`xr.save_mfdataset()` doesn't honor `compute=False` argument 653442225 | |
656395121 | https://github.com/pydata/xarray/issues/4209#issuecomment-656395121 | https://api.github.com/repos/pydata/xarray/issues/4209 | MDEyOklzc3VlQ29tbWVudDY1NjM5NTEyMQ== | andersy005 13301940 | 2020-07-09T23:14:15Z | 2020-07-09T23:14:15Z | MEMBER |
Interesting... I always assumed that all operations (including file creation) were delayed. So, this is a feature and not a bug then? |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`xr.save_mfdataset()` doesn't honor `compute=False` argument 653442225 | |
656388313 | https://github.com/pydata/xarray/issues/4209#issuecomment-656388313 | https://api.github.com/repos/pydata/xarray/issues/4209 | MDEyOklzc3VlQ29tbWVudDY1NjM4ODMxMw== | shoyer 1217238 | 2020-07-09T22:50:16Z | 2020-07-09T22:50:16Z | MEMBER | The way |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
`xr.save_mfdataset()` doesn't honor `compute=False` argument 653442225 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);
user 3