Resolution:

Description

= = = = =

What do these warnings in BE log file mean: "The following rule(s) contain non-equivalent join condition, use equivalent condition to improve performance.", "The following rule(s) contain multiple equivalent join conditions, first equivalent condition will be used to produce join result."

Resolution

=======

Warnings in log files are just to bring to the user’s attention that there may be potential issues. The warning about multiple equivalent join conditions is to let the user pay attention to the order of join if multiple equivalent join conditions are used because it has impact on optimizing the performance. Using a bad join condition may slow down the engine extensively.  

Example.

Transaction.id == EventA.tranId;
Transaction.type == EventA.tranType;

The first join may produce only one result, but the second may produce thousands of results. The message is just to warn users to make sure they are using the right join. If you think the order of the multiple equivalent join conditions is correct after evaluation, you can just ignore the warning. Non-equivalent join conditions for Terms/Identifiers in a rule will produce N x M combinations and the BE engine has to test all combinations to determine if a condition is true. But if the there is no equivalent join condition for a particular rule, you have to use non-equivalent join condition, and you can just ignore that message.

What do join condition related warnings in BE log file mean?