issue_comments

Table actions

2 rows where author_association = "MEMBER" and issue = 109649145 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

issue 1

  • odo support · 2 ✖

author_association 1

  • MEMBER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
454535141 https://github.com/pydata/xarray/issues/607#issuecomment-454535141 https://api.github.com/repos/pydata/xarray/issues/607 MDEyOklzc3VlQ29tbWVudDQ1NDUzNTE0MQ== max-sixty 5635139 2019-01-15T20:15:22Z 2019-01-15T20:15:22Z MEMBER

Closing as stale, please reopen if still relevant

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   odo support 109649145
145299126 https://github.com/pydata/xarray/issues/607#issuecomment-145299126 https://api.github.com/repos/pydata/xarray/issues/607 MDEyOklzc3VlQ29tbWVudDE0NTI5OTEyNg== shoyer 1217238 2015-10-03T23:33:07Z 2015-10-03T23:33:15Z MEMBER

@mrocklin, @cpcloud, @izaid and myself have discussed this, a little bit online and mostly offline.

The trouble is figuring out how to map the xray datamodel into odo. The datashape project, which odo relies on, currently lacks any support for named axes, which makes fitting xray objects into datashape a little awkward. Likewise, xray has tick labels, which don't exist in most odo datatypes. I'm certainly not opposed to adding xray to odo, but it would need some opinionated design choices which are not immediately obvious to me.

Generally, I recommend taking a look at xray's tools for converting to/from pandas and using pandas as intermediate tool for converting to and from other formats.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   odo support 109649145

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