Contents
The following tables list resolved issues for each Live Datamart release.
TIBCO Live Datamart 2.0.4 is a service pack release with updates and enhancements. Live Datamart 2.0.4 inherits all fixes on the 1.6.x release branch through 1.6.5. The following issues were corrected in this release.
Number | Resolution |
---|---|
SB‑28030 | Prior to release 2.0.4, deleting a row via the publish path was less efficient than publishing a row. This was optimized so that deleting a row now costs about as much as publishing one. |
CQS‑3169 | Table row deletes using the data path were failing to honor the case insensitive directive for the primary key field, and thus were always case sensitive. This was fixed. |
CQS‑3165 | A null pointer exception could occur when new rows were inserted following a delete into a StreamBase Query Table exposed to the LiveView server. The cause was identified and corrected. |
CQS‑3141 | In the Alert Send Tuple action, when the connection to the configured StreamBase Server was broken, it would never try to reconnect. LiveView clients now try to reconnect each time another Send Tuple action is fired to that StreamBase Server. |
CQS‑3138 | Values set in the LiveView URI client-info query parameter could not use URI encoded characters. This was fixed. |
CQS‑3119 | In previous releases, for tables configured with periodic publish, if a row was added then removed within the publish period, clients would see a delete event for a row that was never added. This was corrected for releases 1.6.5 and 2.0.4. |
CQS‑3115 | In previous releases, join target tables that were configured with the snapshot-parallelism attribute set greater than 1 would prevent LiveView Server from completing startup. This was fixed for releases 1.6.5 and 2.0.4. |
CQS‑3114 | LiveView Desktop would restart all queries every five minutes, which would cause the server to resend snapshots of the query results. This is no longer the case: the initial snapshot is received only when the query is started, and after that, query updates keep LiveView Desktop up-to-date. |
CQS‑3102, CQS‑3099 | Under certain circumstances, in LiveView Desktop, a time series chart such as a line graph might have displayed erroneous values, due to an interpolation setting that was not user configurable. This automatic interpolation was removed, and a time series lines now display only actual values. This fix also corrected an issue with time series line graphs plotting incorrectly. |
CQS‑3092 | In previous releases, LiveView Desktop could fail to draw open-high-low-close graphs. The cause was identified and corrected. |
TIBCO Live Datamart 2.0.3 is a service pack release with updates and enhancements. Live Datamart 2.0.3 inherits all fixes on the 1.6.x release branch through 1.6.4. The following issues were corrected in this release.
Number | Resolution |
---|---|
CQS‑3082 |
With LiveView Desktop connected to a LiveView Server with running queries, if
the server is then shut down, the query views would display (Not Connected) in their top status bars — which was correct
while the server was, in fact, down. However, when the server was restarted
and the Desktop reconnected (using →
), the query views would
still display the (Not Connected) message, even
though the contents of those views had begun updating again. This was fixed
such that the (Not Connected) message only
displays when the Desktop is genuinely not connected to the server.
|
CQS‑3074 |
Predicates that contained index key fields set to null would sometimes return
an error. The cause was identified and corrected in releases 1.6.5 and 2.0.3.
A workaround for earlier releases is to set the system property liveview.query.unique.plans to 1.
|
CQS‑3072 |
For dynamic aggregation queries only, and only the continuous portion
thereof, and only for predicates that are planned where there is more than
one value used for index equity, client data updates could be missed. The way
to tell whether a predicate has more than one index equity is by looking in
the server log for instances of Predicate rewritten:
<re-written predicate> plans: X, unique plans: Y . If Y is
greater than 1, then this issue can occur.
This situation was corrected in LiveView 1.6.5 and 2.0.3. For LiveView
1.6.4 and below, and for 2.0.0 through 2.0.2, you can work around this
issue by setting the system property |
CQS‑3053 |
The <adapter-configurations> element,
newly added to the XML syntax of server configuration files in release 7.5.0,
was not correctly copied to the generated lv-bin/sbd.sbconf when starting LiveView Server. This
prevented the use in LiveView projects of adapters that use this feature,
such as the ActiveSpaces operators. The cause was identified and corrected in
StreamBase 7.5.3.
|
CQS‑2536 |
The Not Connected message in LiveView Desktop's
bottom right status bar was trying to squeeze into a non-resizable field that
just fit the word Connected . This was fixed.
|
TIBCO Live Datamart 2.0.2 is a service pack release with updates and enhancements. Live Datamart 2.0.2 inherits all fixes on the 1.6.x release branch through 1.6.4. The following issues were corrected in this release.
Number | Resolution |
---|---|
CQS‑2961 | The lastval() aggregate function could sometimes return incorrect values. Tables that had a higher snapshot-parallelism setting and predicates that underflowed for any reason would exacerbate the problem. This was fixed. |
TIBCO Live Datamart 2.0.1 is a service pack release with updates and enhancements. Live Datamart 2.0.1 inherits all fixes on the 1.6.x release branch through 1.6.3. The following issues were corrected in this release.
Number | Resolution |
---|---|
CQS‑2919 | In LiveView Desktop, when connected to a LiveView Server, in the | → dialog, the button could fail to restore the dialog. This was fixed.
CQS‑2918 | In LiveView Desktop, with a tabular query view whose query is not running (because it is paused or has hit a row limit), if you right-clicked in that view and chose either Columns or Notifications, an internal exception would prevent the expected dialog from appearing. This was corrected. |
CQS‑2844 | Deleting rows via the DataIn path was unexpectedly slow. The delete performance was greatly improved. |
CQS‑2837 |
A transform application referencing an aggregation table failed to see delete events when a row left aggregation scope, preventing the transform from acting on these events or sending a delete action into the recipient table.
As of release 2.0.1, transform applications now see these events as an
input tuple with To migrate an existing transform application:
If you expect delete events and wish to act on them, continue with the following migration steps:
|
CQS‑2756 | In release 2.0.0, the Jetty web server launched as part of LiveView Server was locking HTML files under its control by default when running, which affected development of new and updated HTML files, especially on Windows. As of release 2.0.1, the server no longer locks its files by default. |
CQS‑2475 | If a LiveView data table had a snapshot parallelism setting of 1, and a query with a limit of X was issued where there were exactly X rows that matched the query, all X rows would be delivered to the client, but then a snapshot exceeded exception was thrown. This was fixed. |
TIBCO Live Datamart 2.0.0 is a major release with updates and enhancements, and corrections for the issues in the following table. Live Datamart 2.0.0 inherits all fixes on the 1.6.x release branch through 1.6.3.
Number | Resolution |
---|---|
CQS‑2430 |
The text of the EOF reading data from binary
stream DEBUG message was changed to indicate that EOF and I/O
exceptions incurred just after a server connection is closed are normal and
can be safely ignored.
|
-
TIBCO Live Datamart 1.6.5 is a service pack release, correcting the following issues. Live Datamart 1.6.5 inherits all fixes on the 1.5.x release branch through 1.5.7.
Number | Resolution |
---|---|
CQS‑3118 | In previous releases, for tables configured with periodic publish, if a row was added then removed within the publish period, clients would see a delete event for a row that was never added. This was corrected for releases 1.6.5 and 2.0.4. |
CQS‑3115 | In previous releases, join target tables that had the snapshot-parallelism attribute set greater than 1 would prevent LiveView server from completing startup. This was fixed for releases 1.6.5 and 2.0.4. |
CQS‑3074 |
Predicates that contained index key fields set to null would sometimes return
an error. The cause was identified and corrected in releases 1.6.5 and 2.0.3.
A workaround for earlier releases is to set the system property liveview.query.unique.plans to 1.
|
CQS‑3072 |
For dynamic aggregation queries only, and only the continuous portion
thereof, and only for predicates that are planned where there is more than
one value used for index equity, client data updates could be missed. The way
to tell whether a predicate has more than one index equity is by looking in
the server log for instances of Predicate rewritten:
<re-written predicate> plans: X, unique plans: Y . If Y is
greater than 1, then this issue can occur.
This situation was corrected in LiveView 1.6.5 and 2.0.3. For LiveView
1.6.4 and below, and for 2.0.0 through 2.0.2, you can work around this
issue by setting the system property |
TIBCO Live Datamart 1.6.4 is a service pack release with updates and enhancements. The following issues were corrected in this release. Live Datamart 1.6.4 inherits all fixes on the 1.5.x release branch through 1.5.7.
Number | Resolution |
---|---|
CQS‑2930 | LiveView Server startup time was substantially improved when starting a configuration that has already run at least once, and has no configuration changes. |
CQS‑2871 | In LiveView Desktop 1.6.3, trying to re-open a configured table action failed when the selected row contained a colon anywhere, including in timestamp fields. This occurred when the Open new view View Settings option was selected, which is the default setting. The cause was identified and corrected. |
CQS-2847 | If a table index was defined as case insensitive, and a query predicate was planned to use that index, and the index matching string value contained a close-parenthesis character, then the continuous portion of query would not return results when it should. This was fixed. Note that the snapshot portion of the query is always correct. |
TIBCO LiveView® 1.6.3 is a service pack release with updates and enhancements. The following issues were corrected in this release. LiveView 1.6.3 inherits all fixes on the 1.5.x release branch through 1.5.7.
Number | Resolution |
---|---|
CQS‑2576 |
In previous releases, the lv-client command accepted a URI as the
argument to its -u option, but did not recognize
options appended to the URI with standard question-mark syntax. Starting with
release 1.6.3, lv-client
accepts the full URI syntax including options. For example:
lv-client -u lv://lvserver:10090?client-info=StatusMonitor |
CQS‑2557 | The names of spaces in TIBCO ActiveSpaces can contain characters that are not valid StreamBase characters. In previous releases, such spaces could not be used with LiveView. Starting with this release, LiveView detects invalid characters in ActiveSpaces space names and converts each to an underscore. This allows such spaces to be used with LiveView, but with converted names. |
TIBCO LiveView® 1.6.2 is a service pack release with new features and enhancements. The following issues were corrected in this release. LiveView 1.6.2 inherits all fixes on the 1.5.x release branch through 1.5.7.
Number | Resolution |
---|---|
CQS‑2553 |
In previous releases, the LiveView Delete adapter would accept a predicate
with a limit specifier, but the limit was ignored. This is now fixed such
that a delete predicate with no limit specifier means there is no limit to
the number of rows deleted, and a predicate with a limit specifier
will delete from zero to no more than n rows.
|
CQS‑2531 | In some cases, LiveView 1.6.0 clients connecting to a LiveView 1.6.1 server did not receive remove events. The cause was identified and corrected such that all 1.6.x clients are expected to interoperate with any 1.6.x server. |
CQS‑2522 | In previous releases of LiveView Desktop, when you selected columns and rows in a grid view and copied them to another program such as Microsoft Excel, the copied column order would remain in the underlying LiveView table's column order. This was corrected so that grid copies now preserve the current, visible column order in LIveView Desktop. |
CQS‑2480 | In previous releases, if the StreamBase and LiveView server ports were incorrectly configured to be the same, the StreamBase server would fail to start with a confusing error message. The error message was clarified. |
CQS‑2398 | In previous releases, if you used the Select button in LiveView Desktop's Connect to LiveView dialog to select a downloadable workspace, the resulting Desktop perspectives could incorrectly overlap. The cause was identified and corrected. |
CQS‑2275 | LiveView Desktop sometimes showed a black background behind DataWatch (Panopticon) charts. This release includes updated DataWatch libraries that resolve those issues. |
LiveView 1.6.1 is a service pack release with new features and enhancements.
Number | Resolution |
---|---|
CQS‑2196 | In some cases, the .NET API would not correctly read a URI that passed in parameters. This was fixed. |
CQS‑2242 | An aggregate table that used the expression Max(timestamp) would fail. This was fixed. |
CQS‑2394 | In certain rare conditions, LiveView tables with snapshot-parallelism greater than one might drop a snapshot add event. A run-time exception warning is written to the server log, but the client gets no notification. (Continuous queries do not have this issue.) This was fixed. |
CQS‑2422 | Queries of type snapshot and continuous with query predicates that have index equality terms on more then one index that were issued against tables with multiple secondary indices could miss continuous data updates. (The snapshot portion of the query is always correct.) This was fixed. |
LiveView 1.6 is a minor release with new features and enhancements.
Number | Resolution |
---|---|
CQS‑2320 | In LiveView Desktop, some grid view query formatting, such as column reordering, hiding, or width adjustments, would be removed if the query was edited or refreshed. This was fixed. |
CQS‑2273 | In the Java API, if query listeners threw unhandled exceptions while processing events provided to them by LiveView's API, the server connection closed. This behaviour was changed. Now, the query listener receives the exception thrown via #getExceptionRaised, the query is closed, but the connection is unaffected. |