It's probably easiest if you just browse through the JIRA tickets: https://jira.sakaiproject.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SPARSE
Because any storage solution must address both persistence and querying, I would also include the Solr-integration bugs: https://jira.sakaiproject.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SOLR In both cases, many of the bugs have been fixed since this adventure started in February 2011 while some still have not. The key point, however, is that every time we try to add a feature (or just look more closely at anomalies in our production environment), we've hit new bugs. Which shouldn't surprise anyone. No matter how skilled, a small development team cannot simultaneously deliver new application functionality on schedule and maintain an independently coded simulation of Apache Jackrabbit. Best, Ray On 5/31/12 1:38 AM, Daniel Parry wrote: > Hi, > > I notice from the recent OAE Architectural Meeting Summary that Sparse Map > Content has been a source of data integrity issues. Could someone furnish me > with a list of these issues please so we can address them in all our > instances, > if it is indeed still necessary to do so, before we have the embarrassment of > telling our users that we have lost their data? Or, have all the data > integrity > issues already been addressed in a particular version? > > Thanks and best wishes, > > Daniel > _______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
