Re: [rules-users] Loading facts and memory size limits
It seems to me that you are planning the proverbial search for needles in a
haystack.
A better approach should be possible by monitoring the harvest while it
arrives,
one day at a time. (If you have to dig through the past, you still can do it
day
by day.) Use rules to keep track of sales events that qualify/disqualify
customers.
This should reduce the number of facts to a manageable order of magnitude,
i.e.,
the number of customers.
-W
On 9 September 2010 10:27, bellios <carfid(a)gmail.com> wrote:
In my application I would to model the Customers-Sales domain and I thought
that drools could help me to express a set of rules to capture (or execute
on-demand) some "special" customers (e.g. take the customers which not
have/have bought some products of category X in the last 6 months).
To do this i'm loading the last 6 months sales into WM, afterwards on
demand
i execute the rules. This process fails due the memory requirements. I
thought that Drools would use an hibernate/JPA/ or an incremental
mechanisms to load and process the facts.
@Swindells, Thomas: Do you think that it's the right approach?
@Michael Anstis-2: I will try to study in deep the event
processing\CEP\streaming methods.
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/Loading-facts-and-mem...
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
Attachments:
- attachment.html (text/html — 2.2 KB)