minor formatting
more clean up for job alert runner. a lot more methods and objects
are static. It is now obvious that the object is really just a wrapper
for a single boolean in spawn (whether alerts are enabled).
(the only two fields are the reference to spawn and the enabled boolean,
and the spawn reference is final. So, eg. the class could be turned into
an entirely static utility class if that boolean were held in spawn and
passed in to scan alerts, or more likely, just moved the single enclosing if
statement out of scan alerts)
also some other clean up and optimizations
now the reason I went to this class: changed spawn alert email subjects
to encourage threading of emails. If it works correctly, may want to try
threading by job id instead of (job id, alert type) tuples
change name of this inner test class to not mess up navigation
formatting, cleanup on mqs
Use the most recent version of the dropwizard-auth library.
Revert alert refactor 1 (imported to different branch)
Alert revert 2. Imported to different branch.
Alert revert 3. Imported to minor branch.
don't have async queries run twice. This moves them closer to the do-nothing
option they are, and let's me trim a little fat. more elaborately, the async
option performs no functional purpose -- it doesn't do anything that running
the same query twice wouldn't do. I would destroy it now except for legacy.
checkpoint for query cache removal and massive cleanup
this really needs its own commit
going to assume this is what they meant. the reference in Query probably
does not technically have to be volatile because we won't be interested
in it until after a query source has been put onto and pulled off of a
concurrent queue, but this is a little more explicit and the source
reader queue is going to get the axe.
removing more unused features with questionable value
Adding a method to the ConcurrentTree for testing purposes that will walk over all the
pages in the external storage and test whether the nextFirstKey is set to the correct key.
In the unit tests the testing of the pages must happen in the middle of closing a tree.
Testing occurs after writing all pages from memory to disk and before closing the external storage.
changes to mqs:
- gating wasn't doing anything because we were already restricted by the number
of threads. additionally this prevented queue/gate acquisition metrics from working
correctly. Gating using the semaphore is now gone along with some related code, but
a correctly functioning metric for how long a query had to wait before running is now
in place
simple cleanup for mesh file ref cache and disable qcs for tasks by default
fix method order and docs
- moved mqs and qec to the data module to support matt's dream of live queries
- removed bdb specific catch block in mqs that is no longer desirable and dead code
that resulted
experimental support for live queries. Seed command apparently useless so ran out of time
for testing, but it is at least as functional the old version (which was not at all functional)