No. Not aware of any more docs on JS custom functions. I am still uncertain about not using edges and vertexes. For instance, how would you do aggregations (if you do need them) without being able to traverse upward in the hierarchy? You're basically limiting yourself, aren't you?
The only thing that comes to mind, which might help is pre-allocating, say, a day's worth of records. So, create the time based nodes before the time actually hits (the day before?), then it is a matter of only updating the nodes according to the timestamp of the data, once the data is created. This could be like your current batch job, only done earlier to pre-build the time series hierarchy. This seems plausible to me, because the time series data is a fixed or rather known data structure. The only disadvantage is if your time based data has holes in time, meaning, you don't have data for every minute of the day, you'd have nodes with no data. But, theoretically, you could clean those up the day after too. I don't know. Just throwing out some ideas...:-) Scott -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
