Hyrax 1.16.5 Release
7 views
Skip to first unread message
Nathan Potter
Jan 10, 2022, 1:17:58 PM1/10/22
to OPeNDAP Inc., Nathan Potter
Greetings,
OPeNDAP is please to announce the release of Hyrax-1.16.5
DMR++ Improvements
• Added support for the HDF5 filter Fletcher32 to the dmr++ creation and processing code.
• Implemented lazy evaluation of dmr++ files.
• Added version and configuration information to dmr++ files built using the build_dmrpp and get_dmrpp applications.
• This improved dmr++ read performance by a factor of 2-3 orders of magnitude!
BES Handler Updates
• Added new netcdf_handler configuration parameter: NC.PromoteByteToShort Which, when set to true will cause signed 8-bit integer values to be promoted to Int16 (Because the DAP2 data model does not support signed 8-bit integers)
• By default the NetCDF Fileout feature ships with FONc.ClassicModel=false
• Added new configuration option to the hdf5_handler, EnableCFDMR=truewhich will allow the generation of CF compliant DMR output.
OLFS Configuration
In order to make the server's behavior more understandable to users, and its configuration more understandable to admins we have changed the way that the server responds to client requests for the unadorned Dataset URL and the way that the server generates Data Request Form links in its catalog pages. There are new configuration parameters to control these behaviors.
You can find the details here: https://www.opendap.org/software/hyrax/1.16
Sincerely,
Nathan
APPENDIX: Hyrax and the Apache Log4j Vulnerability
Hyrax does not use Log4j and does not ship with Log4j binaries.
The docker container that we use to deploy the Hyrax application is based on CentOS-7.latest running Tomcat version 7.0.76 release 16.el7_9 installed from rpm using yum. Tomcat is a java application and includes (via an rpm dependency) the Log4j-1.2.17 library, installed from rpm.
As of 12:55 ET 12/17/2021 the Mitigation section of the Apache Log4j website’s security page here: https://logging.apache.org/log4j/2.x/security.html
States that:
> Log4j 1.x mitigation: Log4j 1.x is not impacted by this vulnerability.
= = =
Nathan Potter ndp at opendap.org
OPeNDAP, Inc. +1.541.231.3317
OPeNDAP is please to announce the release of Hyrax-1.16.5
DMR++ Improvements
• Added support for the HDF5 filter Fletcher32 to the dmr++ creation and processing code.
• Implemented lazy evaluation of dmr++ files.
• Added version and configuration information to dmr++ files built using the build_dmrpp and get_dmrpp applications.
• This improved dmr++ read performance by a factor of 2-3 orders of magnitude!
BES Handler Updates
• Added new netcdf_handler configuration parameter: NC.PromoteByteToShort Which, when set to true will cause signed 8-bit integer values to be promoted to Int16 (Because the DAP2 data model does not support signed 8-bit integers)
• By default the NetCDF Fileout feature ships with FONc.ClassicModel=false
• Added new configuration option to the hdf5_handler, EnableCFDMR=truewhich will allow the generation of CF compliant DMR output.
OLFS Configuration
In order to make the server's behavior more understandable to users, and its configuration more understandable to admins we have changed the way that the server responds to client requests for the unadorned Dataset URL and the way that the server generates Data Request Form links in its catalog pages. There are new configuration parameters to control these behaviors.
You can find the details here: https://www.opendap.org/software/hyrax/1.16
Sincerely,
Nathan
APPENDIX: Hyrax and the Apache Log4j Vulnerability
Hyrax does not use Log4j and does not ship with Log4j binaries.
The docker container that we use to deploy the Hyrax application is based on CentOS-7.latest running Tomcat version 7.0.76 release 16.el7_9 installed from rpm using yum. Tomcat is a java application and includes (via an rpm dependency) the Log4j-1.2.17 library, installed from rpm.
As of 12:55 ET 12/17/2021 the Mitigation section of the Apache Log4j website’s security page here: https://logging.apache.org/log4j/2.x/security.html
States that:
> Log4j 1.x mitigation: Log4j 1.x is not impacted by this vulnerability.
= = =
Nathan Potter ndp at opendap.org
OPeNDAP, Inc. +1.541.231.3317
Reply all
Reply to author
Forward
0 new messages