issue_comments

Table actions

1 row where issue = 720315478 and user = 22542812 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

  • DerWeh · 1 ✖

issue 1

  • Dropping of unaligned Data at assignment to Dataset · 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
707800003 https://github.com/pydata/xarray/issues/4507#issuecomment-707800003 https://api.github.com/repos/pydata/xarray/issues/4507 MDEyOklzc3VlQ29tbWVudDcwNzgwMDAwMw== DerWeh 22542812 2020-10-13T14:59:36Z 2020-10-13T14:59:36Z NONE

I agree, that the given example problem is related to a tolerance.

In principle, I see the problem in the current practice of just dropping data that doesn't align. If I perform an assignment =, I do not expect to lose any data.

Another example would be assigning:

python dataset['data2'] = xr.DataArray(np.random.random(50), dims=['x'], coords={'x': np.linspace(2, 12)})

This line of code would effectively do nothing, I generate data and upon assignment it is dropped.

But this might be a bit of a physiological question, what the governing design principle is. Personally I think, an assignment should only be possible if the assigned coordinates are a subset of the dataset's coordinates.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dropping of unaligned Data at assignment to Dataset 720315478

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