issue_comments

Table actions

1 row where issue = 1599056009 and user = 2448579 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

  • dcherian · 1 ✖

issue 1

  • Support specifying chunk sizes using labels (e.g. frequency string) · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
1444208978 https://github.com/pydata/xarray/issues/7559#issuecomment-1444208978 https://api.github.com/repos/pydata/xarray/issues/7559 IC_kwDOAMm_X85WFOFS dcherian 2448579 2023-02-24T18:27:18Z 2023-02-25T03:46:49Z MEMBER

is there anywhere else in xarray where we have made some choice about how to let the user choose between specifying via indexes or labels?

coarsen vs groupby/groupby_bins/resample.

I explored this idea in this tutorial

I think it may be a fundamental concept for labelled array analysis. You need to pick whether you're working in "index space" like unlabelled arrays, or in "label space". This also came up in this issue where shift (and roll) operate in "index space".

Another example: Alignment is in "label space", broadcasting seems like "index space" (you just change shapes, but it does use dimension names to do that so maybe 50/50).

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 1
}
   Support specifying chunk sizes using labels (e.g. frequency string) 1599056009

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