The build has to be done in two steps: First in the base directory, then in the distribution project: mvn clean install -DskipTests cd flink-dist It is sufficient to call mvn clean install -DskipTests in the root directory of Flink code base. The dependency shading mechanism was recently changed in Maven and requires users to build Flink slightly differently, depending on their Maven version: ![]() Among the shaded libraries are Google Guava, Asm, Apache Curator, Apache HTTP Components, Netty, and others. flink-python/dist/目录下。它们均可使用pip安装,比如: pip install dist/ *.tar.gz Dependency Shadingįlink shades away some of the libraries it uses, in order to avoid version clashes with user programs that use different versions of these libraries. To speed up the build you can skip tests, QA plugins, and JavaDocs: mvn clean install -DskipTests -Dfast 构建PyFlink This instructs Maven ( mvn) to first remove all existing builds ( clean) and then create a new Flink binary ( install). The simplest way of building Flink is by running: mvn clean install -DskipTests To build unit tests use Java 8u51 or above to prevent failures in unit tests that use the PowerMock runner. Maven 3.2.5 creates the libraries properly. NOTE: Maven 3.3.x can build Flink, but will not properly shade away certain dependencies. In addition you need Maven 3 and a JDK (Java Development Kit). Either download the source of a release or clone the git repository. ![]() In order to build Flink you need the source code. ![]() This page covers how to build Flink 1.9.0 from sources.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |