/**
 * Job for purging expired documents from the search index.
 * This job removes documents that have passed their expiration time based on the expires field.
 * It helps maintain the search index by cleaning up outdated content automatically.
 */
public class PurgeDocJob {

    /** Logger instance for this class */
    private static final Logger logger = LogManager.getLogger(PurgeDocJob.class);

    /**

        }

        response.body.closeQuietly()

        if (++followUpCount > MAX_FOLLOW_UPS) {
          call.eventListener.followUpDecision(call, response, null)
          throw ProtocolException("Too many follow-up requests: $followUpCount")
        }

        call.eventListener.followUpDecision(call, response, followUp)
        request = followUp
        priorResponse = response
      } finally {

        return ResourceBundleUtil.getBundle(systemName + MESSAGES, LocaleUtil.getDefault());
    }

    /**
     * Returns a message with arguments lined up without using a pattern.
     *
     * @param args
     *            Arguments
     * @return Message with arguments lined up
     */
    protected static String getNoPatternMessage(final Object... args) {
        if (args == null || args.length == 0) {
            return "";

   * numElements} elements are not available, it will wait for them up to the specified timeout.
   *
   * @param q the blocking queue to be drained
   * @param buffer where to add the transferred elements
   * @param numElements the number of elements to be waited for
   * @param timeout how long to wait before giving up
   * @return the number of elements transferred

   * numElements} elements are not available, it will wait for them up to the specified timeout.
   *
   * @param q the blocking queue to be drained
   * @param buffer where to add the transferred elements
   * @param numElements the number of elements to be waited for
   * @param timeout how long to wait before giving up
   * @return the number of elements transferred

        it just seem like a sensible behavior for the feature to have?


        Before we make significant changes to existing features in Guava, we really want to be sure
        that it's for a use case that actually comes up in the real world. We want to hear the
        real-world use case so the community can discuss and debate whether this feature is actually

        ComponentUtil.getRelatedQueryHelper().update();
    }

    /**
     * Sets up the search conditions for the related query list based on the pager parameters.
     * This method configures wildcard searches for term and queries fields, and sets up ordering.
     *
     * @param cb the condition bean for building the query

    assertTrue(task.isDone());
    assertFalse(task.isCancelled());
  }

  public void testListenerCalledOnException() throws Exception {
    throwException = true;

    // Start up the task and unblock the latch to finish the task.
    exec.execute(task);
    runLatch.await();
    taskLatch.countDown();

    ExecutionException e = assertThrows(ExecutionException.class, () -> task.get(5, SECONDS));

        ComponentUtil.getRelatedContentHelper().update();
    }

    /**
     * Sets up the search conditions for listing related content entities.
     * Configures wildcard searches for term and content fields, and sets up ordering.
     *
     * @param cb the condition bean for building the query
     * @param relatedContentPager the pager containing search parameters
     */

              : Double.NEGATIVE_INFINITY;
        case CEILING:
          return (roundArbitrarily == Double.POSITIVE_INFINITY)
              ? Double.POSITIVE_INFINITY
              : -Double.MAX_VALUE;
        case UP:
          return roundArbitrarily;
        case UNNECESSARY:
          throw new ArithmeticException(x + " cannot be represented precisely as a double");
      }
    }