: can anyone confirm? everything you said sounded right to me ... scale(...) as a general purpose function probably can't be optimized very heaivly. but it would probably be possible to write an optimization specific to scale(fieldname).
I seem to recall someone saying something at some point about the idea of having the codec record stats like the min/max value of a field (per segment) ... assuming i'm not smoking crack, so you wouldn't have to do any caching, you could have an optimized "scalefield(f)" function that could fail hard if the field didn't use the expected codec type, otherwise it just asked all the atomic readers what the min/max where to find the overall min/max. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
