drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5485) Remove WebServer dependency on DrillClient
Date Tue, 23 May 2017 20:41:05 GMT

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

ASF GitHub Bot commented on DRILL-5485:

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

    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/rpc/UserClientConnection.java
    @@ -0,0 +1,69 @@
    + * 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.rpc;
    +import io.netty.channel.ChannelFuture;
    +import org.apache.drill.exec.physical.impl.materialize.QueryWritableBatch;
    +import org.apache.drill.exec.proto.GeneralRPCProtos;
    +import org.apache.drill.exec.proto.UserBitShared;
    +import org.apache.drill.exec.rpc.user.UserSession;
    +import java.net.SocketAddress;
    + * Interface for getting user session properties and interacting with user connection.
Separating this interface from
    + * {@link AbstractRemoteConnection} implementation for user connection:
    + * <p><ul>
    + * <li> Connection is passed to Foreman and Screen operators. Instead passing this
interface exposes few details.
    + * <li> Makes it easy to have wrappers around user connection which can be helpful
to tap the messages and data
    + * going to the actual client.
    + * </ul>
    + */
    +public interface UserClientConnection {
    +  /**
    +   * @return User session object.
    +   */
    +  UserSession getSession();
    +  /**
    +   * Send query result outcome to client. Outcome is returned through <code>listener</code>
    +   *
    +   * @param listener
    +   * @param result
    +   */
    +  void sendResult(RpcOutcomeListener<GeneralRPCProtos.Ack> listener, UserBitShared.QueryResult
    --- End diff --
    Add imports for inner classes, here and everywhere else.

> Remove WebServer dependency on DrillClient
> ------------------------------------------
>                 Key: DRILL-5485
>                 URL: https://issues.apache.org/jira/browse/DRILL-5485
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Web Server
>            Reporter: Sorabh Hamirwasia
>             Fix For: 1.11.0
> With encryption support using SASL, client's won't be able to authenticate using PLAIN
mechanism when encryption is enabled on the cluster. Today WebServer which is embedded inside
Drillbit creates a DrillClient instance for each WebClient session. And the WebUser is authenticated
as part of authentication between DrillClient instance and Drillbit using PLAIN mechanism.
But with encryption enabled this will fail since encryption doesn't support authentication
using PLAN mechanism, hence no WebClient can connect to a Drillbit. There are below issues
as well with this approach:
> 1) Since DrillClient is used per WebUser session this is expensive as it has heavyweight
RPC layer for DrillClient and all it's dependencies. 
> 2) If the Foreman for a WebUser is also selected to be a different node then there will
be extra hop of transferring data back to WebClient.
> To resolve all the above issue it would be better to authenticate the WebUser locally
using the Drillbit on which WebServer is running without creating DrillClient instance. We
can use the local PAMAuthenticator to authenticate the user. After authentication is successful
the local Drillbit can also serve as the Foreman for all the queries submitted by WebUser.
This can be achieved by submitting the query to the local Drillbit Foreman work queue. This
will also remove the requirement to encrypt the channel opened between WebServer (DrillClient)
and selected Drillbit since with this approach there won't be any physical channel opened
between them.

This message was sent by Atlassian JIRA

View raw message