home / github

Menu
  • GraphQL API
  • Search all tables

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where issue = 481838855 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

  • shoyer 1
  • stale[bot] 1

author_association 2

  • MEMBER 1
  • NONE 1

issue 1

  • Add "on"-parameter to "merge" method · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
883781325 https://github.com/pydata/xarray/issues/3224#issuecomment-883781325 https://api.github.com/repos/pydata/xarray/issues/3224 IC_kwDOAMm_X840rW7N stale[bot] 26384082 2021-07-21T00:00:50Z 2021-07-21T00: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
}
  Add "on"-parameter to "merge" method 481838855
523155674 https://github.com/pydata/xarray/issues/3224#issuecomment-523155674 https://api.github.com/repos/pydata/xarray/issues/3224 MDEyOklzc3VlQ29tbWVudDUyMzE1NTY3NA== shoyer 1217238 2019-08-20T19:13:16Z 2019-08-20T19:13:16Z MEMBER

I appreciate how this could be convenient, but I am concerned about adding more complexity to xarray's merge code, which is already pretty complex and hard to maintain. My refactor in https://github.com/pydata/xarray/pull/3234 is the first time that code has been touched in quite a while and I don't think anyone (other than myself) has made contributions to that part of xarray.

To solve your use-case, what about either: 1. Converting observations into a MultiIndex over individual and subtissue, or 2. Creating separate individual/subtissue dimensions and storing the data the data in the form of a sparse array

Then you could do this sort of data munging with normal indexing/alignment/merging, e.g., python tissue_1 = ds.sel(subtissue="Whole_Blood").rename({k: k + ':1' for k in ds}) tissue_2 = ds.sel(subtissue="Adipose_Subcutaneous").rename({k: k + ':2' for k in ds}) merged = tissue_1.merge(tissue_2) # would have dimensions [gene, individual]

{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
  Add "on"-parameter to "merge" method 481838855

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]);
Powered by Datasette · Queries took 12.096ms · About: xarray-datasette
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows