issue_comments

Table actions

3 rows where issue = 481761508 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 3

author_association 2

issue 1

  • Feature request for multiple tolerance values when using nearest method and sel() · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
890129356 https://github.com/pydata/xarray/issues/3223#issuecomment-890129356 https://api.github.com/repos/pydata/xarray/issues/3223 IC_kwDOAMm_X841DkvM benbovy 4160723 2021-07-30T20:12:36Z 2021-07-30T20:12:36Z MEMBER

This is still relevant.

As part of the ongoing explicit / flexible indexes refactoring, we'll probably need a more general solution to pass any selection option to the corresponding indexes.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature request for multiple tolerance values when using nearest method and sel() 481761508
883977616 https://github.com/pydata/xarray/issues/3223#issuecomment-883977616 https://api.github.com/repos/pydata/xarray/issues/3223 IC_kwDOAMm_X840sG2Q stale[bot] 26384082 2021-07-21T08:00:50Z 2021-07-21T08:00:50Z NONE

In order to maintain a list of currently relevant issues, we mark issues as stale after a period of inactivity

If this issue remains relevant, please comment here or remove the stale label; otherwise it will be marked as closed automatically

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature request for multiple tolerance values when using nearest method and sel() 481761508
522137031 https://github.com/pydata/xarray/issues/3223#issuecomment-522137031 https://api.github.com/repos/pydata/xarray/issues/3223 MDEyOklzc3VlQ29tbWVudDUyMjEzNzAzMQ== shoyer 1217238 2019-08-16T20:13:07Z 2019-08-16T20:13:07Z MEMBER

We could potentially do this, and your suggested API looks sane.

But before we start, are you sure we need it? Would it suffice to index multiple times instead? I guess a motivating use-case could be point-wise indexing in a multi-dimensional dataset, e.g., to pull out lat/lon/time values matching a list of points.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   Feature request for multiple tolerance values when using nearest method and sel() 481761508

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