George
11/30/2023, 3:53 PMcounter = 0
but I’m still seeing some hosts report every single app with counter = 1
. Does anyone know why this is? The docs say
For initial query results that include all records counter will be "0", while initial results without all records (like event tables) will start at "1".
while initial results without all records (like event tables) will start at “1”I don’t fully understand what this means but the apps table isn’t an event table so I don’t think it applies. It’s also not completely clear to me what the schedule epoch does - from what I understand this is an arbitrary static field I can set to any 64bit integer and it will stay the same unless I decide to change it? Thanks!
Stefano Bonicatti
11/30/2023, 7:56 PMwhile for the initial results that do not contain all records (like in the case of event tables) the counter will start at "1"
Stefano Bonicatti
11/30/2023, 8:01 PMcounter=0
then you won't get the initial results.
That been said though, if the epoch gets changed (since it can be changed remotely via a config update), the counter will start at 0 again, because the query will be forced to consider that execution as the very first one.
And so yes, the epoch
is an arbitrary integer you set, and when it changes, it forces the next query executions to be considered new/with counter = 0
George
12/01/2023, 9:58 AMcounter = 1