datasketches-memory

Summary

• The purpose of this release is to align the API as close as possible to what it will be in the 4.0.0 release for Java 17. The Java 17 release will take advantage of the incubator Panama, which will eliminate the need to use JVM internals such as unsafe, VM, bits, etc. It will be faster too.
• UDF-8 encoding is no longer supported. The prior UDF-code was out-of-date and Java already supports UDF-8 encoding directly.
• Protobuf is no longer a dependency as it was only used to help test the UDF-8 encoding.
• The Handles hierarchy has been removed as it will no longer be needed with Java 17.
• Direct encoding of Primitive boolean arrays into bytes is no longer supported. The Java Language Specification does not specify a binary encoding of boolean arrays, and for that reason, Panama does not support them either.

Details of selected PRs

• Prepare for java 8,11 3.0.0 by @leerho in https://github.com/apache/datasketches-memory/pull/190
• Changes to bring 2.2.0, 3.0.0 and 4.0.0 into alignment. by @leerho in https://github.com/apache/datasketches-memory/pull/192
• Update Readme to accommodate changes from 2.X to 3.0.0. by @leerho in https://github.com/apache/datasketches-memory/pull/196
• Release Process - update Master Version to 3.1.0-SNAPSHOT by @leerho in https://github.com/apache/datasketches-memory/pull/199
• Added groupID, artifactId to maven-gpg-plugin parameters. by @leerho in https://github.com/apache/datasketches-memory/pull/201
• Update SpotBugs Filter. by @leerho in https://github.com/apache/datasketches-memory/pull/202

Full Changelog: https://github.com/apache/datasketches-memory/compare/2.2.1...3.0.0

What's Changed

• Fixed issue #178: By @leerho in https://github.com/apache/datasketches-memory/pull/181
• Updated spotbugs and fixed all the warnings. By @leerho in https://github.com/apache/datasketches-memory/pull/182
• Fixed some checkstyle configuration errors. By @leerho in https://github.com/apache/datasketches-memory/pull/183
• The pom file in the ds-memory-java11 branch used indents of 4 instead of 2. By @leerho in https://github.com/apache/datasketches-memory/pull/185
• updates to POM files. By @leerho in https://github.com/apache/datasketches-memory/pull/184
• Fix Java 11 build/compile problem. By @leerho in https://github.com/apache/datasketches-memory/pull/187

Full Changelog: https://github.com/apache/datasketches-memory/compare/2.2.0...2.2.1

This is a maintenance release and simplifies the Maven project structure.

This is a minor release and includes the following:

• Removes Java 9 and Java 10 support from Datasketches-Memory. Since these versions are no longer receiving security patches, developers no longer need to install these versions on their own environments in order to work with Datasketches-Memory.
  See #160.

This is a major release and includes the following:

• Significant refactoring in PR #129 that refines the public API and restricts access to the package internals using the JPMS in Java9+.
• PR #131 maintains existing support for Java 8 and adds support for Java 9 up to Java 13. In Java9+, the library can now be declared as a JPMS module dependency in user applications.
• Includes changes to how the RequestMemoryServer is managed in #136, #138 and #139
• Improved documentation for developers and the end user including usage in Java9+ applications.

This is the first release of Memory as a Top Level Project.

• This includes PR #122 submitted by Jihoon Son as well as follow-on PR #123, which extended the improvements identified in PR #122, to other areas. This is a significant speed improvement.
• Removed references to "incubator" as a result of the TLP move.
• Other minor code cleanup.

Removes a check that required the runtime JDK to be JDK-8. This does not change the requirement that JDK-8 is required for full runtime operation. However in environments that do not use the advanced off-heap (direct) capabilities of Memory this module may still work in JDK versions later than JDK-8. However, there is no guarantee of this as this code has not been fully refactored and tested to operate in these later versions. Caveat Emptor.

This release was created for the convenience of some major users that need to do testing in versions later than JDK-8, and do not use the advanced features of Memory.

There are no other significant changes in this version compared to the previous 1.1.0-incubating release.

This candidate was not released. There were some structural problems in the POM file.

This release came from RC2, which fixed some problems in the structure of the POM file of
RC1. There are no other changes.

This is the first release as Apache DataSketches-memory (incubating). This is a work-in-progress as it doesn't have all the licensing details quite right. But the code is good and passes all the tests. There are no significant code changes from the previous release. There will be another release coming with some speed improvements. So we suggest that you wait for the next release.

Added new functionality.

XxHash is now not only available from Memory, it also is directly available for hashing primitive arrays. See class XxHash64.

• Added xxHash(...) that is accessible via Memory or Buffer and also replaces the slow hashCode().

• Added WritableMemory.allocate(capacity, ByteOrder)

• Added LGTM integration and badges.

• Javadoc improvements & code cleanup.

• Byte arrays can be wrapped with optional ByteOrder specified with non-native endianness. Any putting or getting of multibyte primitives or primitive arrays into this byte array will be automatically byte-swapped.

• The endianness of ByteBuffers will be detected when wrapping the ByteBuffer. Any putting or getting of primitives will be automatically byte-swapped.

• This release includes some minor API changes to make them more understandable.

• This release includes some bug fixes.

• Added PutCharsToUtf8() and GetCharsFromUtf8()

These methods have been specifically designed to avoid garbage generation during the conversions. The speeds are comparable with the Java built-in methods.

• Made the bounds checking more conservative when putting and getting arrays, where the cost of the bounds check is negligible when compared to the cost of internal array copies.

• Cleaned up some of the object construction cost of the ResourceState class.

• Minor bug fixes (e.g., null checks)
• Fix FindBugs warnings
• Updated overview, Javadocs, pom, etc.

• fixed a bug in getting region() of a Buffer
• added direct offset put methods to WritableBuffer

• expanded Buffer API to include commonly used direct access methods
• null handling consistent with ByteBuffer

Completely rewritten code