Github user blrunner commented on a diff in the pull request:
https://github.com/apache/tajo/pull/163#discussion_r18319026
--- Diff: tajo-docs/src/main/sphinx/configuration/catalog_configuration.rst
---
@@ -24,6 +24,39 @@ If you want to customize the catalog service, copy
``$TAJO_HOME/conf/catalog-sit
+-----------------------------------+------------------------------------------------+
=========================
+Derby Configuration
+=========================
+
+By default, Tajo uses `Apache Derby <http://db.apache.org/derby/>`_ as a
persistent storage in order to manage table meta data. So, without any
configuration, you can use Derby for catalog store.
+
+Also, you can set manually configs in ``conf/catalog-site.xml`` as follows:
+
+.. code-block:: xml
+
+ <property>
+ <name>tajo.catalog.store.class</name>
+ <value>org.apache.tajo.catalog.store.DerbyStore</value>
+ </property>
+
+ <property>
+ <name>tajo.catalog.uri</name>
+ <value>jdbc:derby:<absolute directory>;create=true</value>
+ </property>
+
+Since Derby is a file-based embedded database, it stores data into a
specified directory. So, you need to specify the directory for storing data
files instead of specifing JDBC URI with hostname and port. For example, in
case where you use '/var/data/tajo-catalog' as a derby store directory, you
should set configs as follows:
--- End diff --
a small typo: specifing -> specifying
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
