issue_comments

Table actions

2 rows where issue = 262642978 and user = 1197350 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date)

user 1

  • rabernat · 2 ✖

issue 1

  • Explicit indexes in xarray's data-model (Future of MultiIndex) · 2 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
557566798 https://github.com/pydata/xarray/issues/1603#issuecomment-557566798 https://api.github.com/repos/pydata/xarray/issues/1603 MDEyOklzc3VlQ29tbWVudDU1NzU2Njc5OA== rabernat 1197350 2019-11-22T15:07:14Z 2019-11-22T15:07:14Z MEMBER

Thanks @NowanIlfideme for your feedback.

Could you perhaps share a gist of code related to your use case?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Explicit indexes in xarray's data-model (Future of MultiIndex) 262642978
511126208 https://github.com/pydata/xarray/issues/1603#issuecomment-511126208 https://api.github.com/repos/pydata/xarray/issues/1603 MDEyOklzc3VlQ29tbWVudDUxMTEyNjIwOA== rabernat 1197350 2019-07-13T14:27:32Z 2019-07-13T14:27:32Z MEMBER

After spending a few hours on the issue tracker yesterday, it became clear to me that the issue--more flexible indexes--is a major blocker on many high-priority features going forward.

In #2639, @shoyer started to address this. In that now merged-PR, he outlined the following steps, each of which needs its own PR:

  • [x] In #2639 Indexes are recreated from coordinates every time a new DataArray or Dataset is created.
  • [ ] Refactor indexes to be propagated explicitly in xarray operations. This will facilitate future API changes, when indexes will no longer only be associated with dimensions. I will probably add some testing decorator that can be used to mark part of a test as including no creation of default indexes.
  • [ ] Add explicit entries into indexes for MultiIndex levels that are checked instead of MultiIndex variables. Still no public API changes (aside from adding more entries to .indexes).
  • [ ] Support arbitrary coordinates in indexes.

So the best way to make progress on all manner of higher-level xarray feature requests is to start working through the next three items in this list.

 
{
    "total_count": 2,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Explicit indexes in xarray's data-model (Future of MultiIndex) 262642978

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