We have been running a build from July 26th, last commit a10ea4081e864392cd280044b07c05d7f3273e99, and today Oct 25th tried to update to the current build, last commit 462c13ae27c8cc932c19dc870555f0eb86625155, and are having a strange issue.
While running unit tests against the cluster we insert a bunch of data, query against it, then delete it. Insert more data, repeat... With the latest build when we delete all the id's the schema gets deleted as well, we get "invalid core" errors when trying to insert the next batch of data. This did not happen in the older build. Did something change in Solr which is causing this? Or is it a Solandra issue?
Example log entry for the delete is:
INFO [1893413681@qtp-432440941-0] 2011-10-25 15:52:34,160 LogUpdateProcessorFactory.java (line 171) {deleteByQuery=indexkey:testindex.*,commit=}
There doesn't seem to be a difference in the log entries for the deletes, just that after the delete the schema info is gone in the new version.
We have been running a build from July 26th, last commit a10ea4081e864392cd280044b07c05d7f3273e99, and today Oct 25th tried to update to the current build, last commit 462c13ae27c8cc932c19dc870555f0eb86625155, and are having a strange issue. While running unit tests against the cluster we insert a bunch of data, query against it, then delete it. Insert more data, repeat... With the latest build when we delete all the id's the schema gets deleted as well, we get "invalid core" errors when trying to insert the next batch of data. This did not happen in the older build. Did something change in Solr which is causing this? Or is it a Solandra issue? Example log entry for the delete is: INFO [1893413681@qtp-432440941-0] 2011-10-25 15:52:34,160 LogUpdateProcessorFactory.java (line 171) {deleteByQuery=indexkey:testindex.*,commit=} There doesn't seem to be a difference in the log entries for the deletes, just that after the delete the schema info is gone in the new version.