issues: 334942760
This data as json
| id | node_id | number | title | user | state | locked | assignee | milestone | comments | created_at | updated_at | closed_at | author_association | active_lock_reason | draft | pull_request | body | reactions | performed_via_github_app | state_reason | repo | type |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 334942760 | MDExOlB1bGxSZXF1ZXN0MTk2Nzg2ODQ4 | 2246 | Small error in open_zarr docs | 5635139 | closed | 0 | 3 | 2018-06-22T16:30:14Z | 2018-06-22T22:57:50Z | 2018-06-22T22:00:06Z | MEMBER | 0 | pydata/xarray/pulls/2246 | I tried setting this up on GCS as an experiment, and found there's no (also - if anyone has any experience in deploying xarray over https://github.com/dask/dask-kubernetes and GCS, I'd be interested in your experience. We're currently working with either a) BigQuery for big data or b) in-memory xarray for small data, and I was interested whether there's a way of retaining the xarray model for bigger data without too much overhead) |
{
"url": "https://api.github.com/repos/pydata/xarray/issues/2246/reactions",
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
13221727 | pull |