Thanks for the tips. I had read the HowTo but didn't know where the old
lucene code was hosted. It's come a long way since then. :)
Thanks,
David
On 4/26/2017 8:42 PM, Doug Turnbull wrote:
Something I found helpful was to go back to very early Lucene
versions. That let's you see the essential functionality in relatively
straightforward Java code. You can get a sense for how Lucene is
structured. Functionality has been built around this since. The Java
has been battle tested, refactored, and optimized. But those core bits
were really helpful for me to see what Lucene specifically did.
https://sourceforge.net/projects/lucene/
That plus Lucene in Action
On Wed, Apr 26, 2017 at 7:16 PM Erick Erickson
<[email protected] <mailto:[email protected]>> wrote:
Solr/Lucene is big. Really big. I'd think seriously about taking
something you're interested in/know about, finding a JIRA that you'd
like to work on and diving in. Plus there aren't very many
architecture docs.
Your characterization of the realms of responsibility is pretty
accurate.
Have you seen: https://wiki.apache.org/solr/HowToContribute?
A somewhat painful but "safe" way to get your feet wet is to look at
the coverage reports on jenkins and see what code is not tested in the
junit tests and...write a test. At least I think the coverage reports
are still there.
Best,
Erick
On Wed, Apr 26, 2017 at 3:12 PM, David Lee
<[email protected] <mailto:[email protected]>> wrote:
> I'd like to have a better understanding of how much of Solr is
unique to it
> versus directly extending Lucene.
>
> For example, I assume that sharding, replication, etc. is
implemented in
> Solr where-as indexing, querying, etc. would be implemented by
Lucene.
>
> I'm hoping to learn enough to be able to contribute at some point.
>
> Thanks,
>
> David
>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
> For additional commands, e-mail: [email protected]
<mailto:[email protected]>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
<mailto:[email protected]>
For additional commands, e-mail: [email protected]
<mailto:[email protected]>
