[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #LJG-180960]: Nested Aggregations recheckEvery

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #LJG-180960]: Nested Aggregations recheckEvery
  • Date: Fri, 14 Jun 2013 14:36:18 -0600
Mike,

I did a little more research on recheckEvery.  With your setting of 
recheckEvery at 6 hours, you shouldn't trigger a scan with a frequency 
less than 6 hours, and only when the collection is hit. So...if you're 
seeing hourly updates, then something else may be doing the triggering.  
Also, the recheckEvery goes on the innermost scan.

-Lansing

Can you zip up the files you have in cache/agg and send them to us? The 
#null might be something else to investigate.

On 6/14/2013 11:20 AM, Michael McDonald wrote:
> New Client Reply: Nested Aggregations recheckEvery
>
> Lansing,
>
>> There did use to be a radio button in 4.2 that essentially wiped out the 
>> horizontal coordinate in a request when selected; we can add this back into 
>> the interface in 4.3.18.
> Yes. I'd be interested in seeing if simply adding back this radio
> button fixes our problem. I am not too keen on keeping out NCSS
> running the old TDS and our other servers using the new. Creates
> kludgy puppet rules :)
>
>
>
> Ticket Details
> ===================
> Ticket ID: LJG-180960
> Department: Support THREDDS
> Priority: Low
> Status: Open
> Link:  
> https://www.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=22226



Ticket Details
===================
Ticket ID: LJG-180960
Department: Support THREDDS
Priority: Low
Status: Open