issues

Table actions

3 rows where "created_at" is on date 2019-03-14 and user = 1197350 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

type 2

state 1

repo 1

id node_id number title user state locked assignee milestone comments created_at updated_at ▲ closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
421064313 MDExOlB1bGxSZXF1ZXN0MjYxMjAyMDU2 2813 [WIP] added protect_dataset_variables_inplace to open_zarr rabernat 1197350 open 0     3 2019-03-14T14:50:15Z 2024-03-25T14:05:24Z   MEMBER   0 pydata/xarray/pulls/2813

This adds the same call to _protect_dataset_variables_inplace to open_zarr which we find in open_dataset. It wraps the arrays with indexing.MemoryCachedArray.

As far as I can tell, it does not work, in the sense that nothing is cached.

  • [ ] One possible way to close #2812
  • [ ] Tests added
  • [ ] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2813/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
421070999 MDExOlB1bGxSZXF1ZXN0MjYxMjA3MTYz 2814 [WIP] Use zarr internal LRU caching rabernat 1197350 open 0     2 2019-03-14T15:01:06Z 2024-03-25T14:00:50Z   MEMBER   0 pydata/xarray/pulls/2814

Alternative way to close #2812. This uses zarr's own caching.

In contrast to #2813, this does work.

  • [ ] Closes #2812
  • [ ] Tests added
  • [ ] Fully documented, including whats-new.rst for all changes and api.rst for new API
 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2814/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
421029352 MDU6SXNzdWU0MjEwMjkzNTI= 2812 expose zarr caching from xarray rabernat 1197350 open 0     12 2019-03-14T13:50:16Z 2022-09-14T01:33:03Z   MEMBER      

Zarr has its own internal mechanism for caching, described here: - https://zarr.readthedocs.io/en/stable/tutorial.html#distributed-cloud-storage - https://zarr.readthedocs.io/en/stable/api/storage.html#zarr.storage.LRUStoreCache

However, this capability is currently inaccessible from xarray.

I propose to add a new keyword cache=True/False to open_zarr which wraps the store in an LRUStoreCache.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2812/reactions",
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 issue

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [active_lock_reason] TEXT,
   [draft] INTEGER,
   [pull_request] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [performed_via_github_app] TEXT,
   [state_reason] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
);
CREATE INDEX [idx_issues_repo]
    ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
    ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
    ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
    ON [issues] ([user]);