[jira] [Commented] (SOLR-9377) [subquery] augmenter doesn't work with RTG on uncommited docs

["mosh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-9377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706096#comment-16706096 ] 

mosh commented on SOLR-9377:
----------------------------

{quote}Perhaps that's ok? Perhaps the only thing that's really important is that values from the doc used when building the subquery are accurate, and come from the tlog, and the query itself can (or perhaps MUST?) still be run against the same currently open searcher as if the user ran that subquery themselves?
{quote}
Are there any performance implications in case sub-queries are executed using real time searchers?
 Perhaps there could be a flag sent as a parameter for this use case?
 Nonetheless,
 I found it really hard to come by.
 Perhaps this should be included in the ref guide([transforming-result-documents|https://lucene.apache.org/solr/guide/7_5/transforming-result-documents.html#subquery])?

> [subquery] augmenter doesn't work with RTG on uncommited docs
> -------------------------------------------------------------
>
>                 Key: SOLR-9377
>                 URL: https://issues.apache.org/jira/browse/SOLR-9377
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>            Priority: Major
>             Fix For: 6.2, 7.0
>
>         Attachments: SOLR-9377.patch
>
>
> Spinning off from SOLR-9314...
> The {{[subquery]}} DocTransformer can give unexpected results when used with RTG on uncommitted docs.
> Test code demonstrating the problem is being added to TestRandomFlRTGCloud as part of SOLR-9314, but it's being disabled for now due to this current bug.  As noted in that jira...
> {quote}
> The subquery validation tries to search for all docs with teh same field value as the current doc, asserting that there is always at least 1 match – but this assertion currently fails ... by the looks of it this is (obviously) because it doesn't know to to use the realtime seracher re-opened by the RTG ... but based on how the SubQueryAugmenter is implemented, i'm not even certain how to go about it.
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org