cpoerschke commented on PR #2382: URL: https://github.com/apache/solr/pull/2382#issuecomment-2077786562
So I was trying to learn how the main configuration bits fit together here and high-level the reverse search idea and my _solr-monitor-naive-dinner-demo_ branch (or #link-to-follow diff) off this pull request's branch is a side effect of that and my understanding so far based on it is that: * the in-memory state is in the `Presearcher` object in the `ReverseQueryParserPlugin` class object (and in the _solr-monitor-naive-dinner-demo_ i just used a simple `Monitor` object instead of the `Presearcher` object) * the state is updated via the `MonitorUpdateRequestProcessor` i.e. saved searches are added as `MonitorQuery` objects to the `Monitor` object (and updating of the `Presearcher` object is a bit different) * the state is accessed via the `ReverseSearchComponent` component (currently non-distributed but conceptually distributed would work too?) Is that basic understanding correct? As a next step I might go learn more about the `Presearcher` itself. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
