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/802#issuecomment-233482724,https://api.github.com/repos/pydata/xarray/issues/802,233482724,MDEyOklzc3VlQ29tbWVudDIzMzQ4MjcyNA==,17055041,2016-07-18T22:50:50Z,2016-07-18T22:50:50Z,NONE,"Mind if I ask if this will get merged into master? It looks like a lot of work went into the pull request, and the discussion + passed checks lead me to believe it could be close to going in. Is there anything a third party can do to push it across the finish line?
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,143264649
https://github.com/pydata/xarray/pull/802#issuecomment-206410319,https://api.github.com/repos/pydata/xarray/issues/802,206410319,MDEyOklzc3VlQ29tbWVudDIwNjQxMDMxOQ==,17055041,2016-04-06T14:45:17Z,2016-04-06T14:45:17Z,NONE,"This will be a great feature. I for one am really looking forward to using it.

Will this work also allow saving to/reading from hdf5 and netcdf files with a MultiIndex? If not, can you give a sketch outline of the approach you (Stephan or Benoit) would take? I assume it would involve saving the information about the MultiIndex structure in some transformed way that fits into an hdf5 file, then reconstructing it on the read. I might need to hack together something for that before MultiIndex serialization makes it into xarray, but I'd like to make sure I don't veer too far off from the real solution that will ultimately come out.
","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",,143264649