Hi all, Please find attached the first draft for the 10.8.2 release notes. I've also attached a version to the JIRA issue for this release - DERBY-5872. I think I'll not commit this first draft.
Note that this first draft refers to version 10.8.1.6 because I've not changed the versions either in JIRA or in the source, but the version number will be changed later to 10.8.2.0. Please send me your comments. Thx, MyrnaTitle: Release Notes for Apache Derby 10.8.1.6
Release Notes for Apache Derby 10.8.1.6
These notes describe the difference between Apache Derby release 10.8.1.6 and the preceding release 10.8.1.2.
Overview
The most up to date information about Derby releases can be found on the Derby download page.
Apache Derby is a pure Java relational database engine using standard SQL and JDBC as its APIs. More information about Derby can be found on the Apache web site. Derby functionality includes:
- Embedded engine with JDBC drivers
- Network Server
- Network client JDBC drivers
- Command line tools: ij (SQL scripting), dblook (schema dump) and sysinfo (system info)
Java and JDBC versions supported:
- Java SE 1.4 and higher with JDBC 2.1, 3.0, 4.0 and 4.1
- Java ME CDC/Foundation Profile 1.1 with JSR-169 JDBC Optional Package for CDC/Foundation Profile.
New Features
This is a bug fix release. No new features were added.
Bug Fixes
The following issues are addressed by Derby release 10.8.1.6. These issues are not addressed in the preceding 10.8.1.2 release.
| Issue Id | Description |
| DERBY-5402 | Assignment instead of comparison in Driver20.getPropertyInfo |
| DERBY-5396 | DRDAStatement and DRDAConnThread swallow IOExceptions |
| DERBY-5395 | By default, only the DBO should be allowed to run several of the diagnostic VTIs. |
| DERBY-5393 | Remove old in-memory database purge mechanism |
| DERBY-5391 | The syscs_diag.error_log_reader() and syscs_diag.statement_duration() vtis do not work on derby error logs created since 10.7.1 |
| DERBY-5390 | NPE in BasicDatabase.stop in replication slave mode (dd.clearSequenceCaches) |
| DERBY-5385 | Improve documentation for OFFSET/FETCH NEXT |
| DERBY-5384 | Reference Guide talks about a DriverManager method which does not exist. |
| DERBY-5376 | Documentation should state authentication/authorization requirements more strongly |
| DERBY-5372 | Need to document that the != and <> operators are pushed into Restricted table functions (once the work on DERBY-5369 wraps up) |
| DERBY-5362 | HTML frameset files lack closing newline character |
| DERBY-5361 | Document use of URLs with SQLJ.INSTALL_JAR |
| DERBY-5354 | Remove unnecessary dita.regex build target |
| DERBY-5352 | Derby table functions stored in a jar file inside the database which implement VTICosting or RestrictedVTI fail with ClassNotFoundException |
| DERBY-5350 | Devguide needs update for definer's rights |
| DERBY-5339 | Sample domain names should follow RFC 2606 conventions |
| DERBY-5336 | Repeated database creation causes OutOfMemoryError |
| DERBY-5334 | Incorrect permission arguments given for SYSCS_UTIL.SYSCS_SET_USER_ACCESS |
| DERBY-5333 | Intermittent assert failure in testInterruptShutdown: thread's interrupted flag lost after shutdown |
| DERBY-5331 | Incorrect use of CharsetEncoder in DDMWriter |
| DERBY-5329 | Document who is allowed to run which system procedures/functions. |
| DERBY-5325 | Checkpoint fails with ClosedChannelException in InterruptResilienceTest |
| DERBY-5318 | Use assertDirectoryDeleted in ReplicationRun and remove dead code |
| DERBY-5314 | Enable i18n tests in non-English locales |
| DERBY-5312 | InterruptResilienceTest failed with ERROR 40XD1: Container was opened in read-only mode. |
| DERBY-5307 | Document the behavior of the derby.language.sequence.preallocator property. |
| DERBY-5304 | test_derby_4779 (lang.GeneratedColumnsTest) fails with ibm 1.4.2; ERROR 42X50; No method was found that matched the method call java.lang.Integer.signum(int) |
| DERBY-5299 | Document what you should expect to see if you enable authentication/authorization on a database which was created without those safeguards. |
| DERBY-5292 | SQLAuthorisation and views |
| DERBY-5291 | test failure: NullPointerException with J2ME (weme 6.2) in testDerby4137_TransactionTimeoutSpecifiedNotExceeded(org.apache.derbyTesting.functionTests.tests.memory.XAMemTest) |
| DERBY-5289 | Unable to boot 10.5.1.1 database - fails during soft/hard upgrade process for a new version number while trying to drop jdbc metadata |
| DERBY-5284 | A derby crash at exactly right time during a btree split can cause a corrupt db which can not be booted. |
| DERBY-5280 | Large batch of DDL in a database procedure dies on a transaction severity error. |
| DERBY-5278 | AssertionFailedError in IndexSplitDeadlockTest.testBTreeForwardScan_fetchRows_resumeAfterWait_unique_split() |
| DERBY-5276 | Reference manual has wrong length for BIGINT columns in system tables |
| DERBY-5274 | getColumns() doesn't work with auto generated identity columns that start with large numbers |
| DERBY-5271 | Client may hang if the server crashes due to a java.lang.Error |
| DERBY-5264 | OOM issue using XA with timeouts with Java 1.4 |
| DERBY-5262 | Running JUnit tests with Java 1.4.2 fails if the package private tests are on the classpath |
| DERBY-5258 | btree post commit releases latch before committing/aborting purges, possibly allowing other operation on page |
| DERBY-5255 | Fix more difficult table problems |
| DERBY-5254 | The keywords introduced by the CREATE SEQUENCE work are treated as reserved rather than unreserved. |
| DERBY-5253 | Engine code references org.apache.derby.shared.common.sanity.SanityManager |
| DERBY-5252 | make GrantRevokeTest pass in non-English locale |
| DERBY-5251 | make ErrorCodeTest pass in non-English locale |
| DERBY-5249 | A table created with 10.0.2.1 with constraints cannot be dropped with 10.5 due to NullPointerException with insane build or ASSERT FAILED Failed to find sharable conglomerate descriptor for index conglomerate with sane build |
| DERBY-5247 | Warnings regarding XPath displayed when generating JavaDoc |
| DERBY-5243 | assert failure in test testRAFReadWriteMultipleThreads: interrupted flag cleared |
| DERBY-5239 | Remove usages of DriverManager to obtain an Embedded Connection in Derby Server |
| DERBY-5238 | VARCHAR size typos in some documentation topics |
| DERBY-5233 | Interrupt of create table or index (i.e. a container) will throw XSDF1 under NIO - connection survives |
| DERBY-5226 | SQLJ system procedures should be documented in Reference Manual |
| DERBY-5223 | Thread's interrupted flag not always preserved after Derby returns from JDBC API call |
| DERBY-5222 | Compatibility tests fail to delete database directory |
| DERBY-5217 | make ImportExportIJTest pass in non-English locale |
| DERBY-5215 | Localize messages introduced or changed in 10.7 and 10.8 |
| DERBY-5212 | Reference Manual: language on authentication/authorization needs changes for several URL attribute topics |
| DERBY-5211 | Make SysinfoCPCheckTest pass in non-English locale |
| DERBY-5205 | Documentation: toc.html files need lang attribute |
| DERBY-5204 | Misplaced p tags in release notes |
| DERBY-5203 | Documentation of drop=true attribute contains error |
| DERBY-5198 | XPLAIN table documentation needs some cleanup |
| DERBY-5191 | Documentation needed for connection URL attribute retrieveMessageText |
| DERBY-5184 | Tables in documentation need introductions and formatting fixes |
| DERBY-5158 | Incomprehensible error message on client if attempting rollback after database has been shut down. |
| DERBY-5120 | Row from SYSDEPENDS gets deleted when a table has update triggers defined on it and an upate is made to the table |
| DERBY-5108 | Intermittent failure in AutomaticIndexStatisticsTest.testShutdownWhileScanningThenDelete on Windows |
| DERBY-5098 | embedded/in-memory: SQLNonTransientConnectionException: No current connection due to invalid page format |
| DERBY-5097 | testMTSelect(org.apache.derbyTesting.functionTests.tests.store.AutomaticIndex StatisticsMultiTest)junit.framework.AssertionFailedError: failed to get statisti cs for table MTSEL (#expected=2, timeout=0) on AIX IBM JDK 1.5 |
| DERBY-5084 | convert ijConnName.sql to a ScriptTest junit test |
| DERBY-5014 | Tests should restore the timeout values to default after they are done running. |
| DERBY-4984 | ALTER TABLE DROP COLUMN may leave triggers invalid even if they are not using the column getting dropped. |
| DERBY-4779 | NPE while inserting into a table which has a generated column and an insert trigger |
| DERBY-4670 | ThreadDump class included in insane jars |
| DERBY-4669 | ClassLoaderBootTest fails if derbyclient.jar comes before derby.jar on the classpath |
| DERBY-4647 | BaseTestCase.execJavaCmd() does not work with weme 6.2 |
| DERBY-4637 | The Developer's Guide implies that, for in-memory database names, Derby does not resolve relative and absolute paths to the same in-memory database |
| DERBY-4617 | Sysinfo.testSysinfoLocale failed with IB47 M 1.6 on Windows 7 64bit |
| DERBY-4443 | Wrap rollback in exception handlers in try-catch |
| DERBY-4437 | Concurrent inserts into table with identity column perform poorly |
| DERBY-4408 | missing DOCTYPE and META tags in toc.html and index.html pages |
| DERBY-4260 | Make derbynet/NetworkServerControlClientCommandTest run regardless of the locale |
| DERBY-4200 | client side OutOfMemoryError running derbnetclientmats:jdbcapi/derbyStress |
| DERBY-4137 | OOM issue using XA with timeouts |
| DERBY-3870 | Concurrent Inserts of rows with XML data results in an exception |
| DERBY-3337 | convert jdbcapi/derbyStress.java to JUnit |
| DERBY-2625 | SEVERE error involving column-width property |
| DERBY-2623 | SEVERE error involving column-number property |
| DERBY-2254 | Assert during log file switch: log file position exceeded max log file size |
| DERBY-1903 | Convert largedata/LobLimits.java to junit |
| DERBY-1780 | Document all supplied system procedures in the Server and Administration Guide (e.g. class loading utils and import/export) |
| DERBY-484 | Documentation for derby.database.classpath in developers guide is misleading |
| DERBY-159 | When Derby runs in Network Server mode, client does not receive warnings generated by Derby - should get documented |
Issues
Compared with the previous release (10.8.1.2), Derby release 10.8.1.6 introduces the following new features and incompatibilities. These merit your special attention.
- Note for DERBY-5395: Now, only the database owner may view several diagnostic VTIs: syscs_diag.statement_cache, syscs_diag.transaction_table, syscs_diag.error_log_reader( ), and syscs_diag.statement_duration().
- Note for DERBY-4437: Abnormal shutdown may cause sequences and identity columns to leak unused, preallocated values.
Note for DERBY-5395
Summary of Change
Now, only the database owner may view several diagnostic VTIs: syscs_diag.statement_cache, syscs_diag.transaction_table, syscs_diag.error_log_reader( ), and syscs_diag.statement_duration().
Symptoms Seen by Applications Affected by Change
Previously in a database with SQL authorization enabled, any user could select from those diagnostic VTIs. Now only the database owner can.
Incompatibilities with Previous Release
Application designers should ensure that only the database owner selects from these VTIs. For most applications this should not be a problem since the VTIs are intended to be used in production only as technical support tools.
Rationale for Change
These VTIs reveal sensitive information which only authorized persons should see.
Application Changes Required
Table functions with definer's rights can be used to grant other users access to the information in these VTIs. For instance, the following technique can be used to let ordinary users view the non-sensitive data in syscs_diag.statement_cache:
First, create a static Java method which selects only the non-sensitive columns:
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
public class SafeCacheViewer
{
public static ResultSet safeCacheViewer() throws SQLException
{
return DriverManager.getConnection( "jdbc:default:connection" ).prepareStatement
( "select id, schemaName, valid, compiled_at from syscs_diag.statement_cache" ).executeQuery();
}
}
Then the database owner should register the method as a table function enjoying definer's rights, and grant EXECUTE privilege on it to PUBLIC:
create function safeCacheViewer()
returns table
(
id char( 36 ),
schemaName varchar( 128 ),
valid boolean,
compiled_at timestamp
)
language java parameter style derby_jdbc_result_set reads sql data
external security definer
external name 'SafeCacheViewer.safeCacheViewer';
grant execute on function safeCacheViewer to public;
Finally, other users can select data from the table function as follows (here test_dbo is the schema of the database owner):
select * from table( test_dbo.safeCacheViewer() ) s;
Note for DERBY-4437
Summary of Change
Abnormal shutdown may cause sequences and identity columns to leak unused, preallocated values.
Symptoms Seen by Applications Affected by Change
In previous releases, abnormal shutdown could leak up to 5 unused values per sequence. Now abnormal shutdown can leak up to 20 unused values. In addition, abnormal shutdown can leak up to 20 unused values for each identity column as well.
Orderly database shutdown occurs when a user connects to Derby using the "shutdown=true" attribute as described by the Reference Guide in the section titled "Setting attributes for the database connection URL ". Abnormal shutdown occurs when the JVM exits without first closing databases in this orderly fashion.
Incompatibilities with Previous Release
In previous releases, sequences leaked only 5 values apiece on abnormal shutdown. Now they can leak up to 20 values.
In previous releases, abnormal shutdown had no effect on identity columns. Now they too can leak up to 20 unused values apiece on abnormal shutdown.
Rationale for Change
Derby now preallocates longer ranges of upcoming values for sequences and Derby now preallocates the same sized ranges for identity columns. Preallocation results in fewer updates to the system catalogs. That, in turn, can substantially boost the concurrency of applications which use sequences and identity columns.
Application Changes Required
Applications which shut down their databases in an orderly fashion do not need to make any changes. Changes are also unnecessary for applications which exit abnormally but which can tolerate gaps of up to 20 values in sequences and identity columns. Note that Derby has never guaranteed that sequences and identity columns won't have gaps. Gaps can occur for other reasons. For instance, if a transaction aborts or is rolled back, Derby discards sequence and identity values allocated during a transaction--in this situation, gaps appear in the sequence and identity ranges.
If an application cannot tolerate gaps of this size, then Derby's behavior can be customized by setting the derby.language.sequence.preallocator property as follows:
- A number - If the property is set to be a number, then that number becomes the size of the preallocation ranges for all sequences and identity columns. Setting derby.language.sequence.preallocator=1 turns off preallocation. This causes identity columns to behave as they did in previous Derby releases. This also reduces the concurrency of sequences.
- A class name - The property can also be set to be the name of a class which implements org.apache.derby.catalog.SequencePreallocator. See Derby's public API for the javadoc which describes this interface. The user-supplied implementation of org.apache.derby.catalog.SequencePreallocator must appear on the database classpath. The class can individually customize the size of preallocation ranges for each sequence and identity column.
For more information on setting the derby.language.sequence.preallocator property, see its section under the Reference Guide topic titled "Derby property reference".
Build Environment
Derby release 10.8.1.6 was built using the following environment:
- Branch - Source code came from the 10.8 branch.
- Machine - Windows XP Professional Version 2002 Service Pack 3
- Ant - Apache Ant version 1.7.0 compiled on December 13 2006.
- JDK 1.4 - Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142ifx-20110211 (SR13 FP8+PM31983)).
- Java 6 - Java(TM) SE Runtime Environment (build pwi3260sr9fp1-2011-0208_03(SR9 FP1) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623).
- Compiler - The 1.6.0-b105 javac was used to compile all classes.
- JSR 169 - Java ME support was built using libraries from IBM's j9 jvm from WEME 6.2.
Verifying Releases
It is essential that you verify the integrity of the downloaded files using the PGP and MD5 signatures. MD5 verification ensures the file was not corrupted during the download process. PGP verification ensures that the file came from a certain person.
The PGP signatures can be verified using
PGP or
GPG.
First download the Apache Derby
KEYS
as well as the asc signature file for the particular
distribution. It is important that you get these files from the ultimate
trusted source - the main ASF distribution site, rather than from a mirror.
Then verify the signatures using ...
% pgpk -a KEYS % pgpv db-derby-X.Y.tar.gz.asc or % pgp -ka KEYS % pgp db-derby-X.Y.tar.gz.asc or % gpg --import KEYS % gpg --verify db-derby-X.Y.tar.gz.asc
To verify the MD5 signature on the files, you need to use a program
called md5 or md5sum, which is
included in many unix distributions. It is also available as part of
GNU
Textutils. Windows users can get binary md5 programs from here, here, or
here.
We strongly recommend that you verify your downloads with both PGP and MD5.
