|Number of watchers on Github||7257|
|Number of open issues||1250|
|Average time to close an issue||1 day|
|Average time to merge a PR||2 days|
|Open pull requests||406+|
|Closed pull requests||230+|
|Last commit||over 1 year ago|
|Repo Created||almost 7 years ago|
|Repo Last Updated||over 1 year ago|
|Organization / Author||prestodb|
|Do you use presto? Leave a review!|
|View open issues (1250)|
|View presto activity|
|View on github|
|Fresh, new opensource launches 🚀🚀🚀|
Trendy new open source projects in your inbox! View examples
Presto is a distributed SQL query engine for big data.
See the User Manual for deployment instructions and end user documentation.
Presto is a standard Maven project. Simply run the following command from the project root directory:
./mvnw clean install
On the first build, Maven will download all the dependencies from the internet and cache them in the local repository (
~/.m2/repository), which can take a considerable amount of time. Subsequent builds will be faster.
Presto has a comprehensive set of unit tests that can take several minutes to run. You can disable the tests when building:
./mvnw clean install -DskipTests
After building Presto for the first time, you can load the project into your IDE and run the server. We recommend using IntelliJ IDEA. Because Presto is a standard Maven project, you can import it into your IDE using the root
pom.xml file. In IntelliJ, choose Open Project from the Quick Start box or choose Open from the File menu and select the root
After opening the project in IntelliJ, double check that the Java SDK is properly configured for the project:
Presto comes with sample configuration that should work out-of-the-box for development. Use the following options to create a run configuration:
-ea -XX:+UseG1GC -XX:G1HeapRegionSize=32M -XX:+UseGCOverheadLimit -XX:+ExplicitGCInvokesConcurrent -Xmx2G -Dconfig=etc/config.properties -Dlog.levels-file=etc/log.properties
The working directory should be the
presto-main subdirectory. In IntelliJ, using
$MODULE_DIR$ accomplishes this automatically.
Additionally, the Hive plugin must be configured with location of your Hive metastore Thrift service. Add the following to the list of VM options, replacing
localhost:9083 with the correct host and port (or use the below value if you do not have a Hive metastore):
If your Hive metastore or HDFS cluster is not directly accessible to your local machine, you can use SSH port forwarding to access it. Setup a dynamic SOCKS proxy with SSH listening on local port 1080:
ssh -v -N -D 1080 server
Then add the following to the list of VM options:
Start the CLI to connect to the server and run SQL queries:
Run a query to see the nodes in the cluster:
SELECT * FROM system.runtime.nodes;
In the sample configuration, the Hive connector is mounted in the
hive catalog, so you can run the following queries to show the tables in the Hive database
SHOW TABLES FROM hive.default;
We recommend you use IntelliJ as your IDE. The code style template for the project can be found in the codestyle repository along with our general programming and Java guidelines. In addition to those you should also adhere to the following:
PrestoException(HIVE_TOO_MANY_OPEN_PARTITIONS). This categorization lets you generate reports so you can monitor the frequency of various failures.
format("Session property %s is invalid: %s", name, value)(note that
format()should always be statically imported). Sometimes, if you only need to append something, consider using the
Assertionsclass if there is one that covers your case rather than writing the assertion by hand. Over time we may move over to more fluent assertions like AssertJ.