HadoopCryptoLedger V1.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. Also examples include the latest version

HadoopCryptoLedger V1.3.1

• Addressed #86
• 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.

HadoopCryptoLedger V1.3.0

• Separate Hadoop dependencies from hadoopcryptoledger. This allows to run completely Hadoop-free if desired, e.g. on Flink #84
• Hive 2.x and 3.x support #50
• Hadoop 3.x support #19
• Extensions to the Bitcoin model to make data handling a bit easier

HadoopCryptoLedger V1.2.1

• Make Pojos serializable for convenience #66
• Update dependencies of examples #68

HadoopCryptoLedger V1.2.0

Added support for large numbers (e.g. value of transactions). Note: This changes some fields from long to BigInteger (or to HiveDecimal(38,0) or Spark Decimal(38,0), depending on the platform). Related to issue #51. You may need to review your application to fit to the new datatypes. Change applied to Bitcoin and Ethereum on all supported Big Data platforms.
Some small fixes to the HiveUDFs (e.g. Ethereum calculate sendAddress, chainid was not read correctly from parameters)

HadoopCryptoLedger V1.1.4

Fix issue #47 and #48
Removed unnecessary JSON dependency

HadoopCryptoLedger V1.1.3

Fix issue #46
Some minor cleanups

HadoopCryptoLedger V1.1.2

Bug fix release:

• Several bugs related to Ethereum fixed (thanks to liorregev)
• Preventive fix to potential bug in Bitcoin (jornfranke)

Related issues:
#42
#40
#39

HadoopCryptoLedger V1.1.1

Minor release:

• Migration to JUnit5
• Spark HadoopCryptoLedger DataSource: Enrichment option to include transaction hash when using the format org.zuinnote.spark.bitcoin.block

HadoopCryptoLedger V1.1.0

New features:

• Support for Ethereum in Hadoop, Flink, Hive and Spark