It is essential that you verify the integrity of release downloads. See instructions here.
|Java Hive Adaptor||1.1.0-incubating||Download||Signature||Hash||2020-07-06T20:51:06Z||40324||leerho|
|Java Pig Adaptor||1.0.0-incubating||Download||Signature||Hash||2019-10-19T01:24:36Z||36385||leerho|
|C++ PostgreSQL Adaptor||1.3.0-incubating||Download||Signature||Hash||2019-10-29T17:12:09Z||36536||alsay|
From Maven Central.
If you are developing using Maven and want to use, for example, datasketches-java, add the following dependencies to your pom.xml file:
<dependency> <groupId>org.apache.datasketches</groupId> <artifactId>datasketches-java</artifactId> <version>1.3.0</version> </dependency>
Apache DataSketches uses semantic versioning. Version numbers use the form major.minor.incremental and are updated as follows:
All download files include a version number in the name, as in apache-datasketches-java-1.1.0-src.zip. This same number is also in the top section of the pom.xml file and is the same number in the GitHub Tag associated with the GitHub-ID that the release was generated from.
Please use GitHub version history on the respective component repositories. There are several ways to access the release notes:
/releasesto the URL as in
These are fully tested, production quality releases, and hopefully as bug-free as humanly possible. However, the code is continuously evolving and improvements in performance, documentation, additions to the API, and bug fixes do occur. When enough of these build up, especially for bug fixes or performance improvements, a new release will be issued and the minor version digit will be incremented. The incremental digit will only be used for unscheduled bug fixes as stated above.
As stated above, the major digit is being reserved for major refactorings of the library where backward API compatibility may not be guaranteed.
For the repositories that depend on java core, such as datasketches-hive and datasketches-pig, the version number may be incremented just to be in sync with the java core repository, and may not reflect any actual code changes other than a change in the pom.xml to reflect the new dependency. Please refer to the release notes for that version.
We try as much as possible to maintain forward binary compatibility of serialized (stored) sketch images. For example, a Java Theta Sketch stored as a binary image using version 0.1.0 (Aug, 2015) can be read and merged into a C++ Theta Union version 1.2.0 (Jan, 2020). The languages can be swapped in this scenario, but the versions cannot be.