Tutorial Presto 8.8 【OFFICIAL | 2027】

coordinator=true node-scheduler.include-coordinator=true http-server.http.port=8080 discovery.uri=http://localhost:8080 query.max-memory=3GB query.max-memory-per-node=1GB query.max-total-memory-per-node=2GB bin/launcher start Check status:

SELECT p.product_name, p.category, s.sale_amount FROM postgresql.public.products p JOIN memory.default.sales s ON p.product_id = s.order_id WHERE s.sale_date > DATE '2025-01-01'; Here, Presto 8.8 seamlessly pulls products from PostgreSQL and sales from the memory connector. Assuming you have a geotable with a geometry column (e.g., in Hive):

SELECT name, ST_Area(geometry) AS area_sqkm FROM hive.gis.locations WHERE ST_Within(geometry, ST_Point(-74.006, 40.7128)); In Presto 8.8, dynamic filtering is enabled by default. You can control it: tutorial presto 8.8

-- Insert data INSERT INTO memory.default.sales VALUES (1, 'Laptop', 999.99, DATE '2025-01-15'), (2, 'Mouse', 25.50, DATE '2025-01-16');

connector.name=memory memory.max-data-per-node=512MB Restart Presto after adding catalogs: coordinator=true node-scheduler

bin/launcher status Expected output: Running as [PID] . wget https://repo1.maven.org/maven2/io/prestosql/presto-cli/8.8/presto-cli-8.8-executable.jar mv presto-cli-8.8-executable.jar presto chmod +x presto ./presto --server localhost:8080 You should see the Presto shell: presto> Part 3: Configuring Catalogs in Presto 8.8 Presto’s superpower is its connector architecture. Let’s set up three common catalogs. 1. Hive Connector (for S3 or HDFS) Create etc/catalog/hive.properties :

node.environment=production node.id=presto-master-01 node.data-dir=/var/presto/data Create etc/jvm.config : wget https://repo1

-server -Xmx4G -XX:+UseG1GC -XX:G1HeapRegionSize=32M -XX:+UseGCOverheadLimit -XX:+ExplicitGCInvokesConcurrent -Dlog.levels-file=etc/log.properties Create etc/config.properties (coordinator + worker on same machine):