issue_comments: 507480052
This data as json
| html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | performed_via_github_app | issue |
|---|---|---|---|---|---|---|---|---|---|---|---|
| https://github.com/pydata/xarray/issues/3068#issuecomment-507480052 | https://api.github.com/repos/pydata/xarray/issues/3068 | 507480052 | MDEyOklzc3VlQ29tbWVudDUwNzQ4MDA1Mg== | 1217238 | 2019-07-02T01:15:36Z | 2019-07-02T01:15:36Z | MEMBER | The source of the problem here is that when combining objects, xarray needs to decide what coordinates should remain. Our current heuristic, which pre-dates dask support, was really designed for array in memory: we keep around coordinates if they are equal on both arguments, and remove them otherwise. In some cases we can avoid the computation, if we know that the coordinates are the same object. I am open to ideas on how to make this work better. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
462859457 |