issue_comments: 258619392

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/pull/1024#issuecomment-258619392 https://api.github.com/repos/pydata/xarray/issues/1024 258619392 MDEyOklzc3VlQ29tbWVudDI1ODYxOTM5Mg== 4160723 2016-11-05T15:37:46Z 2016-11-05T15:37:46Z MEMBER

we already cache an index in memory for any labeled indexing operations

Oh yes, true!

So at best, you could do something like ds.isel(mesh_edge=slice(int(1e6)))

Indeed, that doesn't look very nice.

For out-of-core operations with labels on big unstructured meshes, you really need a generalization of the pandas.Index that doesn't need to live in memory

From what I intend to do next with xarray, I'd say that extending its support for out-of-core operations to big indexes would be a great feature! I haven't seen yet how dask.Dataframe works internally (including dask.Dataframe.indexand dask.Dataframe.loc), but I guess maybe this could be transposed in some way to the indexing logic in xarray? Though I'm certainly missing a lot of potential issues here... Anyway, I can open a new issue to discuss more about this if you think it's worth it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   180451196