Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:
1. Query Cancel TCK tests
With the latest tests it seems that the big job in query is during
ResultSet.next() instead of Statement.execute(). Next try to write
lock some instances and see if that affects the behavior.
2. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) https://issues.apache.org/jira/browse/JDO-557
Making progress; a bit of reorganization and testing is still needed.
3. Metadata tests Andy says that the latest snapshots of DataNucleus
contain a fix for the getParent() returning nothing. AI Craig test
with the SNAPSHOT version.
4. Spec updates No changes since last week.
5. Other issues
NoSQL might be a good way to improve JDO's visibility.
https://issues.apache.org/jira/browse/JDO-651
JDO was designed to support non-SQL datastores. In fact, the first RI
was a distinctly non-SQL implementation, essentially a key-value
store. What needs to be done for NoSQL in general is to go through the
specification in detail and highlight those parts that cannot now be
implemented reasonably by a key-value store, or a non-transactional
datastore. NoSQL is probably too big a description of the kinds of
datastores that makes sense for JDO to support. Part of the exercise
should be to categorize the NoSQL datastores to focus on those
categories that make sense for JDO.
Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!
