issue_comments

Table actions

2 rows where issue = 927336712 and user = 2448579 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • dcherian · 2 ✖

issue 1

  • Can't remove coordinates attribute from DataArrays · 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
866175750 https://github.com/pydata/xarray/issues/5510#issuecomment-866175750 https://api.github.com/repos/pydata/xarray/issues/5510 MDEyOklzc3VlQ29tbWVudDg2NjE3NTc1MA== dcherian 2448579 2021-06-22T17:14:34Z 2021-06-22T17:14:34Z MEMBER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't remove coordinates attribute from DataArrays  927336712
866121561 https://github.com/pydata/xarray/issues/5510#issuecomment-866121561 https://api.github.com/repos/pydata/xarray/issues/5510 MDEyOklzc3VlQ29tbWVudDg2NjEyMTU2MQ== dcherian 2448579 2021-06-22T16:07:27Z 2021-06-22T16:08:35Z MEMBER

I am not sure there is a good solution here.

As @max-sixty says, xarray does not carry around information that links a specific variable to a subset of coordinate variables (like a coordinates attribute). So in effect, all variables are associated with all coordinate variables.

We could special-case bounds variables (we do this in some places in the encoding/decoding functions) but realization will always be a problem. I think you can override it by explicitly setting the coordinates="" attribute. Perhaps .attrs["coordinates"] = None will avoid writing the attribute, if not we could make it work?

cc @DWesl 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Can't remove coordinates attribute from DataArrays  927336712

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