Hello Alexandre, Please see below. On Tue, Sep 6, 2016 at 5:47 PM, Alexandre Rafalovitch <[email protected]> wrote:
> I opened SOLR-9477 a couple of days ago. Basically it seems that all > but one Update Request Processors do not look at the child documents. > > So, no "schemaless" mapping, no ID generation, no empty field removal, > no trim, etc. for child documents. All of these are only for the > top-level document. > > I would think somebody would have noticed it earlier, so feel that > maybe I am missing something. > > I would appreciate somebody else to test it quickly and confirm/set me > straight on this. > > But if it is true then > *) Do we need to document this as a limitation? > Yes. Sure. But it's nowhere promised that update processors are applied on children. > *) Do we need to fix it individually or there is a smart way to do it > centrally? Probably yes, but I prefer to aim someones real life challenge, than solve an abstract common sense problem. eg. how to apply a processor to children only but not to parent? Another case is ID generation - it's often required to generate it for parent but then implicitly propagate to children, but it requires paradigm shift: uniqueKey should be assigned on a block not a single document. This will fix when childless docs are mixed with blocks, etc. Perhaps, it make sense to create a processed which applies a certain chain of processors to children docs only? Frankly speaking, block support are yet raw, and this limitation is not considered significant at comparison with other ones. > One Jira or a bunch? > *) Are there any catches/complications around this area? > > Regards, > Alex. > > ---- > Newsletter and resources for Solr beginners and intermediates: > http://www.solr-start.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sincerely yours Mikhail Khludnev
