import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

/**
 * Use this to meta-annotate {@code XxxFeature.Require} annotations, so that those annotations can
 * be used to decide whether to apply a test to a given class-under-test.
 *
 * <p>This is needed because annotations can't implement interfaces, which is also why reflection is
 * used to extract values from the properties of the various annotations.

 * that is currently executing does not impact the ongoing run, but it does prevent a recurrence
 * from being scheduled.
 *
 * Tasks may opt-out of cancellation with `cancelable = false`. Such tasks will recur until they
 * decide not to by returning -1L.
 *
 * Task Queues
 * -----------
 *
 * Tasks are bound to the [TaskQueue] they are scheduled in. Each queue is sequential and the tasks

        try {
            final RESULT result = entityType.newInstance();
            result.setCreatedAt(toLocalDateTime(source.get("createdAt")));
            result.setDocId(DfTypeUtil.toString(source.get("docId")));
            result.setQueryId(DfTypeUtil.toString(source.get("queryId")));
            result.setUrl(DfTypeUtil.toString(source.get("url")));
            result.setUserInfoId(DfTypeUtil.toString(source.get("userInfoId")));

     * didn't see that discussed in the review, which included many other
     * changes: https://mail.openjdk.org/pipermail/core-libs-dev/2013-May/thread.html#17367
     *
     * TODO(cpovirk): decide what the best long-term action here is: force users
     * to suppress (as we do now), stop testing entrySet().add() at all, make
     * entrySet().add() tests tolerant of either behavior, introduce a map

        assertEquals(0, deletedDocIdList.size());

        docList.clear();
        deletedDocIdList.clear();
        docList.add(new HashMap<>(Map.of(//
                "config_id", "W01", //
                "doc_id", "1", //
                "url", "http://test.com/001"//
        )));
        documentSizeByQuery = oldDocList.size();
        assertEquals(0, indexingHelper.deleteOldDocuments(client, docList));

        DocList docList = new DocList();

        Map<String, Object> doc1 = new HashMap<>();
        doc1.put("id", "1");
        doc1.put("title", "Test Document 1");

        Map<String, Object> doc2 = new HashMap<>();
        doc2.put("id", "2");
        doc2.put("title", "Test Document 2");

        docList.add(doc1);
        docList.add(doc2);

        assertEquals(2, docList.size());

     * didn't see that discussed in the review, which included many other
     * changes: https://mail.openjdk.org/pipermail/core-libs-dev/2013-May/thread.html#17367
     *
     * TODO(cpovirk): decide what the best long-term action here is: force users
     * to suppress (as we do now), stop testing entrySet().add() at all, make
     * entrySet().add() tests tolerant of either behavior, introduce a map

                // Simulate storing documents
                Map<String, Object> doc1 = new HashMap<>();
                doc1.put("id", "1");
                doc1.put("title", "Document 1");
                callback.store(initParamMap, doc1);

                Map<String, Object> doc2 = new HashMap<>();
                doc2.put("id", "2");

                    return "expires";
                case FessConfig.INDEX_FIELD_URL:
                    return "url";
                case FessConfig.INDEX_FIELD_doc_id:
                    return "doc_id";
                case FessConfig.INDEX_FIELD_ID:
                    return "id";
                case FessConfig.INDEX_FIELD_VERSION:
                    return "_version";

      },
      "expires": {
        "type": "date",
        "format": "date_optional_time"
      },
      "digest": {
        "type": "text",
        "index": false
      },
      "doc_id": {
        "type": "keyword"
      },
      "favorite_count": {
        "type": "long"
      },
      "filename": {
        "type": "keyword"
      },
      "filetype": {