: the thing though: We had one field defined using this fieldtype and we : deployed the new schema to solr when we started seeing the issue. However, : we had not yet released our code that was using the new field (obviously we : have to make the change on the solr end before the code, so we : asynchronously do this offset by a few days). So the field that was of that : fieldtype wasn't even being queried against.
but even then: having the Factorty declared as part of a fieldtype means the factory is going to get instantiated -- so without nay information about what the factory does in it's init/inform methods, there's really no way to guess what might be causing hte behavior you are seeing. : The problem for us would be pretty easy to reproduce, but I don't think our : sys admins would appreciate experimenting with our production solr servers. I completley understand that, but at this point i can't reproduce what you're seeing, and i haven't seen anyone else sy that they can reproduce it either -- the simplest explanation being that it's probably not a bug in Solr, but it might be a bug in your code. I don't know how else to say this but: if you don't show us some code that other people can use to try and reproduce, we can't really help you. -Hoss
