issue_comments

Table actions

4 rows where issue = 173773358 and user = 2443309 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: reactions, created_at (date), updated_at (date)

user 1

  • jhamman · 4 ✖

issue 1

  • Creating unlimited dimensions with xarray.Dataset.to_netcdf · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
269510467 https://github.com/pydata/xarray/issues/992#issuecomment-269510467 https://api.github.com/repos/pydata/xarray/issues/992 MDEyOklzc3VlQ29tbWVudDI2OTUxMDQ2Nw== jhamman 2443309 2016-12-28T17:29:57Z 2016-12-28T17:29:57Z MEMBER

For those of you who are interested in this feature, I'd appreciate your feedback on #1170.

 
{
    "total_count": 1,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 1,
    "rocket": 0,
    "eyes": 0
}
   Creating unlimited dimensions with xarray.Dataset.to_netcdf 173773358
267185985 https://github.com/pydata/xarray/issues/992#issuecomment-267185985 https://api.github.com/repos/pydata/xarray/issues/992 MDEyOklzc3VlQ29tbWVudDI2NzE4NTk4NQ== jhamman 2443309 2016-12-14T23:09:50Z 2016-12-14T23:09:50Z MEMBER

All - I'm actively working on this. I have an initial implementation and will get it cleaned up here in the next few days. Stay tuned.

 
{
    "total_count": 4,
    "+1": 4,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Creating unlimited dimensions with xarray.Dataset.to_netcdf 173773358
258834200 https://github.com/pydata/xarray/issues/992#issuecomment-258834200 https://api.github.com/repos/pydata/xarray/issues/992 MDEyOklzc3VlQ29tbWVudDI1ODgzNDIwMA== jhamman 2443309 2016-11-07T13:24:20Z 2016-11-07T13:24:20Z MEMBER

@shoyer -

I played around with this a bit yesterday. I have two implementation questions: - for a dataset with multiple variables, putting the dimension encoding on the Variable easily leads to conflicts. For example, one variable's encoding may say that dimension x is unlimited while another doesn't. How should we handle these conflicts. - are we apposed to a encoding attribute on the dataset object? 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Creating unlimited dimensions with xarray.Dataset.to_netcdf 173773358
243177100 https://github.com/pydata/xarray/issues/992#issuecomment-243177100 https://api.github.com/repos/pydata/xarray/issues/992 MDEyOklzc3VlQ29tbWVudDI0MzE3NzEwMA== jhamman 2443309 2016-08-29T16:31:45Z 2016-08-29T16:31:45Z MEMBER

xref: https://github.com/pydata/xarray/issues/678

I'm also a +1 on this.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Creating unlimited dimensions with xarray.Dataset.to_netcdf 173773358

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