Skip to content

Releases: IBMStreams/streamsx.eval_predicate

streamsx.eval_predicate toolkit v1.2.2

Choose a tag to compare

@nysenthil nysenthil released this 09 Feb 22:13

This release adds new header comments to the source code. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.2.0

Choose a tag to compare

@nysenthil nysenthil released this 17 Jul 01:23

This release adds a new feature to support a rule expression that has two self-enclosed multi-level subexpressions placed on each side of a logical operator. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.1.9

Choose a tag to compare

@nysenthil nysenthil released this 05 Mar 15:57

This release has a new rearrangement of the directories containing the toolkit logic and the example applications. There is no feature or functional change done in this release. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.1.8

Choose a tag to compare

@nysenthil nysenthil released this 11 Oct 16:17

This release has a fix to correctly evaluate multi-level nested subexpression patterns as shown in the test cases A51.22 to A51.24 in the FunctionalTests.spl file. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.1.7

Choose a tag to compare

@nysenthil nysenthil released this 27 Sep 19:20

This release has a fix to correctly evaluate a particular multi-level nested subexpression as shown in the test case A51.21 in the FunctionalTests.spl file. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.1.6

Choose a tag to compare

@nysenthil nysenthil released this 20 Sep 16:02

This release adds a new feature to evaluate multi-level nested subexpressions present in a user-defined business rule. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.1.5

Choose a tag to compare

@nysenthil nysenthil released this 10 Jan 18:50

This release adds an inline directive to the C++ function get_tuple_schema_and_attribute_info which can be used to get the tuple schema along with a map of fully qualified attribute names as map keys with their SPL type names as map values. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.1.4

Choose a tag to compare

@nysenthil nysenthil released this 08 Jan 02:45

This release adds a new function get_tuple_schema_and_attribute_info to fetch the tuple schema literal string and the tuple attribute information map with fully qualified tuple attribute names and their SPL type names as key/value pairs in that map.. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.1.3

Choose a tag to compare

@nysenthil nysenthil released this 17 Oct 01:52

This release enhances the function compare_tuple_attributes to compare the attribute values of two tuples that are based on the same schema and then give back a list containing the attribute names that have matching values and another list containing the attribute names that have differing values. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

streamsx.eval_predicate toolkit v1.1.2

Choose a tag to compare

@nysenthil nysenthil released this 16 Oct 22:39

This release adds a new function compare_tuple_attributes to compare the attribute values of two tuples that are based on the same schema. Please always use the tar.gz file that has version number, date, time, MD5 and sha1.

What's new: CHANGELOG.md

Note: Though this toolkit release works fine, the next release after this one has an enhancement to receive matching as well as differing attribute names. For future API compatibility, it is better to use v1.1.3 of this toolkit. So, it is better not to use this release i.e. v1.1.2.