Please note that there is also a static version of netty-tcnative but we
currently do not distribute it due to licensing issues. Once openSSL completes
its switch to Apache License v2, we can provide this as well and maybe even
make that one default (by putting it into lib/). Since there are to many things
which may go wrong with the dynamically-linked library (based on the system you
run on), we provide this only in opt/.

This closes #8590.

Note: Currently only flink planner is supported. The blink planner will be supported after the planner discovery is supported which is part of the work of FLIP32.

This closes #8474

This closes #8472

[FLINK-12311][python] Add base python framework and Add Scan, Projection, and Filter operator support

This closes #8267

make travis tests green

fix documents, refine shell file name and optimize program logic.

Adjust the code examples in python documents to be consistent with scala documents.

Refactor flink-python project structure, remove java file from flink-python package.

delete unnecessary dependency and plugins.

This also adadpts update_branch_version.sh to correctly update versions
that have a prefix.

This commit splits the flink-table module into multiple submodules in
accordance with FLIP-32 (step 1).

The new module structure looks as follows:

flink-table-common
       ^
       |
flink-table-api-java <------- flink-table-api-scala
       ^                                 ^
       |                                 |
flink-table-api-java-bridge    flink-table-api-scala-bridge
       ^
       |
flink-table-planner

The module structure assumes that the type system has been reworked such
that only one table environment exists for both Java and Scala users.

The module `flink-table-planner` contains the content of the old
`flink-table` module. From there we can distribute ported classes to
their final module without breaking backwards compatibility or
force users to update their dependencies again.

For example, if a user wants to implement a pure table program in Scala,
`flink-table-api-scala` and `flink-table-planner` need to be
added to the project.

Until we support pure table programs, `flink-table-api-scala/java-bridge`
and `flink-table-planner` need to be added to the project.

This closes #7587.

This changes some modules that had a _2.11 dependency but didn't expose
it in their module name to instead depend on the ${scala.binary.version}
dependency.

The main reason for this is to make the build self contained, before,
with the hard-dependency on 2.11, when buildig for 2.12 it would not be
clear where the dependency would come from because it is not created as
part of the build. This could lead to inconsistencies. For example, when
adding a new class in flink-runtime but not recompiling on 2.11 but only
on 2.12, the 2.12 tests would fail when using that new class because
they would use 2.11 dependencies that weren't rebuilt with the new
class.

We also don't build flink-scala-shell and flink-connector-kafka-0.8
because they don't work with Scala 2.12.

This also includes $PROFILE in dependency convergence check script. This
is in preparation for building with "-Dscala-212", where we hace to
exclude certain things.

We also exclude Kafka 0.8 from stages when building for Scala 2.12

And add Scala 2.12 to the release scripts

This closes #6316.

This closes #6304.

flink-connectors, flink-orc, flink-connector-wikiedits, flink-dist, flink-metrics-*, flink-queryable-state-*

This closes #6093.

This closes #5596.

This closes #5564.

This closes #3838.

This closes #5491.

This closes #5296.

Before, AvroUtils were loaded when the class was loaded which didn't
take into account the user-code ClassLoader. Now, we try loading avro
utils with the Thread context ClassLoader.

This closes #5042.

This closes #8110.

This closes #4981.

This closes #4973.