Closed luocooong closed 2 years ago
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 <<< ERROR!
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.
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 <<< ERROR! 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:
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.@cdmikechen Thanks for the questions.
/Agirish/drill-helm-charts
and create a branch to driven the Drill on K8S
, if anyone ready to contribute the feature. I recommend that you can discussion this topic on mailing list or Slack channel, Talk with @Agirish first.All great ideas have a path to success. We welcome contributions of any kind including pull requests, ideas, bug reports, testing, writing documentation, tutorials and blog posts.
@luocooong About the helm... I noticed that the 1.19 image was recently updated on docker hub. I’ve made some adaptations according to his helm and ran it in the test environment for a long time. I think I can try to submit a PR later, or even change it to an operator directly.
Guys, what do you think about extending information_schema.columns with the "comment" column? At this moment I need to search the database itself. This was discussed here https://apache-drill.slack.com/archives/CG380K519/p1636905663050200
@imamerkhanov Hello. Could you please create a new issue (with a detailed requirements)? So the developer will know that there are new good ideas.
It would be great to add support to additional cloud table storage such as azure table. Also, I think the JDBC used as example in the Drill documentation to connect to SQL Server is too old (v6) and maybe that's why it has this issue .
@alvaradojl thanks for the suggestions. The issue related to LIMIT is actually a bug which we'll tackle soon.
Is your feature request related to a problem? Please describe. Hello guys. Apache Drill is a community-driven project. We are welcome any of your contributions (in any way). Drill team had invested a lot of time in the support of community since 2020 Q4.
Describe the solution you'd like We are regularly discussing how to attract more developers to contribute. Such as adding more friendly guides on the website, marking tasks for
newcomers
at the JIRA, and update the documentation in time... There are many ways to take part in the Drill :Issues
on Github).Describe alternatives you've considered Before that, Drill does not enable the
Issues
on Github. However, we are happy to see that Drill community is more actively. YES, It's time to use a new simple way to talk with our users and developers. I recommend that you can create issues on the Github if you want to talk first, then create the JIRA on the apache issues. That, We can both keep the knowledge to the JIRA and quickly support the users and developers on the Github.Additional context