issue_comments

Table actions

7 rows where issue = 820480606 and user = 24235303 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

  • jp-dark · 7 ✖

issue 1

  • A read-only TileDB backend · 7 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions performed_via_github_app issue
796873186 https://github.com/pydata/xarray/issues/4987#issuecomment-796873186 https://api.github.com/repos/pydata/xarray/issues/4987 MDEyOklzc3VlQ29tbWVudDc5Njg3MzE4Ng== jp-dark 24235303 2021-03-11T16:39:27Z 2021-03-11T16:39:27Z CONTRIBUTOR

@jhamman Is there a planned date for releasing the backend updates to PyPI?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A read-only TileDB backend 820480606
794029445 https://github.com/pydata/xarray/issues/4987#issuecomment-794029445 https://api.github.com/repos/pydata/xarray/issues/4987 MDEyOklzc3VlQ29tbWVudDc5NDAyOTQ0NQ== jp-dark 24235303 2021-03-09T15:14:34Z 2021-03-09T15:14:34Z CONTRIBUTOR

I was able to use this backend from an external code base with the entry point procedure as described in the new docs, and it was completely painless. Great job with the backend refactor!

 
{
    "total_count": 5,
    "+1": 2,
    "-1": 0,
    "laugh": 0,
    "hooray": 3,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A read-only TileDB backend 820480606
791639282 https://github.com/pydata/xarray/issues/4987#issuecomment-791639282 https://api.github.com/repos/pydata/xarray/issues/4987 MDEyOklzc3VlQ29tbWVudDc5MTYzOTI4Mg== jp-dark 24235303 2021-03-05T19:43:10Z 2021-03-05T19:43:10Z CONTRIBUTOR

Is there a branch of xarray that currently supports loading backend engines from third-party libraries?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A read-only TileDB backend 820480606
790860834 https://github.com/pydata/xarray/issues/4987#issuecomment-790860834 https://api.github.com/repos/pydata/xarray/issues/4987 MDEyOklzc3VlQ29tbWVudDc5MDg2MDgzNA== jp-dark 24235303 2021-03-04T19:13:07Z 2021-03-04T19:18:57Z CONTRIBUTOR

See PR #4998 for the example

edit: This example should be able to read a NetCDF dataset using the protocol engine: xr.open_dataset("example.nc", engine="protocol")

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A read-only TileDB backend 820480606
790851791 https://github.com/pydata/xarray/issues/4987#issuecomment-790851791 https://api.github.com/repos/pydata/xarray/issues/4987 MDEyOklzc3VlQ29tbWVudDc5MDg1MTc5MQ== jp-dark 24235303 2021-03-04T19:00:38Z 2021-03-04T19:00:38Z CONTRIBUTOR

@alexamici @shoyer To be clear, my short term plan is absolutely to move the TileDB backend from my draft pull request here to a small plugin in library (thanks for linking the cfgrib @alexamici!).

I only bring up the protocol thing because the backend is really close to a place where a lot of the boilerplate for the lazy loading, etc. could be provided on the xarray side with a simple API requirement on the third-party library side. I'll push up a small proof-of-concept with a read-only netCDF4 example shortly.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A read-only TileDB backend 820480606
790109209 https://github.com/pydata/xarray/issues/4987#issuecomment-790109209 https://api.github.com/repos/pydata/xarray/issues/4987 MDEyOklzc3VlQ29tbWVudDc5MDEwOTIwOQ== jp-dark 24235303 2021-03-03T22:10:46Z 2021-03-03T22:10:46Z CONTRIBUTOR

As a provider of a third-party backend, I would love to be able to integrate with xarray without including xarray as a dependency in my library, and xarray is actually really close to a place where that would be possible.

The main development effort on the xarray side would be creating a generic LazyLoadingBackendStore that accepts duck-typed backends (xarray can define them using Protocols for mypy goodness).

If there is interest in pursuing this, I can help with developing a prototype to test feasibility.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A read-only TileDB backend 820480606
790023571 https://github.com/pydata/xarray/issues/4987#issuecomment-790023571 https://api.github.com/repos/pydata/xarray/issues/4987 MDEyOklzc3VlQ29tbWVudDc5MDAyMzU3MQ== jp-dark 24235303 2021-03-03T20:12:02Z 2021-03-03T20:12:02Z CONTRIBUTOR

@jhamman - thanks for the quick response! As I work through bumps would it be best to comment here or on one of the other currently open issues for the backend refactor?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
   A read-only TileDB backend 820480606

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