issue_comments

Table actions

2 rows where issue = 689384366 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • Dimension attrs lost when creating new variable with that dimension · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
685855523 https://github.com/pydata/xarray/issues/4393#issuecomment-685855523 https://api.github.com/repos/pydata/xarray/issues/4393 MDEyOklzc3VlQ29tbWVudDY4NTg1NTUyMw== dnowacki-usgs 13837821 2020-09-02T16:36:11Z 2020-09-02T16:37:06Z CONTRIBUTOR

Huh, I would not have expected that behavior. To my mind, it seems unwanted, but then again I don't totally follow the nuances of #2180. Thanks for the heads up. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dimension attrs lost when creating new variable with that dimension 689384366
683980088 https://github.com/pydata/xarray/issues/4393#issuecomment-683980088 https://api.github.com/repos/pydata/xarray/issues/4393 MDEyOklzc3VlQ29tbWVudDY4Mzk4MDA4OA== dcherian 2448579 2020-08-31T19:20:44Z 2020-08-31T19:20:44Z MEMBER

I think this is #2180; see https://github.com/pydata/xarray/issues/2180#issuecomment-391932929 . Basically the RHS is prioritized and the x variable gets overwritten with the version of x on the RHS.

You can avoid this by going the Variable route instead of the DataArray route:ds["y"] = ("x", range(len(ds.x))) https://xarray.pydata.org/en/stable/data-structures.html#creating-a-dataset

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dimension attrs lost when creating new variable with that dimension 689384366

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