issue_comments

Table actions

3 rows where author_association = "NONE" and issue = 514077742 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 1

  • Keep index dimension when selecting only a single coord · 3 ✖

author_association 1

  • NONE · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
788661534 https://github.com/pydata/xarray/issues/3458#issuecomment-788661534 https://api.github.com/repos/pydata/xarray/issues/3458 MDEyOklzc3VlQ29tbWVudDc4ODY2MTUzNA== cvoivret 7123715 2021-03-02T06:48:08Z 2021-03-02T06:48:08Z NONE

Hi, I'm new to OSS and I would like to take this issue. After some digging, the initial question seems to be related to vectorized indexing. We could add in a code block multiple ways to extract a column (and keep the second dimension) in the beginning of the section. It is rather specific example but, as @dcherian say, it comes up oftten enough. I can make it if the issue still matter.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Keep index dimension when selecting only a single coord 514077742
557476617 https://github.com/pydata/xarray/issues/3458#issuecomment-557476617 https://api.github.com/repos/pydata/xarray/issues/3458 MDEyOklzc3VlQ29tbWVudDU1NzQ3NjYxNw== NowanIlfideme 2067093 2019-11-22T10:21:08Z 2019-11-22T10:21:08Z NONE

Note that this doesn't work on MultiIndex levels, since vectorized operations on them are not currently supported. Meanwhile, using sel(multiindex_level_name="a") drops the level from the multiindex entirely. The running theme is that this is dependent on #1603, it seems. :)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Keep index dimension when selecting only a single coord 514077742
547577441 https://github.com/pydata/xarray/issues/3458#issuecomment-547577441 https://api.github.com/repos/pydata/xarray/issues/3458 MDEyOklzc3VlQ29tbWVudDU0NzU3NzQ0MQ== ngreenwald 13770365 2019-10-29T18:54:42Z 2019-10-29T18:54:42Z NONE

Great, thanks so much!

On Tue, Oct 29, 2019 at 11:20 AM Deepak Cherian notifications@github.com wrote:

We should add this to the documentation since it comes up often enough.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/pydata/xarray/issues/3458?email_source=notifications&email_token=ADJB47PJGAKVFXIPKCOVBTDQRB5HJA5CNFSM4JGMJOP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECRSJQQ#issuecomment-547562690, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADJB47NCROANMZGIJCOCTFLQRB5HJANCNFSM4JGMJOPQ . 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Keep index dimension when selecting only a single coord 514077742

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