[cweb-CVS] bigdata-rdf/src/java/com/bigdata/rdf TripleStore.java, 1.29, 1.30

[Bryan T. <tho...@us...>]

Update of /cvsroot/cweb/bigdata-rdf/src/java/com/bigdata/rdf
In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv6871/src/java/com/bigdata/rdf

Modified Files:
	TripleStore.java 
Log Message:
Preparing bigdata for license change.  POM may now be used to do a maven compile.  Jini JARs were renamed to include the version (2.1).

Index: TripleStore.java
===================================================================
RCS file: /cvsroot/cweb/bigdata-rdf/src/java/com/bigdata/rdf/TripleStore.java,v
retrieving revision 1.29
retrieving revision 1.30
diff -C2 -d -r1.29 -r1.30
*** TripleStore.java	14 Apr 2007 13:33:52 -0000	1.29
--- TripleStore.java	15 Apr 2007 18:15:55 -0000	1.30
***************
*** 138,145 ****
   *       whether or not we need to abort a transaction in this case.
   * 
   * @todo Refactor to use a delegation mechanism so that we can run with or
   *       without partitioned indices? (All you have to do now is change the
!  *       class that is being extended from Journal to MasterJournal and
!  *       handle some different initialization properties.)
   * 
   * @todo the only added cost for a quad store is the additional statement
--- 138,155 ----
   *       whether or not we need to abort a transaction in this case.
   * 
+  * @todo bnodes do not need to be store in the terms or ids indices if we
+  *       presume that an unknown identifier is a bnode. however, we still need
+  *       to ensure that bnode identifiers are distinct or the same when and
+  *       where appropriate, so we need to assign identifiers to bnodes in a
+  *       restart-safe manner even if we "forget" the term-id mapping.
+  *       
+  * @todo modify the term identifier assignment mechanism to be compatible with
+  *       the scale-out index partitions (32-bit unique within index partition
+  *       identified plus a restart-safe counter for each index partition). 
+  * 
   * @todo Refactor to use a delegation mechanism so that we can run with or
   *       without partitioned indices? (All you have to do now is change the
!  *       class that is being extended from Journal to MasterJournal and handle
!  *       some different initialization properties.)
   * 
   * @todo the only added cost for a quad store is the additional statement