Versions Compared

Old Version 2

changes.mady.by.user Atanu Mishra

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (gtapper)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info
titleObsolete

This page is obsolete. It's been replaced with: http://trafodion.apache.org/release-notes-1-3-0.html

redirect
locationhttp://trafodion.apache.org/release-notes-1-3-0.html

Release 1.3.0

To There are various ways to download and install this version of Trafodion, use this software see the InstallationUsing the Software page for options.

This is the first release of the Apache Trafodion (incubating) project. In addition to including a number of new features and improvements across the project, the focus of this release is to comply with Apache release guidelines.

Build and installation instructions are available here: <TBD>.

New Features

  • Support native HBase tables as EXTERNAL tables (TRAFODION-1483)
  • Support pre-splitting of unsalted tables (TRAFODION-50)
  • Support for IDENTITY columns (TRAFODION-62*)
  • Support HBase region splitting and re-balancing with active transactions (TRAFODION-34)
  • Support for Batch feature in Installer (TRAFODION-1543)
  • Support for Cloudera parcels feature in Installer (TRAFODION-1452)
  • Support for Multi-temperature data – Part 1 (TRAFODION-49)
  • Compile time interface for Table Mapping UDFs (TMUDF) (TRAFODION-51)
  • Support for multiple column families in a Trafodion table (TRAFODION-1419)
  • Support for MODIFY COLUMN attribute for ALTER TABLE (TRAFODION-18)

...

HBase uses a lease mechanism to protect against memory leaks in Region Servers caused by potential client instabilities that would open scanners, but die before having the opportunity to close cleanly and release resources. This mechanism relies on a server side timer, configured by the hbase.client.scanner.timeout.period parameter in hbase-site.xml. If a client fails to call next() within the timeout period, the server will assume the client died, and will force close the server side scanner and release resources. However, in EsgynDBTrafodion, there are legitimate use cases where client is busy doing heavy processing, and needs more time than specified in the default scanner timeout value.  Increasing the hbase.client.scanner.timeout.period value has the side effect of weakening the safety mechanism previously described. 

...

<property> <name>hbase.trafodion.patchclientscanner.enabled</name><value>true</value> <description>Enable an EsgynDB a Trafodion feature to allow a client to reset the HBase scanner and resume where it left off instead of throwing an exception upon expiry of the HBase hbase.client.scanner.timeout.period timer</description> </property>

...