issue_comments

Table actions

3 rows where issue = 484270833 and user = 35968931 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

  • TomNicholas · 3 ✖

issue 1

  • combine_by_coords fails with DataArrays · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
741908629 https://github.com/pydata/xarray/issues/3248#issuecomment-741908629 https://api.github.com/repos/pydata/xarray/issues/3248 MDEyOklzc3VlQ29tbWVudDc0MTkwODYyOQ== TomNicholas 35968931 2020-12-09T17:03:24Z 2020-12-09T17:03:24Z MEMBER

@aijams while that isn't quite how I think about it, I think that is an accurate description of what combine_by_coords does :blush:

I'm assuming the main issue here is to have combine_by_coords put a set of unnamed DataArrays into a single group and paste them together.

Yes - which involves making the assumption that these different unnamed DataArrays are actually the same physical variable, and so can be meaningfully combined into a group.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   combine_by_coords fails with DataArrays 484270833
737591086 https://github.com/pydata/xarray/issues/3248#issuecomment-737591086 https://api.github.com/repos/pydata/xarray/issues/3248 MDEyOklzc3VlQ29tbWVudDczNzU5MTA4Ng== TomNicholas 35968931 2020-12-03T01:02:46Z 2020-12-03T01:02:46Z MEMBER

Hi @max-sixty good question, and it would be nice to fix this!

I think that if we go with the scheme suggested by @dcherian for handling this issue then it answers the question I posed in #3312 - the answer being that we care more about combine_by_coords happily accepting two unnamed DataArrays than we do about it being consistent with merge by throwing an error. If we're happy with that then I think it shouldn't be too difficult to finish off the PR in #3312?

(I think that this bug mentioned in #3312 is separate, and possibly deserves its own small issue.)

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   combine_by_coords fails with DataArrays 484270833
526251545 https://github.com/pydata/xarray/issues/3248#issuecomment-526251545 https://api.github.com/repos/pydata/xarray/issues/3248 MDEyOklzc3VlQ29tbWVudDUyNjI1MTU0NQ== TomNicholas 35968931 2019-08-29T15:59:24Z 2019-08-29T15:59:24Z MEMBER

@dcherian is this a merge problem, or a combine_by_coords problem?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   combine_by_coords fails with DataArrays 484270833

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