Release 7.2.0
Change to SQL Server Dialect in datasource file
If you are running against a SQL Sever database, you need to update the dialect specified in the datasource file. The Standard Upgrade Instructions describe managing your phixflow-datasource.xml file, and migrating this to the new release. In this file you will have:
<prop key="hibernate.dialect">org.hibernate.dialect.SQLServerDialect</prop>
Update this to say:
<prop key="hibernate.dialect">org.hibernate.dialect.SQLServer2012Dialect</prop>
New Graphical User Interface for design component
This release is the first to feature the design component of PhixFlow in the new presentation technology, which uses HTML5 rather than flash.
The design component has also been given a new look a feel, to support creating models and rich applications.
Features and Improvements
URLs for opening PhixFlow and applications
The URLs used to start PhixFlow in standard mode, or to go straight to an application, have changed. See Start PhixFlow on the Client for details.
Performance
It is now possible to specify on a stream by stream basis
- whether any indices should created during publishing
- whether inserts into Oracle should be direct paths inserts
Bug Fixes
Cache refreshes after PhixFlow upgrades
It is no longer necessary to clear your browser cache after upgrading PhixFlow. Previously, in some cases after an upgrade, you would get an error telling you that the client and server version did not match, and to resolve this, you would need to clear your browser cache.
Analysis fixes
Recovery after cancellation
If an analysis run was cancelled then re-run, the following run would always fail as it tried to roll back the incomplete results of the first run. This is now fixed.
Lookup pipe failures sometimes ignored
In some cases, lookup pipe failures were reported but did not cause stream data generation to fail. This problem was introduced in 6.0. This is now fixed.
Try function
The try() attribute function sometimes handled a failure of its first parameter incorrectly, reporting instead 'Stack Corrupted'. For example, if the expression being tested attempted a divide by zero. This is now fixed, and in such cases an error will be detected, and the expression in the failure argument of the try() function will be evaluated.