[
https://issues.apache.org/jira/browse/IGNITE-29205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18132202#comment-18132202
]
Ignite TC Bot commented on IGNITE-29205:
----------------------------------------
Concrete documentation proposal: in
docs/_docs/key-value-api/using-cache-queries.adoc, under Executing Index
Queries, state that IndexQuery returns deserialized cache values by default and
that callers can execute it through cache.withKeepBinary() to receive
BinaryObject values when possible. The related implementation is
https://github.com/apache/ignite/pull/13744.
Automation blocker: the local ignite checkout does not yet contain that merged
implementation and this runtime cannot fetch the public GitHub ref, so no
documentation branch or PR was prepared in this run.
> [doc] Clarify IndexQuery value deserialization
> ----------------------------------------------
>
> Key: IGNITE-29205
> URL: https://issues.apache.org/jira/browse/IGNITE-29205
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Ignite TC Bot
> Priority: Major
>
> Source issue: https://issues.apache.org/jira/browse/IGNITE-29199
> Document that local IndexQuery results follow the cache binary-mode contract:
> a query executed through a regular cache returns deserialized values, while
> cache.withKeepBinary() returns BinaryObject values when possible.
> Suggested minimal change: add this clarification to
> docs/_docs/key-value-api/using-cache-queries.adoc in the Executing Index
> Queries section, linking to the existing Binary Objects documentation.
> Implementation PR: https://github.com/apache/ignite/pull/13744
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
