What are you trying to achieve when you say your task is 'log processing'
 
Will ALL Log entries(objects) be of interest
Assuming NOT - you can (maybe) write some Rules which filter your input so that ONLY those Log entries you need to process are committed to the working memory
(you will probably have to Load each Log entry into the working memory & have your 'Filter Rules' Retract Log entries that you are not interested in)
 
Subsequent Rules can process the 'Real' Log entries however you need to
 
Haven't tried any of this myself  - BUT I think you should be able to make it work
 
 
 
 

From: 张茂森 [mailto:[EMAIL PROTECTED]
Sent: Friday, November 10, 2006 2:46 AM
To: [email protected]
Subject: [drools-user] Some thoughts about drools

Hi All:

After I have read the drools user guide, and now my work is about log processing. I want to know whether rule engine is proper to be used to do log processing.

1         Log can be a very large “fact” set (even tera-bytes is possible). Could Rule Engine achieve the requirement of performance?

2         As far as I know, I must wrap each log into object then send it to workmemory of Rule Engine, Does it need? Could I have some more lightweight solution?

Any suggestion would be appreciated

Thank you!

 

 

Reply via email to