issue_comments: 442965602

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/1603#issuecomment-442965602 https://api.github.com/repos/pydata/xarray/issues/1603 442965602 MDEyOklzc3VlQ29tbWVudDQ0Mjk2NTYwMg== 1217238 2018-11-29T19:38:34Z 2018-11-29T19:38:34Z MEMBER

It occurs to me that for the case of "multiple single indexes" along the same dimension there is no good way to use them simultaneously for indexing/reindexing at the same time. We should explicitly raise if you try to do this.

I guess we have a few options for automatic alignment with multiple single indexes, too: 1. We could only support "exact" indexing 2. We could require that aligning each index separately gives the same result

(2) seems least restrictive and is probably the right choice.

One advantage of not having MultiIndex objects as variables is that the serialization story gets simpler. The rule becomes "multi-indexes don't get saved".

What should the default behavior of set_index(['x', 'y']) without an explicit kind argument be? - Should this mean individual indexes or a combined MultiIndex? The later might be more surprising but is arguably more useful. It would make sense if the model is that set_index() always creates a single index object. - We could potentially automatically pick an index type using simple heuristics. For example, if the arguments are 1D, you get get a MultiIndex by default. If the arguments have two or more dimensions, you get a KDTree.

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