issue_comments

Table actions

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

issue 1

  • Dataset to zarr not working with newest s3fs Storage (s3fs > 0.5.0) · 3 ✖

author_association 1

  • MEMBER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
704359408 https://github.com/pydata/xarray/issues/4478#issuecomment-704359408 https://api.github.com/repos/pydata/xarray/issues/4478 MDEyOklzc3VlQ29tbWVudDcwNDM1OTQwOA== rabernat 1197350 2020-10-06T15:40:03Z 2020-10-06T15:40:03Z MEMBER

@jhnnsrs: just a tip based on my own experience. In the code above, you are not specifying any chunks explicitly. The default is then to let zarr choose the chunk sizes. Zarr's default chunks are usually much smaller than what is optimal with cloud storage. I would recommend you explicitly chunk you array and aim for chunks around 100 MB.

Closing this as it appears to be fixed by @martindurant's quick response in fsspec / s3fs.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset to zarr not working with newest s3fs Storage (s3fs > 0.5.0) 712782711
702257613 https://github.com/pydata/xarray/issues/4478#issuecomment-702257613 https://api.github.com/repos/pydata/xarray/issues/4478 MDEyOklzc3VlQ29tbWVudDcwMjI1NzYxMw== rabernat 1197350 2020-10-01T16:38:00Z 2020-10-01T16:38:00Z MEMBER

Martin, thanks for your comments. I have read them several times but am left scratching my head as to their meaning. It would be useful if you could help identify a specific development direction to address @jhnnsrs's bug. In your best judgement, is this - a bug in xarray - a bug in dask - a bug in zarr - a bug in s3fs - some problem relating to @jhnnsrs's environment / dependencies - something else?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset to zarr not working with newest s3fs Storage (s3fs > 0.5.0) 712782711
702118079 https://github.com/pydata/xarray/issues/4478#issuecomment-702118079 https://api.github.com/repos/pydata/xarray/issues/4478 MDEyOklzc3VlQ29tbWVudDcwMjExODA3OQ== rabernat 1197350 2020-10-01T13:00:53Z 2020-10-01T13:00:53Z MEMBER

Thanks for the bug report! There were recently some big changes to s3fs. We will look into it.

cc @martindurant

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Dataset to zarr not working with newest s3fs Storage (s3fs > 0.5.0) 712782711

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