issue_comments

Table actions

3 rows where issue = 170259709 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

issue 1

  • Skip identical indexes with non-unique values in align? · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
240470141 https://github.com/pydata/xarray/issues/956#issuecomment-240470141 https://api.github.com/repos/pydata/xarray/issues/956 MDEyOklzc3VlQ29tbWVudDI0MDQ3MDE0MQ== shoyer 1217238 2016-08-17T16:36:32Z 2016-08-17T16:36:32Z MEMBER

I just checked on xarray v0.7.2 and the example from the StackOverflow post worked. I think we should treat this as a regression -- we were already doing this prior to v0.8.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Skip identical indexes with non-unique values in align? 170259709
238737474 https://github.com/pydata/xarray/issues/956#issuecomment-238737474 https://api.github.com/repos/pydata/xarray/issues/956 MDEyOklzc3VlQ29tbWVudDIzODczNzQ3NA== shoyer 1217238 2016-08-10T00:58:45Z 2016-08-10T00:58:45Z MEMBER

I think it's important to preserve the ability to work with non-unique indexes insofar as it is necessary for cleaning your data. That's why we support non-unique indexes in merge, which is internally used anytime you assign to a Dataset. I'm less sure about the use cases for arithmetic and the like.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Skip identical indexes with non-unique values in align? 170259709
238724079 https://github.com/pydata/xarray/issues/956#issuecomment-238724079 https://api.github.com/repos/pydata/xarray/issues/956 MDEyOklzc3VlQ29tbWVudDIzODcyNDA3OQ== max-sixty 5635139 2016-08-09T23:32:01Z 2016-08-09T23:32:01Z MEMBER

Another option is to fully disallow non-unique indexes. Not sure how big a use case this is, so this might be a non-starter.

But two wondrous features of xarray: - Smaller & more defined surface than pandas, so not forced to have all these work arounds - Coords that aren't dimensions, so labels are possible in place of indexes

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Skip identical indexes with non-unique values in align? 170259709

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