[ https://issues.apache.org/jira/browse/SOLR-9309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-9309: --------------------------- Attachment: SOLR-9309.patch Suggested fix: * refactors duplicated "param parsing" & "add doc/list to response" logic into helper methods ** this refactoring keeps the "single node" logic on the doc vs list choice, resolving the current inconsistencies * enables some (previously commented out) logic in TestRandomFlRTGCloud to assert that we get a list when we expect a list -- even if some/all of the ids requested don't exist. > SolrCloud RTG with multiple "id" params has inconsistent behavior if only 0 > or 1 ids are returned > ------------------------------------------------------------------------------------------------- > > Key: SOLR-9309 > URL: https://issues.apache.org/jira/browse/SOLR-9309 > Project: Solr > Issue Type: Bug > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Hoss Man > Attachments: SOLR-9309.patch > > > * RTG uses a diff reqponse format depending on whether a single id is > requested or multiple ids are requested. > * there are 2 ways to request multiple ids: > *# multiple {{id}} params > *# comma seperated ids in one (or more) {{ids}} param(s) > But in cloud mode, asking for multiple ids using the first method can > incorrectly return the "single" doc response structure if 0 or 1 docs are > returned (ie: because the other doc(s) don't exist in the index or were > deleted). > This inconsistency does not seem to exist in single node solr RTG > (Example to follow in comment) -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org