Robert, IIRC, the bottleneck on my end was getting the unit tests to pass. The patch caused some failures (in a feature I wanted to deprecate anyway), but I have not had time to get to it. Now that two people want the feature, I'll try to prioritize.
Thanks again for the patch :-) -- Shawn On Jun 7, 12:48 pm, Robert Kluin <[email protected]> wrote: > I can relate to latency on projects. Have some updates I need to push > out to stuff as well. > > Maybe we'll find one or more volunteers will to help contribute new > code and / or test this patch. :) > > Robert > > > > > > > > On Tue, Jun 7, 2011 at 13:31, Jason Collins <[email protected]> wrote: > > Yup, you're right Robert. That patch would address this issue, but we > > haven't applied yet. Nothing wrong with the patch, just some latency > > on the open source project in general. > > j > > > On Jun 6, 8:39 pm, Robert Kluin <[email protected]> wrote: > >> Hey Jason, > >> Sounds like Mike is asking for the same thing I was when first > >> looking at Fantasm (quite some time ago now). I thought we'd came up > >> with a patch that supported this? I'm not really sure where we left > >> off with that. > > >> Robert > > >> On Mon, Jun 6, 2011 at 13:04, Jason Collins <[email protected]> > >> wrote: > >> > Currently, the fan_in aggregation rules cannot be customized; Fantasm > >> > will aggregate anything that belongs to the same machine instance. > >> > We're looking at some possible adjustments to this to allow developers > >> > to specify their desired fan_in semantics. No ETA. > > >> > For now, you could split your machine into two separate machines. The > >> > first machine would simply iterate through your dates and kick off a > >> > separate machine instance for each day (technically, in your case, > >> > there's no need to build a continuation over the dates - the > >> > documentation below will allow you to easily kick off multiple > >> > machines in one call). The fan_in semantics will work over each > >> > machine instance (date) separately. > > >> > See > >> > context.spawn():http://code.google.com/p/fantasm/wiki/AdvancedConcepts#Spawning_New_M... > > >> > j > > >> > On Jun 4, 8:08 am, Mike_W <[email protected]> wrote: > >> >> Hi, > >> >> I use fantasm to aggregate daily transaction > >> >> amounts.http://code.google.com/p/fantasm/wiki/GettingStarted > > >> >> This is how the current working state machine looks: > > >> >> Step-1) Class getCalendarDate -- returns a single date > >> >> Step-2) Class QueryDB is a continuation class. -- returns transaction > >> >> costs > >> >> Step-3) Class Aggregate [Fan-in] -- Aggregates daily costs. > > >> >> Step-1 passes a date to step-2. > >> >> Step-2 returns transaction details for the given date. > >> >> Step-3 creates a DailyAggregate entity with the date as the entity > >> >> name. > > >> >> This works great. > >> >> _____________________________________________________________ > > >> >> What I want to do is make > >> >> Step-1 getCalendarDate a continuation class > > >> >> I want to be able to aggregate a month's data in parallel. > > >> >> So for each date returned by Step-1, Step-2 kicks off a query [for > >> >> this date]. > >> >> This means that all 31 days in May are being queried simultaneously. > > >> >> How do I get ClassAggregate to fan in each day individually? > > >> >> Currently, when the fan in runs it aggregates all the data from Step-2 > >> >> regardless which date is being queried. > > >> >> Regards > >> >> Mike > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups "Google App Engine" group. > >> > To post to this group, send email to [email protected]. > >> > To unsubscribe from this group, send email to > >> > [email protected]. > >> > For more options, visit this group > >> > athttp://groups.google.com/group/google-appengine?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
