[
https://issues.apache.org/jira/browse/SOLR-13034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17291239#comment-17291239
]
ASF subversion and git services commented on SOLR-13034:
--------------------------------------------------------
Commit 112e398d97d77f89bd2d114e569572d77536c290 in lucene-solr's branch
refs/heads/branch_8x from David Smiley
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=112e398 ]
SOLR-13034: RTG sometimes didn't materialize LazyField (#2408)
Partial (AKA Atomic) updates could encounter "LazyField" instances in the
document
cache and not know hot to deal with them when writing the updated doc to the
update log.
(cherry picked from commit 62971c4f990437e3ba4a5f4a2e980a058c2c01f1)
> RealTimeGetComponent#toSolrInputDocument should materialize LazyFields
> ----------------------------------------------------------------------
>
> Key: SOLR-13034
> URL: https://issues.apache.org/jira/browse/SOLR-13034
> Project: Solr
> Issue Type: Bug
> Reporter: mosh
> Assignee: David Smiley
> Priority: Major
> Labels: RealTimeGet
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Edited for toSolrInputDocument instead of toSolrDoc...
> ----
> As I was working on SOLR-12638, I noticed RealTimgeGetComponent#toSolrDoc
> does not resolve lazy fields.
> This behavior is cause by the use of transformers which use
> SolrDocumentFetcher, which caused exceptions to be thrown when said input
> documents were written to the transaction log(TransactionLog:100).
> IMO, These fields ought to be resolved by the
> RealTimgeGetComponent#toSolrDoc method, which takes a Document as an
> input(which may contain LazyFields) and returns a SolrInputDocument
> representation of said SolrDocument.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
