issue_comments

Table actions

3 rows where issue = 309691307 and user = 1217238 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

These facets timed out: author_association

user 1

  • shoyer · 3 ✖

issue 1

  • slice using non-index coordinates · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
377318151 https://github.com/pydata/xarray/issues/2028#issuecomment-377318151 https://api.github.com/repos/pydata/xarray/issues/2028 MDEyOklzc3VlQ29tbWVudDM3NzMxODE1MQ== shoyer 1217238 2018-03-29T17:51:27Z 2018-03-29T17:51:27Z MEMBER

@maxim-lian Probably. Or you could make the pandas.Index explicitly, e.g., da.sel(a=da.c.to_index().get_indexer(['x', 'y'])).

We should really add DataArray.isin() (https://github.com/pydata/xarray/issues/1268).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   slice using non-index coordinates 309691307
377311481 https://github.com/pydata/xarray/issues/2028#issuecomment-377311481 https://api.github.com/repos/pydata/xarray/issues/2028 MDEyOklzc3VlQ29tbWVudDM3NzMxMTQ4MQ== shoyer 1217238 2018-03-29T17:28:58Z 2018-03-29T17:28:58Z MEMBER

This has some connections to the broader indexes refactor envisioned in https://github.com/pydata/xarray/issues/1603.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   slice using non-index coordinates 309691307
377311169 https://github.com/pydata/xarray/issues/2028#issuecomment-377311169 https://api.github.com/repos/pydata/xarray/issues/2028 MDEyOklzc3VlQ29tbWVudDM3NzMxMTE2OQ== shoyer 1217238 2018-03-29T17:28:14Z 2018-03-29T17:28:14Z MEMBER

we're discussed this before: https://github.com/pydata/xarray/issues/934

I agree that this would be nice to support in theory. The challenge is that we would need to create (and then possibly throw away?) a pandas.Index do to the actual indexing, or use a numpy search function like np.isin(). Neither of these are very efficient.

Conceptually, I think it makes sense to support indexing on arbitrary variables, which is simply more expensive if an index is not already set. Dimension coordinates would not be special except that they have indexes created automatically.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   slice using non-index coordinates 309691307

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