[
https://issues.apache.org/jira/browse/IGNITE-22582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860139#comment-17860139
]
Pavel Tupitsyn commented on IGNITE-22582:
-----------------------------------------
Merged to main:
https://github.com/apache/ignite-3/commit/da7a116d8ce93277f7218364b9b2413f29158dd2
> Improve javadoc for KeyValueView#getAllAsync regarding not existing keys
> ------------------------------------------------------------------------
>
> Key: IGNITE-22582
> URL: https://issues.apache.org/jira/browse/IGNITE-22582
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 3.0.0-beta1
> Reporter: Tiago Marques Godinho
> Assignee: Tiago Marques Godinho
> Priority: Major
> Labels: ignite-3
>
> The [current javadoc|
> https://github.com/apache/ignite-3/blob/38d13fcd5f0b45879f210bcc15b1e048b8916fa4/modules/api/src/main/java/org/apache/ignite/table/KeyValueView.java#L129-L137]
> for the `getAll` methods in the KeyValueView does not specify what happens
> if the requested keys are not found.
> The user might expect the following behaviours:
> * Method fails because cannot find all the keys
> * The returned map contains all the keys but non-existing keys are mapped to
> a null value.
> * The returned map does not contain non-existing keys.
> What to do:
> * Clarify the actual scenario in the javadoc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
