*
     * @param searchEngineClient the search engine client to use for deletion
     * @param docList the list of new documents to check against
     * @return the number of old documents that were deleted
     */
    protected long deleteOldDocuments(final SearchEngineClient searchEngineClient, final DocList docList) {
        final FessConfig fessConfig = ComponentUtil.getFessConfig();

### Motivation

This library makes it easy to test that your app Does The Right Thing when it
makes HTTP and HTTPS calls. It lets you specify which responses to return and
then verify that requests were made as expected.

Because it exercises your full HTTP stack, you can be confident that you're
testing everything. You can even copy & paste HTTP responses from your real web

        String result = purgeLogJob.execute();

        // Assert all services were called
        assertTrue(deleteCrawlingInfoCalled[0]);
        assertTrue(deleteSearchLogCalled[0]);
        assertTrue(deleteJobLogCalled[0]);
        assertTrue(deleteUserInfoCalled[0]);
        assertTrue(updateJobLogStatusCalled[0]);

        // Assert correct parameters were passed - verify that time passed is greater than 0

 * the keys in the order they were first added to the multimap. Similarly, {@code get}, {@code
 * removeAll}, and {@code replaceValues} return collections that iterate through the values in the
 * order they were added. The collections generated by {@code entries} and {@code values} iterate
 * across the key-value mappings in the order they were added to the multimap.
 *

 * the order they were first added to the multimap. Similarly, {@link #get}, {@link #removeAll}, and
 * {@link #replaceValues} return collections that iterate through the values in the order they were
 * added. The collections generated by {@link #entries()}, {@link #keys()}, and {@link #values}
 * iterate across the key-value mappings in the order they were added to the multimap.
 *

        authenticationManager.addChain(chain1);
        authenticationManager.addChain(chain2);
        authenticationManager.addChain(chain3);

        // Verify all chains were added by testing their effect
        User user = createTestUser("testuser");
        authenticationManager.insert(user);

        assertEquals(1, chain1.updateCallCount);
        assertEquals(1, chain2.updateCallCount);

     * @throws IllegalArgumentException if duplicate keys or values were added
     */
    @Override
    public ImmutableBiMap<K, V> build() {
      return buildOrThrow();
    }

    /**
     * Returns a newly-created immutable bimap, or throws an exception if any key or value was added
     * more than once. The iteration order of the returned bimap is the order in which entries were

   * analysis that that means "plain {@code T}" rather than the inferred type {@code @Nullable T}.
   * (And even if annotations on local variables were permitted as an optional hint, no annotation
   * would be the right tool for the job here: {@code @Nullable} is the annotation that we're trying
   * to get rid of, and {@code @NonNull} would be wrong for our use case for the same reason as

        // Execute
        indexUpdateCallback.store(paramMap, dataMap);

        // Verify
        assertEquals(1, indexUpdateCallback.getDocumentSize());
        // Check if fields were added (they should be added by the store method)
        assertNotNull("ID should be set", dataMap.get("id"));
        assertNotNull("Doc ID should be set", dataMap.get("doc_id"));

    public String virtualHost;

    /**
     * The username who created these related queries.
     */
    @Size(max = 1000)
    public String createdBy;

    /**
     * The timestamp when these related queries were created.
     */
    @ValidateTypeFailure
    public Long createdTime;

    /**
     * Initializes the form with default values for creating new related queries.
     */
    public void initialize() {