issue_comments

Table actions

1 row where issue = 252707680 and user = 306380 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

  • mrocklin · 1 ✖

issue 1

  • Consider setting name=False in Variable.chunk() · 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
324735578 https://github.com/pydata/xarray/issues/1525#issuecomment-324735578 https://api.github.com/repos/pydata/xarray/issues/1525 MDEyOklzc3VlQ29tbWVudDMyNDczNTU3OA== mrocklin 306380 2017-08-24T19:37:27Z 2017-08-24T19:37:27Z MEMBER

To be explicit, by default da.from_array currently names arrays by hashing all of the data within them. This can be somewhat slow depending on what hashing libraries you have on your machine, generally something like 500-1000 MB/s. This buys you a deterministic name for your array. If someone else with the exact same data does the exact same operations that then Dask can track that and avoid repeated work.

So you have to choose:

  1. Avoid repeated work
  2. Avoid hashing data

The choice really depends on how often you plan to repeat the same computation on the same data that comes from the same numpy array. If you only ever call a.chunk(...) once per array then there is no reason to hash.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Consider setting name=False in Variable.chunk() 252707680

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