{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-17T22:44:07.049Z",
  "record_id": "VXI-EXT-PROCUREMENT-ELASTIC-DELETE-QUERY-RESIDUE-01-v1",
  "record_kind": "external_reference",
  "title": "Elasticsearch: Failed deletion with retained effects",
  "system": "Elasticsearch",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a failed Elasticsearch delete-by-query leave the original matching documents intact?",
  "near_questions": [
    "Are successful delete-by-query deletions rolled back on failure?",
    "What remains after an Elasticsearch version conflict?",
    "Which snapshot did delete-by-query use?",
    "Does conflicts=proceed restore atomic deletion?",
    "Can a failed query still delete some documents?",
    "Were concurrent document changes preserved?",
    "Which delete-by-query failures need reconciliation?",
    "Does the task failure label mean zero effects?",
    "How should remaining matching documents be reviewed?",
    "What evidence limits a destructive Elasticsearch retry?",
    "Was the approved query scope changed during recovery?",
    "Can INDEX verify deleted Elasticsearch documents?"
  ],
  "supported_claims": [
    {
      "claim": "Elasticsearch 8.19 delete-by-query works from an initial snapshot using internal versioning. Concurrent changes can cause version conflicts. If processing stops after failed requests, successful earlier deletions remain; they are not rolled back. Setting conflicts to proceed changes conflict handling, not the need to reconcile remaining documents and completed deletions.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Atomic bulk deletion, automatic restoration or approval for a broader retry",
    "Verified buyer configuration, effective access or actual event completeness",
    "Runtime enforcement, certification or approval to act"
  ],
  "public_summary": "Elasticsearch 8.19 delete-by-query works from an initial snapshot using internal versioning. Concurrent changes can cause version conflicts. If processing stops after failed requests, successful earlier deletions remain; they are not rolled back. Setting conflicts to proceed changes conflict handling, not the need to reconcile remaining documents and completed deletions.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Elasticsearch: Delete by query",
    "source_url": "https://www.elastic.co/guide/en/elasticsearch/reference/8.19/docs-delete-by-query.html",
    "checked_on": "2026-10-17",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-ELASTIC-DELETE-QUERY-RESIDUE-01-v1",
    "candidate_record_sha256": "894452c6da97b7b2aba27d7f20485b43463c036dd05ddb979f70c2afaf0c5fe3",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Elasticsearch 8.19 delete-by-query works from an initial snapshot using internal versioning. Concurrent changes can cause version conflicts. If processing stops after failed requests, successful earlier deletions remain; they are not rolled back. Setting conflicts to proceed changes conflict handling, not the need to reconcile remaining documents and completed deletions.",
    "required_buyer_context": "Exact query, index scope and conflict options submitted. Task response, deletion counts, conflicts and failed items. Remaining document versions and any approved restoration or further deletion plan. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-17",
    "claim_to_check": "Does a failed Elasticsearch delete-by-query leave the original matching documents intact?",
    "documented_statement": {
      "status": "documented",
      "statement": "Elasticsearch 8.19 delete-by-query works from an initial snapshot using internal versioning. Concurrent changes can cause version conflicts. If processing stops after failed requests, successful earlier deletions remain; they are not rolled back. Setting conflicts to proceed changes conflict handling, not the need to reconcile remaining documents and completed deletions.",
      "source_ids": [
        "elastic-delete"
      ]
    },
    "buyer_evidence_required": [
      "Exact query, index scope and conflict options submitted.",
      "Task response, deletion counts, conflicts and failed items.",
      "Remaining document versions and any approved restoration or further deletion plan."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Decline no-effect or fully-deleted claims until successful deletions and residual matches are separately accounted for."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "elastic-delete",
        "url": "https://www.elastic.co/guide/en/elasticsearch/reference/8.19/docs-delete-by-query.html",
        "final_url": "https://www.elastic.co/guide/en/elasticsearch/reference/8.19/docs-delete-by-query.html",
        "title": "Elasticsearch: Delete by query",
        "checked_on": "2026-10-17",
        "captured_at_utc": "2026-10-17T22:37:23.155Z",
        "version_context": "Elasticsearch 8.19 versioned reference; not asserted for all versions",
        "sha256": "ed244cabecb61edbfd3cc36570aad518a00e4e494716e9500f0b8927afe27baf",
        "bytes": 71150,
        "hash_basis": "Decoded HTTP response body bytes; not a signature or truth guarantee",
        "reviewed_sections": [
          "Description; Version conflicts and failed requests"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "A failed destructive bulk action can leave a mixed state that neither a total-failure label nor a blanket retry explains.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Exact query, index scope and conflict options submitted. Task response, deletion counts, conflicts and failed items. Remaining document versions and any approved restoration or further deletion plan."
    },
    "buyer_relevance": "A failed destructive bulk action can leave a mixed state that neither a total-failure label nor a blanket retry explains.",
    "refusal_conditions": [
      "Decline no-effect or fully-deleted claims until successful deletions and residual matches are separately accounted for."
    ]
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#elasticsearch-delete-by-query-partial-residual-state",
  "machine_readable_record": "/varexis-index/records/elasticsearch-delete-by-query-partial-residual-state.json"
}
