[
https://issues.apache.org/jira/browse/SOLR-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598308#action_12598308
]
Jason Rutherglen commented on SOLR-564:
---------------------------------------
After review, function queries ValueSource should be fine because the values
are not loaded from the field cache until the query is executed in the
sub-searcher. Sort is not mentioned because it is handled in the sub-searcher.
LUCENE-831 is a good step, however, if used for the top level reader in a
realtime system, large arrays will constantly be created for the top level
reader after every transaction. This is why the work, meaning the query and
the results, should be performed in the sub-searcher and then merged.
SimpleFacets.getFieldCacheCounts should be placed in the SolrIndexSearcher in
order for it to be operable which will be placed in SOLR-567.
The Ocean Solr code patch will be attached to this issue.
> Realtime search in Solr
> -----------------------
>
> Key: SOLR-564
> URL: https://issues.apache.org/jira/browse/SOLR-564
> Project: Solr
> Issue Type: New Feature
> Components: replication, search
> Affects Versions: 1.3
> Reporter: Jason Rutherglen
>
> Before when I looked at this, the changes required to make Solr realtime
> would seem to break the rest of Solr. Is this still the case? In project
> Ocean http://code.google.com/p/oceansearch/ there is a realtime core however
> integrating into Solr has looked like a redesign of the guts of Solr.
> - Support for replication per update to transaction log
> - Custom realtime index creation
> - Filter and facet merging
> - Custom IndexSearcher that ties into realtime subsystem
> - Custom SolrCore that ties into realtime subsystem
> Is there a way to plug into these low level Solr functions without a massive
> redesign? A key area of concern is the doclist caching which is not used in
> realtime search because after every update the doclists are no longer valid.
> The doclist caching and handling is default in SolrCore. Ocean relies on a
> custom threaded MultiSearcher rather than a single IndexSearcher is a
> difficulty. DirectUpdateHandler2 works directly on IndexWriter is
> problematic.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
