issue_comments

Table actions

1 row where issue = 146812468 and user = 1217238 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

  • shoyer · 1 ✖

issue 1

  • Dataset.__repr__ causing dask to be computed. · 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
207556347 https://github.com/pydata/xarray/issues/820#issuecomment-207556347 https://api.github.com/repos/pydata/xarray/issues/820 MDEyOklzc3VlQ29tbWVudDIwNzU1NjM0Nw== shoyer 1217238 2016-04-08T18:56:12Z 2016-04-08T18:56:12Z MEMBER

Showing a preview of values in a dask dataset can be very convenient for interactive use, so I'm loathe to turn it off entirely. I agree that it's not always useful, though.

The current check for remote data is a complete hack that should probably be removed :).

What do you think about adding an user configurable option to disable printing lazily computed values in datasets? You could then write something like xarray.set_options(preview_lazy_data=False): http://xarray.pydata.org/en/stable/generated/xarray.set_options.html

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset.__repr__ causing dask to be computed. 146812468

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