v1.1.3-2.3-SystemTest

This release is only for system testing against Spark 2.3.

v1.1.2-2.2-SystemTest

This release is only for system testing against Spark 2.2.

v1.1.1-2.1-SystemTest

This release is only for system testing Spark 2.1.

v1.1.1-2.1-HDP-2.6.1.0

This release is for HDP-2.6.1.0.

v1.1.1-2.1

This release has the following updates.

• Support multiple secure HBase clusters. Two long running examples (LRJobAccessing2Clusters and LRJobForDataSources) for this feature have been added.
• Bug fixes.

v1.1.1-1.6

Bug fixes.

v1.1.0-2.1

This release has the same features/functionalities as v1.1.0-1.6 and v1.1.0-2.0.

v1.1.0-2.0

This release has the following updates.

• Support Phoenix as data coder. Phoenix coder supports the composite key in which the length of values of each individual key can be variable. Also, SHC supports plugin coders, which just needs to extends trait SHCDataType (there are three internal coders) and specify the coder name in catalog definition like this.
• Fully support all the Avro schemas. Users can use either a complete record schema or partial field schema as data type in their catalog.
• Add an API to log the state of HBase connection cache (commit 82d7aa0).
• Fix some bugs. Now different columns can be written into the same column family, and users are able to specify the namespace for their tables.
• Fix some performance issues. E.g. the performance of OR has been improved.

v1.1.0-1.6

This release has the following updates.

• Support Phoenix as data coder. Phoenix coder supports the composite key in which the length of values of each individual key can be variable. Also, SHC supports plugin coders, which just needs to extends trait SHCDataType (there are three internal coders) and specify the coder name in catalog definition like this.
• Fully support all the Avro schemas. Users can use either a complete record schema or partial field schema as data type in their catalog.
• Add an API to log the state of HBase connection cache (commit 82d7aa0).
• Fix some bugs. Now different columns can be written into the same column family, and users are able to specify the namespace for their tables.
• Fix some performance issues. E.g. the performance of OR has been improved.