drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [drill] cdmikechen edited a comment on issue #2233: [Notice] welcome the ideas and contribution with next release 1.20.0
Date Tue, 01 Jun 2021 00:35:45 GMT

cdmikechen edited a comment on issue #2233:
URL: https://github.com/apache/drill/issues/2233#issuecomment-851122085

   > Wish to add more guides. Now I run test like `mvn test -pl contrib/storage-hive/core`,
but it looks like run failed.
   > ```
   > Hive Session ID = efd0bb19-db4a-4143-8dd8-f59f79de6e10
   > [INFO] Running org.apache.drill.exec.fn.hive.TestHiveUDFs
   > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.09 s <<<
FAILURE! - in org.apache.drill.exec.fn.hive.TestHiveUDFs
   > [ERROR] org.apache.drill.exec.fn.hive.TestHiveUDFs  Time elapsed: 0.014 s  <<<
   > org.apache.drill.exec.rpc.RpcException: CONNECTION : io.netty.channel.ConnectTimeoutException:
connection timed out: xxx.local/ip:31010
   > Caused by: java.util.concurrent.ExecutionException: io.netty.channel.ConnectTimeoutException:
connection timed out: xxx.local/ip:31010
   > Caused by: io.netty.channel.ConnectTimeoutException: connection timed out: xxx.local/ip:31010
   > ```
   > I don't know why failed and how to fix it, and can not find some more useful document
to help me debug.
   Oh It's my fault, I set my computer host to another ip in `/etc/hots`, so that drill can
not find my ip. 
   I have been used drill since 1.16. At present, I have encountered some problems and some
ideas in use:
   1. How to better deploy on k8s. We use drill in a k8s cluster base on a helm using https://github.com/Agirish/drill-helm-charts.
Can we merge this project directly into drill or create an operator to deploy drill? According
to this helm, I also made some configuration and content modification and adaptation in the
actual operation (like add `daemonsets` mode).
   Meanwhile this leads to another problem, how to use environment variables to modify the
configuration more conveniently. And how to adjust the level of related logs more conveniently,
so that users can use docker to start the container more directly.
   2. Is it possible for drill to support Apache Atlas or Apache Ranger? Users maybe will
make better use of drill for data processing and analysis by using Ranger to do unified management
of data permissions or using Atlas to obtain metadata.
   3. Have we some examples or documents about using drill to query alluxio or ozone? Now
I only use drill to query data in HDFS, and I don't know much about other file systems.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message