Well, in that case i'd open a ticket for this one. The problem is, for now,
that i can only replicate the behaviour using the spatial plugin.
On Wednesday 08 December 2010 21:58:06 Chris Hostetter wrote:
> : That's fine - it could be a Solr bug too.
>
> it definitely looks like a generic solr b
: That's fine - it could be a Solr bug too.
it definitely looks like a generic solr bug.
JSONResponseWriter.java:398
(in the writeSolrDocument method that supports psuedo-fields)
writeMapOpener(-1); // no trivial way to determine map size
PHPSerializedResponseWriter.java:221
(in which PHP
On Wed, Dec 8, 2010 at 9:45 AM, Markus Jelsma
wrote:
> I know, but since it's an Apache component throwing the exception, i'd figure
> someone just might know more about this.
That's fine - it could be a Solr bug too.
IMO, solr-user traffic just needs to be solr related and hopefully
useful to ot
I know, but since it's an Apache component throwing the exception, i'd figure
someone just might know more about this. An, the guys do visit the list afaik.
Anyway, i'd ask there too. Thanks
On Wednesday 08 December 2010 15:41:21 Grant Ingersoll wrote:
> That sounds like a JTeam plugin problem,
That sounds like a JTeam plugin problem, which is not supported here.
On Dec 8, 2010, at 5:38 AM, Markus Jelsma wrote:
> Hi,
>
> Got another issue here. This time it's the PHP serialized response writer
> throwing the following exception only when spatial parameters are set using
> LocalParam
Hi,
Got another issue here. This time it's the PHP serialized response writer
throwing the following exception only when spatial parameters are set using
LocalParams in Solr 1.4.1 using JTeam's plugin:
Map size must not be negative
java.lang.IllegalArgumentException: Map size must not be negat
