3 ms·
I'm getting: ERROR: Internal Splitgraph error CONTEXT: PL/pgSQL function schema_controller.fatal(text) line 3 at RAISE When running: SELECT ":id", "v
by mritchie712 6y ago
I'm getting:
ERROR: Internal Splitgraph error CONTEXT: PL/pgSQL function schema_controller.fatal(text) line 3 at RAISE
When running:
SELECT ":id", "vacancy_rates"
FROM "brla-gov/census-demographics-xsrb-mxqt:latest"."census_demographics"
LIMIT 100;
- mritchie712 6y agoThis one seems to work fine: "calgary-ca/civic-census-by-ward-age-and-gender-ga6m-7k2i:latest"."civic_census_by_ward_age_and_gender"
- mildbyte 6y agoThanks for the report! Our error reporting could definitely be more informative here. I've just looked at the logs and in this case the problem is that the upstream government data portal (https://data.brla.gov/ https://data.brla.gov/) is temporarily unavailable.
- mritchie712 6y agoI see, so you hit the data in real time? Do you cache anything?
- mildbyte 6y agoWe hit it in real time for most datasets. A lot of government open data portals are powered by Socrata [0] and we wrote a foreign data wrapper that translates the query into their proprietary query language. If it's a dataset that we host ourselves, there's no problem with the upstream being unavailable. We have a cache too, but it currently just hashes the query's AST. In the future, we'll be looking at caching actual tables as well -- basically, we'd store some regions of the remote table and selectively pull data from upstream when a query comes in to fill out our view of what the remote table looks like. [0] https://www.splitgraph.com/docs/ingesting-data/socrata https://www.splitgraph.com/docs/ingesting-data/socrata