issue_comments

Table actions

2 rows where issue = 193294729 and user = 1217238 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

  • shoyer · 2 ✖

issue 1

  • Scalar coords seep into index coords · 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
268669077 https://github.com/pydata/xarray/issues/1152#issuecomment-268669077 https://api.github.com/repos/pydata/xarray/issues/1152 MDEyOklzc3VlQ29tbWVudDI2ODY2OTA3Nw== shoyer 1217238 2016-12-21T23:14:17Z 2016-12-21T23:14:17Z MEMBER

@MaximilianR Let me help clarify:

  • Currently, DataArray does not have a .variables attributes.
  • The state of a DataArray is stored in the form of variables in ._variable (an xarray.Variable) and ._coords (of type OrderedDict[Any, xarray.Variable]).
  • From a user facing API, you can get access to these variables via .variable and .coords.variables (I don't know if the later is clearly documented, but if not it should be).

So the "infinite tree of DataArrrays" only applies if you are accessing them directly via .coords, and under the covers data is represented in a pretty sane way.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Scalar coords seep into index coords 193294729
264786579 https://github.com/pydata/xarray/issues/1152#issuecomment-264786579 https://api.github.com/repos/pydata/xarray/issues/1152 MDEyOklzc3VlQ29tbWVudDI2NDc4NjU3OQ== shoyer 1217238 2016-12-05T07:41:43Z 2016-12-05T07:41:43Z MEMBER

So this definitely was intentional, according to the principle that coordinates are shared between everything in a Dataset/DataArray.

I agree that doesn't always make sense -- sometime coordinates really only describe the data variable(s), so keeping them around on coordinates merely because they contain the appropriate dimensions is inappropriate.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Scalar coords seep into index coords 193294729

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