issue_comments

Table actions

3 rows where author_association = "MEMBER", issue = 124700322 and user = 953992 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

  • jreback · 3 ✖

issue 1

  • Basic multiIndex support and stack/unstack methods · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
171503989 https://github.com/pydata/xarray/pull/702#issuecomment-171503989 https://api.github.com/repos/pydata/xarray/issues/702 MDEyOklzc3VlQ29tbWVudDE3MTUwMzk4OQ== jreback 953992 2016-01-14T02:13:04Z 2016-01-14T02:13:04Z MEMBER

makes sense about dask.array.dropna

though I think you should dropna if at all possible (or have an option at least)

it IS a bit suprising to get back the full index not sure how common that will be in practice esp if u r stacking multiple levels

finally - think about only supporting sequential stacking as it conceptually makes more sense 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Basic multiIndex support and stack/unstack methods 124700322
171422543 https://github.com/pydata/xarray/pull/702#issuecomment-171422543 https://api.github.com/repos/pydata/xarray/issues/702 MDEyOklzc3VlQ29tbWVudDE3MTQyMjU0Mw== jreback 953992 2016-01-13T20:26:03Z 2016-01-13T20:26:14Z MEMBER

hmm, is dask.array dropna not implemented? I don't see why it couldn't conceptually be done (though a bit unfamiliar with the impl) - set_index takes 'data' and makes it an 'index', so that is orthogonal. It would make a new Coordinate. reset_index would do the converse. - stack/unstack effectively take existing Coordinates and transform between them.

ok makes sense.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Basic multiIndex support and stack/unstack methods 124700322
171298177 https://github.com/pydata/xarray/pull/702#issuecomment-171298177 https://api.github.com/repos/pydata/xarray/issues/702 MDEyOklzc3VlQ29tbWVudDE3MTI5ODE3Nw== jreback 953992 2016-01-13T13:58:57Z 2016-01-13T13:58:57Z MEMBER

couple of comments: - I think the repr, though technically accurate, is a bit misleading. lists of tuples is really only useful as a MI, so why not actually indicate that - stack/unstack (as in [9]) is not idempotent, as you are reconstituting the full cartesian product of levels. This seems a bit odd though (pandas can do this because its is separately tracking what is actually in the index, via the labels), I don't think you have this though? - these ops are really analogs of set_index/reset_index, rather than stack/unstack, so might be a bit confusing (though I think I get why you are doing it this way), it makes more sense esp for multi-dim. Maybe explain this in the pandas guide?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Basic multiIndex support and stack/unstack methods 124700322

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]);