<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Wolfgang, Thanks for the reply. The N threads means I need to be able to query/check the list very often. The through put is undetermined, but could be as high as several hundred lookups per second. It seems you agree that using a stateful session would require me to process each request serially, unless I wanted to spin up several copies of my facts. That would seem inefficient.<br>
<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
Date: Mon, 18 Apr 2011 10:05:29 +0200<br>
From: Wolfgang Laun <<a href="mailto:wolfgang.laun@gmail.com" target="_blank">wolfgang.laun@gmail.com</a>><br>
Subject: Re: [rules-users] Searching a list - Is Drools the answer?<br>
To: Rules Users List <<a href="mailto:rules-users@lists.jboss.org" target="_blank">rules-users@lists.jboss.org</a>><br>
<br></div><div><div></div><div class="h5">
It's possible that putting the "constants" into rules will result in a rule<br>
building process that's more complex than what you need to do if this data<br>
is in facts. Notice that your Object_1 has to participate in (at least)<br>
three different matching scenarios, which is a simple thing for a fact, but<br>
may need three rules if FirstName and LastName are literals in rules.<br>
<br>
A (serially) reusable Stateful Session would need to be set up with the 10k<br>
facts. A search request enters an object, produces results, and retracts the<br>
request; then the session is ready for the next request. (The N threads you<br>
are talking about results from some overall application context?)<br>
<br>
Regards<br>
Wolfgang<br>
<br>
2011/4/18 Drools User <<a href="mailto:drools2030@gmail.com" target="_blank">drools2030@gmail.com</a>><br>
<br>
> I have been using Drools for several years, but just with constraints<br>
> (rules) on 1 set of objects at a time. Think many rules, few facts in a<br>
> stateless session. I have been given a new project at the office which<br>
> requires having about 10-100k facts and few rules. These 10k facts would be<br>
> basically constants, a list of things I need to search on each request. I<br>
> would then need to load a single object, based on a request to see if my<br>
> request object matched the list. It is somewhat a simple search, but I need<br>
> to be able to inject aliases and search partial matches in addition to exact<br>
> matches. A generic example:<br>
><br>
> List:<br>
> Object 1 (FirstName=John, LastName=Smith)<br>
> Object 2 (FirstName=Will, LastName=Smith)<br>
> Object 3 (FirstName=Jon, LastName=Smith)<br>
><br>
> Request/Use Case:<br>
> LastName=Smith, would return all 3 objects, but marked as single match<br>
> LastName=Smith, Firstname =John, Would return object 1, as exact double<br>
> match, and Object 3 a nickname double match<br>
> LastName=Smith, Firstname =J, Would return object 1 and 3, as partial match<br>
><br>
> In the second request, I need to run all names through a nickname DB/list<br>
> to explode the name into multiple search patterns. Possibly using (<br>
> <a href="http://code.google.com/p/nickname-and-diminutive-names-lookup/" target="_blank">http://code.google.com/p/nickname-and-diminutive-names-lookup/</a>)<br>
><br>
> Hopefully that explains a bit about the problem.<br>
><br>
> So to the question, there are a few ways to solve this. The simplest is<br>
> just SQL from a DB, but this proves to be slow to search all the ways I<br>
> need. I need sub second response times. An in memory DB is another possible<br>
> solution we are looking at. Not to think of Drools as the golden hammer, but<br>
> this smells like something I can use Drools for. My first thought was to<br>
> load the "List" as facts into a stateful session. My concern is wouldn't I<br>
> need N copies of the list loaded to have N threads? This would be<br>
> inefficient if so. I know rules aren't copied per working memory, but is<br>
> there a way to create a master working memory for facts to use?<br>
><br>
> So my second thought is to convert my List into rules so they would only be<br>
> stored once in the system, regardless of number of threads using the engine.<br>
><br>
> What do you guys think, am I on the right track with this? Is Drools a good<br>
> way to do this or is there something better I have overlooked?<br>
><br>
> Thank you for taking the time.<br>
> -Drools user<br></div></div></blockquote></div><br>
</blockquote></div><br>