Github user dsmiley commented on a diff in the pull request:

    https://github.com/apache/lucene-solr/pull/410#discussion_r197868389
  
    --- Diff: 
solr/core/src/java/org/apache/solr/update/processor/DeeplyNestedUpdateProcessor.java
 ---
    @@ -0,0 +1,101 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *     http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +
    +package org.apache.solr.update.processor;
    +
    +import java.io.IOException;
    +import java.util.Collection;
    +import java.util.EnumSet;
    +import java.util.Locale;
    +import java.util.Objects;
    +
    +import org.apache.solr.common.SolrInputDocument;
    +import org.apache.solr.common.SolrInputField;
    +import org.apache.solr.request.SolrQueryRequest;
    +import org.apache.solr.response.SolrQueryResponse;
    +import org.apache.solr.schema.IndexSchema;
    +import org.apache.solr.update.AddUpdateCommand;
    +import static 
org.apache.solr.update.processor.DeeplyNestedUpdateProcessorFactory.NestedFlag;
    +
    +public class DeeplyNestedUpdateProcessor extends UpdateRequestProcessor {
    --- End diff --
    
    I wonder if we want to call this as-such.  Can this be used if the nesting 
is "shallow"?  Perhaps remove the "Deeply" part.  Perhaps this URP should 
handle "_root_" as well to thus unify where nested child doc fields are added?  
Although that raises other questions.  With 8.0 on the horizon this fall, we 
can think of the best solution that isn't necessarily fully backwards 
compatible.  This conversation should probably be taken to the JIRA as it's a 
bigger question and not a code detail.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to