You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2018/12/24 15:52:00 UTC
[jira] [Assigned] (SOLR-12888) NestedUpdateProcessor code should
activate automatically in 8.0
[ https://issues.apache.org/jira/browse/SOLR-12888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley reassigned SOLR-12888:
-----------------------------------
Assignee: David Smiley
> NestedUpdateProcessor code should activate automatically in 8.0
> ---------------------------------------------------------------
>
> Key: SOLR-12888
> URL: https://issues.apache.org/jira/browse/SOLR-12888
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Blocker
> Fix For: master (8.0)
>
>
> If the schema supports it, the NestedUpdateProcessor URP should be registered automatically somehow. The Factory for this already looks for the existence of certain special fields in the schema, so that's good. But the URP Factory needs to be added to your chain in any of the ways we support that. _In 8.0 the user shouldn't have to do anything to their solrconfig._
> We might un-URP this and call directly somewhere. Or perhaps we might add a special named URP chain (needn't document), defined automatically, that activates at RunURP. Perhaps other things could be added to this in the future.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org