[Notice] welcome the ideas and contribution with next release 1.20.0

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 :

1. Create issues with your want (use the Issues on Github).
2. Create JIRA on the issues.apache.org.
3. Git fork & clone and contribute the PR. quick-start.
4. Learning the Drill :

• docs/usage and docs/dev.
• Learning Apache Drill Book [English].
• Learning Apache Drill Book [Chinese].
• Deep dive into Drill internals. Paul Rogers’ wiki.

1. Discussion using the Mailing Lists.
2. Talk anything on the Slack channel. (Extremely active !)
3. To Help with testing, feedback and resolve issues with the above ways.

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

1. Welcome to contact us If you want to show your use case.
2. Community Over Code. Hope to see you soon…

[cdmikechen]

@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.

[cdmikechen]

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.