JAVA-3099: Fix failing integration tests (#1701)

should_extract_hosts_using_native_transport_address_port_ssl_from_peers
- use testng style ignore

should_function_with_snappy_compression
- skip for cassandra 4.0.0 and greater (not supported)

should_handle_failing_or_missing_contact_points
- use V4 protocol to avoid initial retry with default V5

should_ignore_and_warn_peers_with_null_entries_by_default
- encode expected "missing native_transport_*" strings when not using v2-style peers

should_init_policy_with_up_contact_points
- since adding SNI support for astra, only contact points will have state INIT

should_throw_proper_read_timeout_exception
- update expected error message string

should_throw_exception_when_frame_exceeds_configured_max
- use V4 protocol for cassandra 4.0+

OPPTokenIntegrationTest/OPPTokenVnodeIntegrationTest
- not applicable for cassandra 4.0+

MailboxServiceSnappyIT
- not applicable for cassandra 4.0+

osgi/BundleOptions
- add missing dependencies for recent library upgrades

override org.ops4j.pax.url.mvn.repositories in osgi tests because https is now required by maven central
15 files changed
tree: b957b79d3fae5fba440bcfa2ceb94a11fad7b58e
  1. .github/
  2. changelog/
  3. ci/
  4. driver-core/
  5. driver-dist/
  6. driver-examples/
  7. driver-extras/
  8. driver-mapping/
  9. driver-tests/
  10. faq/
  11. manual/
  12. testing/
  13. upgrade_guide/
  14. .gitignore
  15. .travis.yml
  16. clirr-ignores.xml
  17. CONTRIBUTING.md
  18. docs.yaml
  19. doxyfile
  20. Jenkinsfile
  21. LICENSE
  22. pom.xml
  23. README.md
README.md

Datastax Java Driver for Apache Cassandra®

If you're reading this on github.com, please note that this is the readme for the development version and that some features described here might not yet have been released. You can find the documentation for the latest version through the Java driver docs or via the release tags, e.g. 3.11.4.

A modern, feature-rich and highly tunable Java client library for Apache Cassandra (2.1+) and using exclusively Cassandra's binary protocol and Cassandra Query Language v3. Use the DataStax Enterprise Java driver for better compatibility and support for DataStax Enterprise.

Features:

The driver architecture is based on layers. At the bottom lies the driver core. This core handles everything related to the connections to a Cassandra cluster (for example, connection pool, discovering new nodes, etc.) and exposes a simple, relatively low-level API on top of which higher level layers can be built.

The driver contains the following modules:

  • driver-core: the core layer.
  • driver-mapping: the object mapper.
  • driver-extras: optional features for the Java driver.
  • driver-examples: example applications using the other modules which are only meant for demonstration purposes.
  • driver-tests: tests for the java-driver.

Useful links:

Getting the driver

The last release of the driver is available on Maven Central. You can install it in your application using the following Maven dependency (if using DataStax Enterprise, install the DataStax Enterprise Java driver instead):

<dependency>
  <groupId>com.datastax.cassandra</groupId>
  <artifactId>cassandra-driver-core</artifactId>
  <version>3.11.4</version>
</dependency>

Note that the object mapper is published as a separate artifact:

<dependency>
  <groupId>com.datastax.cassandra</groupId>
  <artifactId>cassandra-driver-mapping</artifactId>
  <version>3.11.4</version>
</dependency>

The ‘extras’ module is also published as a separate artifact:

<dependency>
  <groupId>com.datastax.cassandra</groupId>
  <artifactId>cassandra-driver-extras</artifactId>
  <version>3.11.4/version>
</dependency>

We also provide a shaded JAR to avoid the explicit dependency to Netty.

If you can't use a dependency management tool, a binary tarball is available for download.

Compatibility

The Java client driver 3.11.4 (branch 3.x) is compatible with Apache Cassandra 2.1, 2.2 and 3.0+ (see this page for the most up-to-date compatibility information).

UDT and tuple support is available only when using Apache Cassandra 2.1 or higher (see CQL improvements in Cassandra 2.1).

Other features are available only when using Apache Cassandra 2.0 or higher (e.g. result set paging, BatchStatement, lightweight transactions -- see What's new in Cassandra 2.0). Trying to use these with a cluster running Cassandra 1.2 will result in an UnsupportedFeatureException being thrown.

The java driver supports Java JDK versions 6 and above.

If using DataStax Enterprise, the DataStax Enterprise Java driver provides more features and better compatibility.

Disclaimer: Some DataStax/DataStax Enterprise products might partially work on big-endian systems, but DataStax does not officially support these systems.

Upgrading from previous versions

If you are upgrading from a previous version of the driver, be sure to have a look at the upgrade guide.

If you are upgrading to DataStax Enterprise, use the DataStax Enterprise Java driver for more features and better compatibility.

License

© DataStax, Inc.

Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.