On Fri, Mar 27, 2015 at 12:27 AM, Mike Hansen wrote:
> There are a few things which could probably help with performance.
> Each document has only around say 30 polygons. You could do a binary
> search which would help reduce the cost. Additionally, I have a
> distinguished point contained inside
+1 for starting with unit tests - they show you how things work, give you
something to step through in the debugger, are (or should be!) always
current, and are a great place to start for contributing code, like
improving coverage and optimizing coverage. Commenting code and enhancing
the Javadoc i
Hi all,
Thanks a lot for your suggestions!
I believe the current lucene code repository is
https://github.com/apache/lucene-solr/tree/trunk/lucene
On Sat, Mar 28, 2015 at 5:49 AM, Jack Krupansky
wrote:
> +1 for starting with unit tests - they show you how things work, give you
> something to st
