Spark Datasource HadoopCryptoLedger V1.3.2

• Based on HadoopCryptoLedger v 1.3.2
• Update to log4j2 2.17 - note: HadoopCryptoLedger does not include log4j2 during runtime. It is only used in the build process during testing. Nevertheless it is a good practice to have the latest version.

Spark Datasource HadoopCryptoLedger V1.3.1

• Based on HadoopCryptoLedger V1.3.1
• Addressed #21
• Various dependency and build tool updates
• Various updates to examples

Note: Independent of updating the dependencies - as a defense in the depth - we recommend additionally to upgrade to the latest JDK8 (at least > 191, better the latest) or JDK11/JDK17 and to set the Java System properties (e.g. via -D) "log4j2.formatMsgNoLookups" to "true" and set "com.sun.jndi.rmi.object.trustURLCodebase" and "com.sun.jndi.cosnaming.object.trustURLCodebase" to "false".
You may want to set the environment variable JAVA_TOOL_OPTIONS in any case as follows

export JAVA_TOOL_OPTIONS="-Dlog4j2.formatMsgNoLookups=true -Dcom.sun.jndi.rmi.object.trustURLCodebase=false -Dcom.sun.jndi.cosnaming.object.trustURLCodebase=false"

Additionally set the environment LOG4J_FORMAT_MSG_NO_LOOKUPS to true

export LOG4J_FORMAT_MSG_NO_LOOKUPS=true

especially in all your container images and redeploy the container images to all environments where they are running

ENV LOG4J_FORMAT_MSG_NO_LOOKUPS=true

Finally, replace in all your log4j configuration files %m or %msg with %m{nolookups} to protect your applications also in the future.

Spark Datasource HadoopCryptoLedger V1.3.0

• Based on HadoopCryptoLedger V1.3.0
• Due to the separation of dependencies from Hadoop in the HadoopCryptoLedger libraries we needed to do some minor changes, check the latest examples on Bitcoin and Ethereum. Basically BitcoinBlock became BitcoinBlockWritable and EthereumBlock became EthereumBlockWritable

Spark Datasource HadoopCryptoLedger V1.2.1

• Updated to HadoopCryptoLedger V1.2.1
• Updated dependencies
• Shaded Bouncycastle library to facilitate use of library

Spark Datasource HadoopCryptoLedger V1.2.0

Based on HadoopCryptoLedger library 1.2.0 (https://github.com/ZuInnoTe/hadoopcryptoledger/releases). Support for large numbers. Note this means some field that have been previous of type long are now of type Decimal(38,0). You may need to review your application.

Spark Datasource HadoopCryptoLedger V1.1.4

Based on HadoopCryptoLedger 1.1.4 (https://github.com/ZuInnoTe/hadoopcryptoledger/releases) fixing bugs related to correct encoding for calculating the transaction hash and implement EIP-155 for calculating correctly the sendAddress for EIP-155 transctions

Spark Datasource HadoopCryptoLedger V1.1.3

Based on HadoopCryptoLedger 1.1.3 (fix issue 46)
Minor cleanups

Spark Datasource HadoopCryptoLedger V1.1.2

Based on HadoopCryptoLedger library (https://github.com/ZuInnoTe/hadoopcryptoledger) 1.1.2

Several bug fixes related to Ethereum

Spark Datasource HadoopCryptoLedger V1.1.1

Based on HadoopCryptoLedger library (https://github.com/ZuInnoTe/hadoopcryptoledger) 1.1.1

Datasource provides now the option enrich for the format org.zuinnote.spark.bitcoin.block to enhance it with the transaction hash

Spark Datasource HadoopCryptoLedger V1.1.0

Based on HadoopCryptoLedger library (https://github.com/ZuInnoTe/hadoopcryptoledger) 1.1.0 - support for Ethereum