lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mosh (JIRA)" <>
Subject [jira] [Commented] (SOLR-12685) RTG should return the whole block if schema is nested
Date Tue, 04 Sep 2018 07:45:00 GMT


mosh commented on SOLR-12685:

{quote}A ticket for the RTG handler(RealTimeGetComponent#process).
I was thinking about this one, it has been a tough one alright!
 Wouldn't this result in a major difference from an API perspective between the search component
and the RTG component?
 When querying a document by id, unless ChildDocTransformer is specified in the fl, only the
matching document is returned.
 The same applies to the RTG handler. When a request is made where ChildDocTranformer is supplied,
the whole block is returned.
 This makes sense to me,
 unless there is a specific need for the "/get" handler to possess the ability of returning
the whole block if exists,
 I can not foresee any reason for this change.
 Unless, of course, there is a concrete requirement for this logic in the replication process.

> RTG should return the whole block if schema is nested
> -----------------------------------------------------
>                 Key: SOLR-12685
>                 URL:
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: mosh
>            Priority: Major
>         Attachments: SOLR-12638-no-commit.patch
> Currently Solr's RealTimeGet component return the document if provided a docId when consulting
the index. For AtomicUpdates for child documents, RTG should return the whole block when dealing
with a nested schema.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message