issue_comments

Table actions

3 rows where author_association = "NONE", issue = 247697176 and user = 865212 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

  • acrosby · 3 ✖

issue 1

  • Reusing coordinate doesn't show in the dimensions · 3 ✖

author_association 1

  • NONE · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
517736527 https://github.com/pydata/xarray/issues/1499#issuecomment-517736527 https://api.github.com/repos/pydata/xarray/issues/1499 MDEyOklzc3VlQ29tbWVudDUxNzczNjUyNw== acrosby 865212 2019-08-02T15:08:24Z 2019-08-02T15:08:24Z NONE

I think I side with @jhamman now on this issue. Labeled access to this kind of dataarray and broadcasting operations are not useful in my cases, and working in straight numpy or pandas ends up making more sense. We just drop the appropriate variables upon opening the relevant files.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Reusing coordinate doesn't show in the dimensions 247697176
326286406 https://github.com/pydata/xarray/issues/1499#issuecomment-326286406 https://api.github.com/repos/pydata/xarray/issues/1499 MDEyOklzc3VlQ29tbWVudDMyNjI4NjQwNg== acrosby 865212 2017-08-31T12:54:22Z 2017-08-31T12:54:22Z NONE

@jhamman I'm interested in helping, but I definitely can't be timely unless we can get a project here at work that I can leverage for time. What were you thinking for test coverage?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Reusing coordinate doesn't show in the dimensions 247697176
324975826 https://github.com/pydata/xarray/issues/1499#issuecomment-324975826 https://api.github.com/repos/pydata/xarray/issues/1499 MDEyOklzc3VlQ29tbWVudDMyNDk3NTgyNg== acrosby 865212 2017-08-25T16:49:07Z 2017-08-25T16:49:07Z NONE

This is important for some of my use cases, it's something we do a lot--as noted it is not forbidden by the netcdf format or CF standards.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Reusing coordinate doesn't show in the dimensions 247697176

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