JarCasting
JarCasting JarCasting

presto-bytecode

Presto

License

License
GroupId

GroupId

uk.co.nichesolutions.presto
ArtifactId

ArtifactId

presto-bytecode
Last Version

Last Version

0.143-CUSTOM
Release Date

Release Date
Type

Type

jar
Description

Description

presto-bytecode
Presto

Download presto-bytecode

Filename Size
presto-bytecode-0.143-CUSTOM.pom
presto-bytecode-0.143-CUSTOM.jar 181 KB
presto-bytecode-0.143-CUSTOM-tests.jar 28 KB
presto-bytecode-0.143-CUSTOM-test-sources.jar 19 KB
presto-bytecode-0.143-CUSTOM-sources.jar 94 KB
presto-bytecode-0.143-CUSTOM-javadoc.jar 460 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/uk.co.nichesolutions.presto/presto-bytecode/ -->
<dependency>
    <groupId>uk.co.nichesolutions.presto</groupId>
    <artifactId>presto-bytecode</artifactId>
    <version>0.143-CUSTOM</version>
</dependency>
// https://jarcasting.com/artifacts/uk.co.nichesolutions.presto/presto-bytecode/
implementation 'uk.co.nichesolutions.presto:presto-bytecode:0.143-CUSTOM'
// https://jarcasting.com/artifacts/uk.co.nichesolutions.presto/presto-bytecode/
implementation ("uk.co.nichesolutions.presto:presto-bytecode:0.143-CUSTOM")
'uk.co.nichesolutions.presto:presto-bytecode:jar:0.143-CUSTOM'
<dependency org="uk.co.nichesolutions.presto" name="presto-bytecode" rev="0.143-CUSTOM">
  <artifact name="presto-bytecode" type="jar" />
</dependency>
@Grapes(
@Grab(group='uk.co.nichesolutions.presto', module='presto-bytecode', version='0.143-CUSTOM')
)
libraryDependencies += "uk.co.nichesolutions.presto" % "presto-bytecode" % "0.143-CUSTOM"
[uk.co.nichesolutions.presto/presto-bytecode "0.143-CUSTOM"]

Dependencies

compile (4)

Group / Artifact Type Version
org.ow2.asm : asm-all jar 5.0.4
com.google.code.findbugs : annotations jar 2.0.3
com.google.guava : guava jar 18.0
io.airlift : log jar 0.124

test (1)

Group / Artifact Type Version
org.testng : testng jar 6.9.6

Project Modules

There are no modules declared in this project.

Presto Build Status

Presto is a distributed SQL query engine for big data.

See the User Manual for deployment instructions and end user documentation.

Requirements

  • Mac OS X or Linux
  • Java 8 Update 40 or higher (8u40+), 64-bit
  • Maven 3.2.3+ (for building)
  • Python 2.4+ (for running with the launcher script)

Building Presto

Presto is a standard Maven project. Simply run the following command from the project root directory:

mvn 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:

mvn clean install -DskipTests

Running Presto in your IDE

Overview

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 pom.xml file.

After opening the project in IntelliJ, double check that the Java SDK is properly configured for the project:

  • Open the File menu and select Project Structure
  • In the SDKs section, ensure that a 1.8 JDK is selected (create one if none exist)
  • In the Project section, ensure the Project language level is set to 8.0 as Presto makes use of several Java 8 language features

Presto comes with sample configuration that should work out-of-the-box for development. Use the following options to create a run configuration:

  • Main Class: com.facebook.presto.server.PrestoServer
  • VM Options: -ea -Xmx2G -Dconfig=etc/config.properties -Dlog.levels-file=etc/log.properties
  • Working directory: $MODULE_DIR$
  • Use classpath of module: presto-main

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):

-Dhive.metastore.uri=thrift://localhost:9083

Using SOCKS for Hive or HDFS

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:

-Dhive.metastore.thrift.client.socks-proxy=localhost:1080

Running the CLI

Start the CLI to connect to the server and run SQL queries:

presto-cli/target/presto-cli-*-executable.jar

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 default:

SHOW TABLES FROM hive.default;
uk.co.nichesolutions.presto

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.

Versions

Version
0.143-CUSTOM