issue_comments: 330464740
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/1576#issuecomment-330464740 | https://api.github.com/repos/pydata/xarray/issues/1576 | 330464740 | MDEyOklzc3VlQ29tbWVudDMzMDQ2NDc0MA== | 206773 | 2017-09-19T08:16:43Z | 2017-09-19T08:16:43Z | NONE | @shoyer
I believe this fact is surprising for any user of integer/index/enum/classification datasets. Since its justification seems to be an implementation detail which comes at the cost of increased memory and CPU consumption I suggest documenting it in Here is how we overcome this issue by deleting the
where |
{
"total_count": 2,
"+1": 2,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
258500654 |