issues

Table actions

2 rows where user = 9658781 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date), closed_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
402908148 MDExOlB1bGxSZXF1ZXN0MjQ3NDg2MDYy 2706 Appending to zarr store jendrikjoe 9658781 closed 0     59 2019-01-24T21:43:02Z 2019-06-29T23:43:50Z 2019-06-29T23:43:15Z CONTRIBUTOR   0 pydata/xarray/pulls/2706

This pull request allows to append an xarray to an existing datastore. - [x] Closes #2022 - [x] Tests will be added. Wanted to get an opinion if this is what is imagined by the community - [x] Fully documented, including whats-new.rst for all changes and api.rst for new API To filter the data written to the array, the dimension over which the data will be appended has to be explicitly stated. If someone has an idea how to overcome this, I would be more than happy to incorporate the necessary changes into the PR. Cheers, Jendrik

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2706/reactions",
    "total_count": 4,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 4,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
400678252 MDU6SXNzdWU0MDA2NzgyNTI= 2689 [Feature Request] Dataset.loc should accept comparisons with a contained DataArray as key jendrikjoe 9658781 closed 0     5 2019-01-18T11:06:50Z 2019-01-22T18:12:23Z 2019-01-22T18:12:00Z CONTRIBUTOR      

Hey xarray maintainers,

first of all, I love this repository! Thanks for all your effort. I have a feature request for the .loc function of the Dataset class. I think it would be beneficial to allow comparisons with DataArrays as keys for the loc function. Obviously, this only works for DataArrays which contain the same dimensions or more than the indexer. But e.g. in the weather dataset used as the example in the docs, it would allow one to filter precipitation and temperature by longitude or latitude, or precipitation by temperature. I started implementing it, cause I required it for another use case. I would be happy to integrate it to xarray, if it is of interest.

Cheers, Jendrik

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2689/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   completed 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]);