[ 
https://issues.apache.org/jira/browse/DRILL-4132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227252#comment-15227252
 ] 

ASF GitHub Bot commented on DRILL-4132:
---------------------------------------

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

    https://github.com/apache/drill/pull/368#discussion_r58623695
  
    --- Diff: 
exec/java-exec/src/main/java/org/apache/drill/exec/planner/fragment/ExchangeManipulatorMaterializerVisitor.java
 ---
    @@ -0,0 +1,97 @@
    +/**
    + * 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.drill.exec.planner.fragment;
    +
    +import java.util.List;
    +
    +import org.apache.drill.common.exceptions.ExecutionSetupException;
    +import org.apache.drill.exec.exception.FragmentSetupException;
    +import org.apache.drill.exec.physical.PhysicalOperatorSetupException;
    +import org.apache.drill.exec.physical.base.AbstractPhysicalVisitor;
    +import org.apache.drill.exec.physical.base.Exchange;
    +import org.apache.drill.exec.physical.base.GroupScan;
    +import org.apache.drill.exec.physical.base.PhysicalOperator;
    +import org.apache.drill.exec.physical.base.Store;
    +import org.apache.drill.exec.physical.base.SubScan;
    +import 
org.apache.drill.exec.planner.fragment.Materializer.IndexedFragmentNode;
    +
    +import com.google.common.collect.Lists;
    +
    +/**
    + * Materializer visitor to remove exchange(s)
    + */
    +public class ExchangeManipulatorMaterializerVisitor extends 
AbstractPhysicalVisitor<PhysicalOperator, Materializer.IndexedFragmentNode, 
ExecutionSetupException> {
    +
    +  static final org.slf4j.Logger logger = 
org.slf4j.LoggerFactory.getLogger(ExchangeManipulatorMaterializerVisitor.class);
    +
    +  public static final ExchangeManipulatorMaterializerVisitor INSTANCE = 
new ExchangeManipulatorMaterializerVisitor();
    +
    +  private ExchangeManipulatorMaterializerVisitor() {
    +
    +  }
    +
    +  @Override
    +  public PhysicalOperator visitExchange(Exchange exchange, 
IndexedFragmentNode iNode) throws ExecutionSetupException {
    +    iNode.addAllocation(exchange);
    +    PhysicalOperator childEx = exchange.getChild().accept(this, iNode);
    +    childEx.setOperatorId(Short.MAX_VALUE & exchange.getOperatorId());
    --- End diff --
    
    yes, I can probably skip setting id here


> Ability to submit simple type of physical plan directly to EndPoint DrillBit 
> for execution
> ------------------------------------------------------------------------------------------
>
>                 Key: DRILL-4132
>                 URL: https://issues.apache.org/jira/browse/DRILL-4132
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Execution - Flow, Execution - RPC, Query Planning & 
> Optimization
>            Reporter: Yuliya Feldman
>            Assignee: Yuliya Feldman
>
> Today Drill Query execution is optimistic and stateful (at least due to data 
> exchanges) - if any of the stages of query execution fails whole query fails. 
> If query is just simple scan, filter push down and project where no data 
> exchange happens between DrillBits there is no need to fail whole query when 
> one DrillBit fails, as minor fragments running on that DrillBit can be rerun 
> on the other DrillBit. There are probably multiple ways to achieve this. This 
> JIRA is to open discussion on: 
> 1. agreement that we need to support above use case 
> 2. means of achieving it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to