vitess-gh/java
Andres Taylor 4df218d08c Add tracing to the jdbc driver
The jdbc driver will now pass on span information over grpc.

Signed-off-by: Andres Taylor <antaylor@squareup.com>
2019-03-27 16:51:18 +01:00
..
client java: checkstyle for client module 2019-02-07 10:31:27 -05:00
example example: conform to checkstyle 2019-02-07 10:31:27 -05:00
grpc-client Add tracing to the jdbc driver 2019-03-27 16:51:18 +01:00
hadoop Change http to https for security links 2019-02-16 12:41:48 +07:00
jdbc Add tracing to the jdbc driver 2019-03-27 16:51:18 +01:00
.gitignore java: checkstyle for client module 2019-02-07 10:31:27 -05:00
README.md update java/README.md 2019-02-20 20:06:25 -05:00
checkstyle-suppression.xml jdbc: complete checkstyle 2019-02-07 10:31:27 -05:00
pom.xml Merge branch 'master' into zklapow-checkstyle 2019-02-12 10:23:25 -05:00

README.md

Overview

This subdirectory contains all Vitess Java code.

It is split in the following subdirectories (Maven modules):

  • client: Our Java client library.
    • See VTGateConn.java and VTGateBlockingConn.java for the API.
    • Note: The library is agnostic of the underlying RPC system and only defines an interface for that.
    • In open-source, the library must always be used together with the code in grpc-client.
  • grpc-client: Implements the client's RPC interface for gRPC.
  • jdbc: JDBC driver implementation for Vitess.
  • example: Examples for using the client or the jdbc module.
  • hadoop: Vitess support for Hadoop. See documentation for details.

Note: The artifactId for each module listed above has the prefix vitess- i.e. you will have to look for vitess-jdbc and not jdbc.

TODO(mberlin): Mention Maven Central once we started publishing artifacts there.

Adding new Dependencies

When submitting contributions which require new dependencies, please follow these guidelines:

  • Put every directly used dependency into the module's dependencies section (e.g. in jdbc/pom.xml for changes to the JDBC code).
    • make java_test (which calls mvn verify in the /java directory) will run mvn dependency:analyze and fail if you got this wrong.
  • Limit the scope of test dependencies to <scope>test</scope>.
  • Do not include the version number in the module's pom.xml. Instead, add the dependency to the dependencyManagement section in /java/pom.xml and include the version number there.
  • Sort dependencies in alphabetic order. Modules only: Put all dependencies with limited scope (e.g. test) in a separate block and sort it alphabetically as well (see /java/client/pom.xml for an example).
  • Feel free to separate groups of dependencies by newlines (e.g. all io.vitess.* dependencies are a group).