5:59 p.m.
Would someone be so kind to describe exactly what happens when we hot deploy a rule change
to a stateful session. It looks like the old version of the rule is deleted, in turn
forcing a retraction of any RHS that was logically inserted (all our inserts are logical)
as a consequence of this rule (and any cascading effects) that has no other LHS to support
its existence. Then the new rule is inserted, the agenda is rebuilt based on the current
working memory contents, and the rule is automatically fired (in our case recreating
everything it just deleted)
Do I have this right?
Is there a way to change the behavior to be less invasive? This "rebuild" can
take minutes, and I am not running at high volume yet.
For example what if the updated rule logically has no impact on existing working memory
contents, let's say it's a maintenance change for future facts or new conditions?
If the operation did not delete and rebuild everything, rather if it determined the impact
of the change, and only replaced retracted/deleted what is affected by the logic change,
would this be faster?
Bottom line it would be highly desirable for this to be minimally invasive.
thanks
[cid:image001.gif@01CDF7F0.4B5CB130]
Bill Guinn | Sr. Vice President, and CTO
SUMMUS Software, Inc.
3179 Skyway Court, Fremont, CA 94539
510.780.3895 office | 916.715.6433 mobile
@summussoftware twitter
william.guinn@summussoftware.com<mailto:kl@summussoftware.com>
[cid:image002.png@01CDF7F0.4B5CB130] [cid:image003.jpg@01CDF7F0.4B5CB130]
<http://www.summussoftware.com/pdfs/EMA_NGITM-Q4-2012_Radar_Summus-Profile...
________________________________
NOTICE TO RECIPIENT: THIS E-MAIL (INCLUDING ANY ATTACHMENTS) IS MEANT FOR ONLY THE
INTENDED RECIPIENT OF THE TRANSMISSION, MAY CONTAIN CONFIDENTIAL INFORMATION, AND IS
PROTECTED BY LAW. IF YOU RECEIVED THIS E-MAIL IN ERROR, PLEASE IMMEDIATELY NOTIFY THE
SENDER OF THE ERROR BY RETURN E-MAIL, DELETE THIS COMMUNICATION AND SHRED ANY ATTACHMENTS.
UNAUTHORIZED REVIEW, USE, DISSEMINATION, DISTRIBUTION, COPYING OR TAKING OF ANY ACTION
BASED ON THIS COMMUNICATION IS STRICTLY PROHIBITED.
6:44 p.m.
You have it right.
If any rule is modified, it's effective removed and added. Removal of a rule,
remove's all it's matches, activations and logical inserts.
There is no way to preserve this information for a rule that modified.
It would be very hard to determine what information is or is not safe to preserve.
If the rule is a very minor change then add a new rule instead, it will re-use all the
available sharing (matched information). It can build up a second set of justifiers for
the logical insertions. Then you can remove the old role.
Mark
On 21 Jan 2013, at 23:59, William Guinn <William.Guinn(a)summussoftware.com> wrote:
Would someone be so kind to describe exactly what happens when we hot
deploy a rule change to a stateful session. It looks like the old version of the rule is
deleted, in turn forcing a retraction of any RHS that was logically inserted (all our
inserts are logical) as a consequence of this rule (and any cascading effects) that has no
other LHS to support its existence. Then the new rule is inserted, the agenda is rebuilt
based on the current working memory contents, and the rule is automatically fired (in our
case recreating everything it just deleted)
Do I have this right?
Is there a way to change the behavior to be less invasive? This "rebuild" can
take minutes, and I am not running at high volume yet.
For example what if the updated rule logically has no impact on existing working memory
contents, let’s say it’s a maintenance change for future facts or new conditions? If the
operation did not delete and rebuild everything, rather if it determined the impact of the
change, and only replaced retracted/deleted what is affected by the logic change, would
this be faster?
Bottom line it would be highly desirable for this to be minimally invasive.
thanks
<image001.gif>
Bill Guinn | Sr. Vice President, and CTO
SUMMUS Software, Inc.
3179 Skyway Court, Fremont, CA 94539
510.780.3895 office | 916.715.6433 mobile
@summussoftware twitter
william.guinn(a)summussoftware.com
<image002.png> <image003.jpg>
NOTICE TO RECIPIENT: THIS E-MAIL (INCLUDING ANY ATTACHMENTS) IS MEANT FOR ONLY THE
INTENDED RECIPIENT OF THE TRANSMISSION, MAY CONTAIN CONFIDENTIAL INFORMATION, AND IS
PROTECTED BY LAW. IF YOU RECEIVED THIS E-MAIL IN ERROR, PLEASE IMMEDIATELY NOTIFY THE
SENDER OF THE ERROR BY RETURN E-MAIL, DELETE THIS COMMUNICATION AND SHRED ANY ATTACHMENTS.
UNAUTHORIZED REVIEW, USE, DISSEMINATION, DISTRIBUTION, COPYING OR TAKING OF ANY ACTION
BASED ON THIS COMMUNICATION IS STRICTLY PROHIBITED.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
4326
days inactive
4327
days old
1 comments
2 participants
participants (2)
-
Mark Proctor -
William Guinn