Recent changes to FAQ

WikiPage FAQ modified by Dean

Dean — Fri, 13 Jan 2012 07:48:15 -0000

--- v3 
+++ v4 
@@ -17,7 +17,7 @@
 
 Derby will play a role as a MetaData Store for JackHare by default, but this not limit to this RDB only, you can extend the class _net.jackhare.sql.metadata.MetaDataRepository_, for using other RDB as you like :)
 
-\3. How do i pass the noSQL bound parameters via JackHare ?
+\3. How do I pass the noSQL bound parameters via JackHare ?
 
 You can use _java.sql.DriverManager.getConnection_ method to create _java.sql.Connection_, and also put your noSQL bound parameters with _Properties_ object.

WikiPage FAQ modified by Dean

Dean — Fri, 13 Jan 2012 07:47:40 -0000

--- v2 
+++ v3 
@@ -13,7 +13,7 @@
 * We choose the RDB technology to mitigate metadata change transaction issues. 
 
 
-\2. Can i change the __Metadata Store__ to other RDB(or even it is not)?
+\2. Can I change the __Metadata Store__ to other RDB(or even it is not)?
 
 Derby will play a role as a MetaData Store for JackHare by default, but this not limit to this RDB only, you can extend the class _net.jackhare.sql.metadata.MetaDataRepository_, for using other RDB as you like :)

WikiPage FAQ modified by takeshi.miao

takeshi.miao — Thu, 12 Jan 2012 03:38:32 -0000

--- v1 
+++ v2 
@@ -1,20 +1,33 @@
 Frequently Asked Questions as listed as follows...
 
 1. Why we use __Metadata Store__ ?
-2. Can i change the __Metadata Store__ to other RDB(or even it is not)?
-
-
-* Why we use __Metadata Store__ ?
-
+2. Can i change the __Metadata Store__ to other RDB(or even it is not) ?
+3. How do i pass the noSQL bound parameters via JackHare ?
+
+\1. Why we use __Metadata Store__ ?
+
 The __Metadata Datastore__ is a store for the meta data or DB schema (at present, is apache derby). it is like a bridge for maintaining schema between the ANSI-SQL schema and noSQL DB schema (or schemaless). following are the reasons why we use an extra-metadata store.
 
 * Some noSQL DB is schemaless design (like HBase), we need to mitigate this gap between ANSI-SQL schema and these noSQL DB.
 * JackHare can help the data type check and transformation based on the metadata in the metadata store.
 * We choose the RDB technology to mitigate metadata change transaction issues. 
 
 
-* Can i change the __Metadata Store__ to other RDB(or even it is not)?
+\2. Can i change the __Metadata Store__ to other RDB(or even it is not)?
 
 Derby will play a role as a MetaData Store for JackHare by default, but this not limit to this RDB only, you can extend the class _net.jackhare.sql.metadata.MetaDataRepository_, for using other RDB as you like :)
 
-
+\3. How do i pass the noSQL bound parameters via JackHare ?
+
+You can use _java.sql.DriverManager.getConnection_ method to create _java.sql.Connection_, and also put your noSQL bound parameters with _Properties_ object.
+
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+:::java
+Connection conn = null;
+Properties props = new Properties();
+props.setProperty("user", USER_NAME);
+props.setProperty("password", PASSWORD);
+//sample for passing noSQL bound parameter
+props.setProperty("hbase.client.scanner.caching", "20000");
+conn = DriverManager.getConnection(CONNECTION_STRING, props);
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

WikiPage FAQ modified by takeshi.miao

takeshi.miao — Thu, 12 Jan 2012 03:23:14 -0000

Frequently Asked Questions as listed as follows... 1. Why we use __Metadata Store__ ? 2. Can i change the __Metadata Store__ to other RDB(or even it is not)? * Why we use __Metadata Store__ ? The __Metadata Datastore__ is a store for the meta data or DB schema (at present, is apache derby). it is like a bridge for maintaining schema between the ANSI-SQL schema and noSQL DB schema (or schemaless). following are the reasons why we use an extra-metadata store. * Some noSQL DB is schemaless design (like HBase), we need to mitigate this gap between ANSI-SQL schema and these noSQL DB. * JackHare can help the data type check and transformation based on the metadata in the metadata store. * We choose the RDB technology to mitigate metadata change transaction issues. * Can i change the __Metadata Store__ to other RDB(or even it is not)? Derby will play a role as a MetaData Store for JackHare by default, but this not limit to this RDB only, you can extend the class _net.jackhare.sql.metadata.MetaDataRepository_, for using other RDB as you like :)