March 2018 Update
I originally posted this content to LinkedIn here in May 2016. Cross posting to my blog with minor edits on the ~2 year anniversary of the announcement of me becoming an Apache Lucene/Solr committer.
Overview
My previous post in my Apache Solr JDBC blog series showed how to connect JDBC tools like Apache Zeppelin to Apache Solr. This post describes how you can get involved with Apache Solr and the JDBC driver. This post was inspired by the great Lucidworks blog post by Hoss about the 14 ways to contribute to Apache Solr.
Improving the Documentation
The Apache Solr Reference Guide contains information about how to use Parallel SQL and the JDBC driver to connect to Apache Solr. Documentation can always be improved to reduce the amount of time to get started. If there is anything that should be improved in the reference guide, leave a comment on the specific page and it will be reviewed.
In addition to the reference guide, here are some references that can be used to get started with Parallel SQL and the JDBC driver:
- Apache Solr JDBC - Introduction - Kevin Risden
- Apache Solr JDBC - Java - Sematext
- Apache Solr JDBC - JDBC Tools - Kevin Risden
Asking Questions & Reporting Bugs/Improvements
If you have questions or would like to report any bugs you run across, the Apache Solr has a section on Community and how to use the solr-user mailing list. The solr-user mailing list is monitored by committers and users so you can get an answer quickly. Providing details and searching before asking can improve your experience with the mailing list. Once a bug or improvement has been vetted, it is typically entered into the Apache JIRA.
Helping with Development
In addition to documentation, contributing back code and patches to Apache Solr can be a way to give back. Apache Solr has a How to Contribute guide that outlines where to get started. Apache Solr is written in Java and is open source. The development tasks are stored on Apache JIRA and allow developers to see what needs to be improved. Looking through JIRA and finding an issue that you are interested in is a great way to get started. The next step is to ensure the issue is reproducible or provide a patch with tests that solves the problem. A committer can then review the patch and commit it. The Apache Solr Community page has information about the solr-dev list which is used specifically for contributors to the Apache Solr code base.
A few of the relevant Apache Solr JIRAs for Parallel SQL and JDBC are:
- SOLR-8125 - Umbrella ticket for Streaming & SQL issues
- SOLR-8659 - Improve JDBC driver for more SQL clients
- SOLR-8593 - Apache Calcite optimizer
Conclusion
I’ve given a peek into how I became an Apache Solr committer, an introduction to the Apache Solr JDBC driver, and some step-by-step guides on how to use the Apache Solr JDBC driver. If you are interested definitely feel free to get involved by follwing some of this tips described above.
Top comments (0)