> Are you saying that the server load generated by such an additional aggregation query would be a blocker? If yes, how about we combine the two (for pageviews and previews) into one?
Sorry, no it isn’t a blocker. The tagging logic that Nuria and others have been working on for a while now makes this a little easier, since the webrequests only need to be read once to add all tags. It is separate than pageviews (for now), but we might use tagging for pageviews eventually too.
> I assume it could be quite analogous to the one your team has implemented for pageviews
If we did it like the linked Hive query, it would be quite a lot. We don’t want to read every webrequest from disk for every aggregate dataset. Tagging helps, since we define the set of tags and filters once, and the job that adds tags reads all webrequest once, and adds all tags.
But anyway, yes, it can be done.
I’m mostly objecting and recommending EventLogging because we really shouldn’t’ be doing searching webrequest to measure interactions over and over again. It's fragile and monolithic and not very portable. Events are better :)