issue_comments

Table actions

3 rows where issue = 331415995 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

  • Zarr Backend: check for non-uniform chunks is too strict · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
396748317 https://github.com/pydata/xarray/issues/2225#issuecomment-396748317 https://api.github.com/repos/pydata/xarray/issues/2225 MDEyOklzc3VlQ29tbWVudDM5Njc0ODMxNw== shoyer 1217238 2018-06-12T21:59:19Z 2018-06-12T21:59:19Z MEMBER

I think zarr also requires that the last chunk is no larger than the previous chunks.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Zarr Backend: check for non-uniform chunks is too strict 331415995
396649675 https://github.com/pydata/xarray/issues/2225#issuecomment-396649675 https://api.github.com/repos/pydata/xarray/issues/2225 MDEyOklzc3VlQ29tbWVudDM5NjY0OTY3NQ== jhamman 2443309 2018-06-12T16:20:38Z 2018-06-12T16:20:38Z MEMBER

Is this check enough:

python if any(len(set(chunks[:-1])) > 1 for chunks in var_chunks): raise ValueError( "Zarr requires uniform chunk sizes excpet for final chunk." " Variable %r has incompatible chunks. Consider " "rechunking using `chunk()`." % (var_chunks,))

where

python var_chunks = da.chunks

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Zarr Backend: check for non-uniform chunks is too strict 331415995
396454242 https://github.com/pydata/xarray/issues/2225#issuecomment-396454242 https://api.github.com/repos/pydata/xarray/issues/2225 MDEyOklzc3VlQ29tbWVudDM5NjQ1NDI0Mg== shoyer 1217238 2018-06-12T03:28:18Z 2018-06-12T03:28:18Z MEMBER

Yes, this is too strict. It looks like we wrote the code with the right intent here, but it only allows a single last chunk over all dimensions to have a different shape, not the last chunk along each dimension.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Zarr Backend: check for non-uniform chunks is too strict 331415995

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