This example shows how to write nested sub queries.
Let us write a query to calculate the average tips for rides taken from a particular Zone. The outermost query JOINs the taxi_zone_lookup with a nested subquery hfz which does the job of filtering and grouping the trips table. hfz contains another sub query which ensures prior filtering of trips with license plates that end with 3.
SELECT tzl.Zone, hfz.avg_tips, hfz.trip_count
INTO table1
FROM taxi_zone_lookup tzl
JOIN (
SELECT PULocationID, COUNT(1) AS trip_count, AVG(tips) AS avg_tips
FROM (
SELECT PULocationID, tips
FROM trips
WHERE hvfhs_license_num LIKE '%3'
)
GROUP BY PULocationID
HAVING COUNT(1) > 100 AND AVG(tips) > 1.00
) hfz ON tzl.LocationID = hfz.PULocationIDTo run Dozer navigate to the join folder /sql/sub-queries & use the following command
dozer runTo remove the cache directory, use
dozer cleanTo run with Dozer live, replace run with live
dozer liveDozer live automatically deletes the cache upon stopping the program.
Dozer API lets us use filter,limit,order_by and skip at the endpoints. For this example lets order the data in descending order of avg_tips.
Execute the following commands over bash to get the results from REST and gRPC APIs.
REST
curl -X POST http://localhost:8080/hfz-trips/query \
--header 'Content-Type: application/json' \
--data-raw '{"$order_by": {"avg_tips": "desc"}}'gRPC
grpcurl -d '{"endpoint": "hfz-tips", "query": "{\"$order_by\": {\"avg_tips\": \"desc\"}}"}' \
-plaintext localhost:50051 \
dozer.common.CommonGrpcService/query