[
https://issues.apache.org/jira/browse/CAMEL-24542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18112653#comment-18112653
]
Andrea Cosentino commented on CAMEL-24542:
------------------------------------------
Fixed via https://github.com/apache/camel/pull/26192 (merged to main as
cb1ed2b20e1fddb9dbb4aedc283ce70265e8a2bf).
The header is now wired into both RETRIEVE and SIMILARITY_SEARCH rather than
removed: it maps onto a real Qdrant capability
(WithPayloadSelectorFactory.include / exclude) that the component otherwise
cannot reach, and the change is backwards compatible since the INCLUDE_PAYLOAD
boolean remains the fallback.
Covered by QdrantPayloadSelectorIT against a real Qdrant container.
_Claude Code on behalf of oscerd_
> camel-qdrant: the PayloadSelector header is declared and advertised but never
> read
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-24542
> URL: https://issues.apache.org/jira/browse/CAMEL-24542
> Project: Camel
> Issue Type: Bug
> Components: camel-qdrant
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.23.0
>
>
> QdrantHeaders (line 31) declares PAYLOAD_SELECTOR =
> "CamelQdrantPointsPayloadSelector" and it is advertised in the generated
> qdrant.json (line 40), but it is never read anywhere in the component. The
> retrieve and similaritySearch operations only honour the INCLUDE_PAYLOAD
> boolean, so a user who sets PayloadSelector to request specific payload
> fields gets it silently ignored. Fix: either wire the header into the
> retrieve/similaritySearch requests (build a Qdrant WithPayloadSelector from
> it) or remove the dead constant.
> _Claude Code on behalf of oscerd_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
