Yep, was a problem with the maven artifact publishing.
Not an actual problem...
jayson.minard wrote:
>
> Does look like the publishing from Solr ANT went to wrong place and wasn't
> being picked up by Maven for the main build.
>
> Confirming but this is most likely a non-issue.
>
> --j
>
>
Does look like the publishing from Solr ANT went to wrong place and wasn't
being picked up by Maven for the main build.
Confirming but this is most likely a non-issue.
--j
jayson.minard wrote:
>
> clearing our maven repo and rebuilding to be sure.
>
>
> Yonik Seeley-2 wrote:
>>
>> On Thu,
clearing our maven repo and rebuilding to be sure.
Yonik Seeley-2 wrote:
>
> On Thu, May 14, 2009 at 2:01 PM, jayson.minard
> wrote:
>>
>> When using the Solr trunk tip, get this error now when reading an index
>> created by Solr with Lucene directly:
>>
>> java.lang.IndexOutOfBoundsException:
It is the reverse case, created with solr, optimized and then in the
post-optimize listener open snapshot with lucene.
Code used is this:
Directory directory = new FSDirectory(new File(luceneIndexDir), null);
reader = IndexReader.open(directory, true); // open directory read-only
...
reader
On Thu, May 14, 2009 at 2:16 PM, Yonik Seeley
wrote:
> Hmmm, OK... so you created the index with Lucene and are reading it with Solr.
> What version of Lucene did you use to create?
Oops, vise versa, right?
-Yonik
-
To unsubscr
This is with an optimized index since the code runs just after optimization.
jayson.minard wrote:
>
> When using the Solr trunk tip, get this error now when reading an index
> created by Solr with Lucene directly:
>
> java.lang.IndexOutOfBoundsException: Index: 24, Size: 0
> at java.util
On Thu, May 14, 2009 at 2:01 PM, jayson.minard wrote:
>
> When using the Solr trunk tip, get this error now when reading an index
> created by Solr with Lucene directly:
>
> java.lang.IndexOutOfBoundsException: Index: 24, Size: 0
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
>
