"so encouraging folks to conserve them by charging for bytes scanned seem like a good measure."
I wonder if it warns you about potentially expensive button clicks. A little cartesian join, and...ouch.
It’s not powerful enough to do a Cartesian join (yet?). Most you can do is scan once over a big dataset.
Hmm. I wonder if an "index only" query charges for the scan of the index, or a full table scan.
AFAICT, there is no indexing. It appears to just scan the logs as necessary. Maybe indexing will come later.
Obviously disk iops are the bottleneck with such a system, so encouraging folks to conserve them by charging for bytes scanned seem like a good measure.
Won’t an enterprise implementing this themselves or using third party tools have to scale out their index nodes based on the amount data queries are scanning?