Making it easy to query APIs via SQL
Project description
Shillelagh is a Python DB API and SQLAlchemy dialect for querying non-SQL resources like APIs and files. You can use it to write queries like this:
INSERT INTO "csv:///path/to/file.csv"
SELECT time, chance_of_rain
FROM "https://api.weatherapi.com/v1/history.json?key=XXX&q=London"
WHERE strftime('%Y-%m-%d', time) IN (
SELECT day
FROM "https://docs.google.com/spreadsheets/d/1_rN3lm0R_bU3NemO0s9pbFkY5LQPcuy1pscv8ZXPtg8/edit#gid=2064361835"
)The query above reads holidays from a Google Sheet, uses the days to get weather data from WeatherAPI, and writes the change of rain at each hour of the holidays into a (pre-existing) CSV file.
Each of these resources is implemented via an adapter, and writing adapters is relatively straightforward.
Using Shillelagh
You can use Shillelagh similar to how you would use SQLite (Shillelagh is built on top of APSW):
# currently there's just the APSW backend, but in the future
# we could implement more
from shillelagh.backends.apsw.db import connect
connection = connect(":memory:") # or connect("database.sqlite")
cursor = connection.cursor()
query = "SELECT * FROM some_table"
for row in cursor.execute(query):
print(row)You can also use it with SQLAlchemy:
from sqlalchemy.engine import create_engine
engine = create_engine("shillelagh://")
connection = engine.connect()The main advantage of Shillelagh is that it allows you to treat non-SQL resources like a table. For example, if you have a Google Spreadsheet URL you can query it directly:
SELECT country, SUM(cnt)
FROM "https://docs.google.com/spreadsheets/d/1_rN3lm0R_bU3NemO0s9pbFkY5LQPcuy1pscv8ZXPtg8/edit#gid=1648320094"
WHERE cnt > 0
GROUP BY countryWhen you run the query above Shillelagh will automatically create a new virtual table (if it doesn’t exist) and associate it with an adapter.
Supported adapters
Currently, Shillelagh supports the following adapters:
CSV files
CSV (comma separated values) are supported via the csv:// scheme (example):
SELECT * FROM "csv:///path/to/file.csv"The adapter supports full DML, so you can also INSERT, UPDATE, or DELETE rows from the CSV file. Deleted rows are marked for deletion, modified and inserted rows are appended at the end of the file, and garbage collection is applied when the connection is closed.
Google Spreadsheets
Google Spreadsheets can be accessed as tables. To SELECT data from a spreadsheets simply use its URL as the table name (example):
SELECT country, SUM(cnt)
FROM "https://docs.google.com/spreadsheets/d/1_rN3lm0R_bU3NemO0s9pbFkY5LQPcuy1pscv8ZXPtg8/edit#gid=1648320094"
WHERE cnt > 0
GROUP BY countryAuthentication is supported, and necessary if you want to use INSERT, UPDATE or DELETE on the spreadsheets. You need to pass credentials via the service_account_info or service_account_file arguments when creating the connection:
service_account_info = {
"type": "service_account",
"project_id": "XXX",
...,
}
engine = create_engine(
"shillelagh://",
adapter_kwargs={
"gsheetsapi": {
"service_account_info": service_account_info,
"subject": "user@example.com",
},
},
)When present, the subject email will be used to impersonate a given user; if not present the connection will have full access to all spreadsheets in a given project, so be careful. Also, make sure the service account has access to the following scopes:
https://www.googleapis.com/auth/drive.readonly
https://www.googleapis.com/auth/spreadsheets
https://spreadsheets.google.com/feeds
You should also confirm that the Google Drive and Google Sheets APIs are active in the project.
Shillelagh also defines a custom dialect called gsheets:// which has only the Google Spreadsheets adapter enabled. Use this is you don’t want users connecting to other resources supported by Shillelagh.
engine = create_engine(
"gsheets://",
service_account_info=service_account_info,
subject="user@example.com",
)Socrata
The Socrata Open Data API is a simple API used by many governments, non-profits, and NGOs around the world, including the CDC. Similarly to the Google Spreadsheets adapter, with the Socrata adapter you can query any API URL directly (example):
SELECT date, administered_dose1_recip_4
FROM "https://data.cdc.gov/resource/unsk-b7fc.json"
WHERE location = 'US'
ORDER BY date DESC
LIMIT 10The adapter is currently read-only.
WeatherAPI
The WeatherAPI adapter was the first one to be written, and provides access to historical weather data (forecasts should be easy to implement as well). You need an API key in order to use it (example):
from datetime import datetime, timedelta
from shillelagh.backends.apsw.db import connect
three_days_ago = datetime.now() - timedelta(days=3)
# sign up for an API key at https://www.weatherapi.com/my/
api_key = "XXX"
connection = connect(":memory:")
cursor = connection.cursor()
sql = f"""
SELECT *
FROM "https://api.weatherapi.com/v1/history.json?key={api_key}&q=94923" AS bodega_bay
WHERE time >= ?
"""
for row in cursor.execute(sql, three_days_ago):
print(row)Writing a new adapter
Let’s say we want to fetch data from WeatherAPI using SQL. Their API is pretty straightforward — to fetch data for a given day in a given location all we need is an HTTP request:
https://api.weatherapi.com/v1/history.json?key=XXX&q=94158&dt=2020-01-01This will return data for 2020-01-01 in the ZIP code 94158 as a JSON payload.
The response contains many different variables, but let’s assume we’re only interested in timestamp and temperature for the sake of this example. Of those two, timestamp is special because it can be used to filter data coming from the API, reducing the amount that needs to be downloaded.
We start by defining an “adapter” class, with the columns we’re interested in:
from shillelagh.adapters.base import Adapter
class WeatherAPI(Adapter):
ts = DateTime(filters=[Range], order=Order.ASCENDING, exact=False)
temperature = Float()The ts (timestamp) column has the type DateTime, and can be filtered with a desired range (for example, WHERE ts >= '2020-01-01' AND ts <= '2020-01-07'). We know that the values will be returned in ascending order by the API, so we annotate that to help the SQL engine. If a query has ORDER BY ts ASC we know that we don’t need to sort the payload.
In addition, we declare that the results from filtering ts are not exact. This is because the API returns data for every hour of a given day. To make our lives easier we’re going to filter the data down to the daily granularity, and let the SQL engine filter the rest. For example, imagine this query:
SELECT * FROM weatherapi WHERE ts > '2020-01-01T12:00:00' AND ts < '2020-01-02T12:00:00'In this case, the adapter is going to download all data for the days 2020-01-01 and 2020-01-02, and pass them to the SQL engine to narrow it down to between noon in each day. We could do that filtering ourselves in the adapter, but since we’re not discarding a lot of data it’s ok.
For temperature we simply declare it as float, since we can’t use temperature values to pre-filter data in the API.
Now we define our __init__ method, which initializes the adapter with the location and API key:
def __init__(self, location: str, api_key: str):
self.location = location
self.api_key = api_keyFinally, we define a method to download data from the API:
def get_data(self, bounds: Dict[str, Filter], order: List[Tuple[str, RequestedOrder]]) -> Iterator[Row]:
ts_range: Range = bounds["ts"]
today = date.today()
start = ts_range.start.date() if ts_range.start else today - timedelta(days=7)
end = ts_range.end.date() if ts_range.end else today
while start <= end:
url = (
f"https://api.weatherapi.com/v1/history.json?key={self.api_key}"
f"&q={self.location}&dt={start}"
)
response = requests.get(url)
if response.ok:
payload = response.json()
hourly_data = payload["forecast"]["forecastday"][0]["hour"]
for record in hourly_data:
dt = dateutil.parser.parse(record["time"])
yield {
"rowid": int(dt.timestamp()),
"ts": dt.isoformat(),
"temperature": record["temp_c"],
}
start += timedelta(days=1)The important thing to know here is that since we defined ts as being filtered through a Range, a corresponding range will be passed to the get_data method specifying how ts should be filtered. The range has optional start and end values, which when not present are defaulted to 7 days ago and today, respectively.
Note also that the method yields rows as dictionaries. In addition to values for ts and temperature it also returns a row ID. This should be a unique value for each row.
We also need to define some dispatching methods, so our adapter can be found:
@staticmethod
def supports(uri: str) -> bool:
"""https://api.weatherapi.com/v1/history.json?key=XXX&q=94158"""
parsed = urllib.parse.urlparse(uri)
query_string = urllib.parse.parse_qs(parsed.query)
return (
parsed.netloc == "api.weatherapi.com"
and parsed.path == "/v1/history.json"
and "key" in query_string
and "q" in query_string
)
@staticmethod
def parse_uri(uri: str) -> Tuple[str, str]:
parsed = urllib.parse.urlparse(uri)
query_string = urllib.parse.parse_qs(parsed.query)
location = query_string["q"][0]
api_key = query_string["key"][0]
return (location, api_key)Now we can use our class to query the API using Sqlite:
from shillelagh.backends.apsw.db import connect
connection = connect(":memory:")
cursor = connection.cursor()
api_key = "XXX"
query = f"""
SELECT *
FROM "https://api.weatherapi.com/v1/history.json?key={api_key}&q=94923" AS bodega_bay
WHERE ts >= '2020-01-01T12:00:00'
"""
for row in cursor.execute(query):
print(row)Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for shillelagh-0.7.4-py2.py3-none-any.whl
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | bd5d225948657dc31d7f5bf3b5a94da8af057a3a55b5add61ab6803aac2cc421 |
|
| MD5 | 33023410b707f3d67d1b40c5546db9ec |
|
| BLAKE2b-256 | f3f76b4d92429d56a0a7f2799cedc66a16151d22bb17c3177fab7a71ec7cfda1 |
