welcome, I'm glad you want to help with Hibernate Search!
But I'm afraid we don't maintain diagrams of the internal architecture. I
would suggest to start getting familiar with it by using it, and trying to
figure out how it works by debugging, writing tests or exploring the source
code. Using it in a project you work on is usually very effective as well.
The code base is quite large so I would not suggest to try reading it all.
A good approach could be to try fixing a simple issue - you can find many
open tasks on our JIRA - by writing a unit test first and then trying to
figure out how to create a fix for it.
This is a list of open JIRA issues which we *think* might be a good
starting point for developers new to the project:
When you think you have a great patch to share send a pull request (make
sure to include tests, javadoc and documentation changes if any are
Some other person will eventually volunteer to review your changes, and
possibly suggest improvements or give you other advice based on their
longer experience with the project. It's possible your pull request will
require improvements or not be merged, but there's nothing to be ashamed of
we all learn that way.
On 1 March 2017 at 12:39, vaibhav kulkarni <vcharmcaster(a)gmail.com> wrote:
Vaibhav Khamgavkar( VK ) is newbies name, Hibernate Search grabbed my
Will like to contribute to this project. can you send me high level
design/ architecture diagram?
in case you are not right person to contact let me know whom should i
Note: This e-mail message and attachments may contain confidential
information. If you have received this message in error, please immediately
notify the sender and delete this e-mail message.