issues

Table actions

2 rows where repo = 13221727, type = "pull" and user = 8982598 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 1

  • pull · 2 ✖

state 1

repo 1

  • xarray · 2 ✖
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
326834855 MDExOlB1bGxSZXF1ZXN0MTkwNzk4NTYw 2189 docs: add xyzpy to projects jcmgray 8982598 closed 0     1 2018-05-27T17:38:44Z 2018-05-27T20:46:07Z 2018-05-27T20:45:38Z CONTRIBUTOR   0 pydata/xarray/pulls/2189

Justs adds xyzpy to the list of projects utilizing xarray.

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/2189/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     xarray 13221727 pull
174404136 MDExOlB1bGxSZXF1ZXN0ODM1NDgwNzU= 996 add 'no_conflicts' as compat option for merging non-conflicting data jcmgray 8982598 closed 0     8 2016-08-31T23:38:00Z 2016-09-15T16:07:16Z 2016-09-15T16:07:16Z CONTRIBUTOR   0 pydata/xarray/pulls/996

This solves #742 and partially #835 (does not address a combine_first option yet). It essentially adds a notnull_equals method to Variable (and currently DataArray/set) that merge can use to compare objects, subsequently combining them with 'fillna'. Used as such:

``` python

import xarray as xr ds1 = xr.Dataset(data_vars={'x': ('a', [1, 2])}) ds2 = xr.Dataset(data_vars={'x': ('a', [2, 3])}, coords={'a': [1, 2]}) xr.merge([ds1, ds2], compat='notnull_equals') <xarray.Dataset> Dimensions: (a: 3) Coordinates: * a (a) int64 0 1 2 Data variables: x (a) float64 1.0 2.0 3.0 ```

Should be very easy to add other merging options such as overwriting left to write and vice versa.

TODO

  • docs
  • tests for various type combinations
  • some of the error excepting is mirrored from equals and might not be necessary (e.g. for numpy structured arrays).

ISSUES

  • It seemed natural to add notnull_equals as a method to Dataset, but it might be unnecessary/not useful. Current version is conservative in that it still requires aligned Datasets with all the same variables.
  • Due to the float nature of NaN, type is sometimes not preserved, e.g. merging two int arrays yields a float array, even when the final array has no NaN values itself.
  • float rounding errors can cause unintended failures, so a notnull_allclose option might be nice.

Currently all tests passing (6 new), and no flake8 errors on the diff...

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

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