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-5910) ClassNotFoundException message enhancement
Date Sat, 28 Oct 2017 16:49:00 GMT

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

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

Github user vrozov commented on the issue:

    https://github.com/apache/drill/pull/1013
  
    @arina-ielchiieva I guess just logging an exception does not help unless it targets Java
developers. Consider logging a message that has information regarding which authentication
provider can't be instantiated/initialized and continue.


> ClassNotFoundException message enhancement 
> -------------------------------------------
>
>                 Key: DRILL-5910
>                 URL: https://issues.apache.org/jira/browse/DRILL-5910
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.11.0
>            Reporter: Volodymyr Tkach
>            Assignee: Volodymyr Tkach
>            Priority: Minor
>              Labels: ready-to-commit
>             Fix For: 1.12.0
>
>
> We need to add factory name in exception message  when ClassNotFoundException is caught
and DrillRuntimeException is than re-thrown in ClientAuthenticatorProvider constructor.
> Steps to repoduce:
> 1) Configure plain authentication
> 2) Add 
> -Ddrill.customAuthFactories=org.apache.drill.exec.rpc.security.maprsasl.MapRSaslFactory
to SQLLINE_JAVA_OPTS or another class that is not present in classpath.
> 3) Run sqlline and connect to drillbit



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message