issue_comments

Table actions

4 rows where issue = 376953925 and user = 5308236 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

  • mschrimpf · 4 ✖

issue 1

  • single coordinate is overwritten with dimension by set_index · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
720612094 https://github.com/pydata/xarray/issues/2537#issuecomment-720612094 https://api.github.com/repos/pydata/xarray/issues/2537 MDEyOklzc3VlQ29tbWVudDcyMDYxMjA5NA== mschrimpf 5308236 2020-11-02T17:24:32Z 2020-11-02T17:24:32Z NONE

still relevant

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   single coordinate is overwritten with dimension by set_index 376953925
435676969 https://github.com/pydata/xarray/issues/2537#issuecomment-435676969 https://api.github.com/repos/pydata/xarray/issues/2537 MDEyOklzc3VlQ29tbWVudDQzNTY3Njk2OQ== mschrimpf 5308236 2018-11-04T15:04:03Z 2018-12-01T20:06:11Z NONE

I think the issue stems from this line of code. Removing it leads to the desired MultiIndex. But I'm not sure if it leads to downstream issues, e.g selecting over coord1 then seems to also squeeze that dimension. Perhaps @benbovy and @jhamman can chime in as the owners of that line.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   single coordinate is overwritten with dimension by set_index 376953925
435560123 https://github.com/pydata/xarray/issues/2537#issuecomment-435560123 https://api.github.com/repos/pydata/xarray/issues/2537 MDEyOklzc3VlQ29tbWVudDQzNTU2MDEyMw== mschrimpf 5308236 2018-11-03T04:37:52Z 2018-11-03T04:37:52Z NONE

I would expect the dimension to become a MultiIndex with a single coordinate:

<xarray.DataArray (dim: 1)> array([0]) Coordinates: * dim MultiIndex coord (dim) int64 0

When there is more than one coordinate that is what happens, but not when there is only a single coordinate.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   single coordinate is overwritten with dimension by set_index 376953925
435548784 https://github.com/pydata/xarray/issues/2537#issuecomment-435548784 https://api.github.com/repos/pydata/xarray/issues/2537 MDEyOklzc3VlQ29tbWVudDQzNTU0ODc4NA== mschrimpf 5308236 2018-11-03T01:04:50Z 2018-11-03T01:12:53Z NONE

Sorry I missed a line in the issue, added it now. You're right about the .sel -- since it does not operate on dimension levels by default, I manually set the index: d.set_index(append=True, inplace=True, dim=['coord']). However, this now gets rid of the coordinate: <xarray.DataArray (dim: 1)> array([0]) Coordinates: * dim (dim) int64 0 and thus d.sel(coord=0) does not work because the coord has been discarded.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   single coordinate is overwritten with dimension by set_index 376953925

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
);
CREATE INDEX [idx_issue_comments_issue]
    ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
    ON [issue_comments] ([user]);