You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@trafodion.apache.org by db...@apache.org on 2015/12/08 19:06:41 UTC
[1/8] incubator-trafodion git commit: TRAFODION-1507 Second phase of
incubator.trafodion.apache.org update.
Repository: incubator-trafodion
Updated Branches:
refs/heads/master 250ee055b -> d00c7731c
TRAFODION-1507 Second phase of incubator.trafodion.apache.org update.
Please refer to website.md and document.md for information about how to
update the website.
jenkins, skip test
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/commit/1c617ae3
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/tree/1c617ae3
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/diff/1c617ae3
Branch: refs/heads/master
Commit: 1c617ae3968352c6cf0680363350634802c6492c
Parents: fbfab1e
Author: Gunnar Tapper <gt...@esgyn.local>
Authored: Mon Dec 7 09:07:09 2015 -0700
Committer: Gunnar Tapper <gt...@esgyn.local>
Committed: Mon Dec 7 09:07:09 2015 -0700
----------------------------------------------------------------------
docs/src/site/markdown/architecture-overview.md | 3 +
docs/src/site/markdown/code-organization.md | 47 ++---
docs/src/site/markdown/contribute.md | 57 +++---
docs/src/site/markdown/index.md | 34 ++--
docs/src/site/markdown/release-notes-1-3-0.md | 13 +-
docs/src/site/markdown/release-notes.md | 23 +--
docs/src/site/markdown/website.md | 52 +++--
docs/src/site/resources/css/site.css | 21 ++-
.../resources/images/carousel/processes.png | Bin 492019 -> 129503 bytes
.../resources/images/carousel/revolution.png | Bin 185424 -> 66062 bytes
.../site/resources/images/carousel/scale.png | Bin 236303 -> 93783 bytes
.../site/resources/images/carousel/stack.png | Bin 408722 -> 102472 bytes
.../site/resources/images/carousel/timeline.png | Bin 322888 -> 115681 bytes
docs/src/site/site.xml | 189 +++++++++++++++----
14 files changed, 288 insertions(+), 151 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/markdown/architecture-overview.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/architecture-overview.md b/docs/src/site/markdown/architecture-overview.md
index 658e91a..2619d3c 100644
--- a/docs/src/site/markdown/architecture-overview.md
+++ b/docs/src/site/markdown/architecture-overview.md
@@ -11,6 +11,9 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+This page provides information about the Trafodion architecture.
+
+# Introduction
Trafodion provides an operational SQL engine on top of Hadoop -- a solution targeted toward operational workloads in the Hadoop Big Data environment. Included are:
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/markdown/code-organization.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/code-organization.md b/docs/src/site/markdown/code-organization.md
index f8e3119..1ba2057 100644
--- a/docs/src/site/markdown/code-organization.md
+++ b/docs/src/site/markdown/code-organization.md
@@ -11,40 +11,17 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
+This page describes how the Trafodion source tree is organized.
-# Code Organization
-The Trafodion source repository is organized as follows:
+**Under Construction**
-## Connectivity ##
-<span>
- <table>
- <tr>
- <th>Directory</th>
- <th>Contains</th>
- </tr>
- <tr>
- <td><code>core/conn/jdbc_type2</code></td>
- <td>JDBC type-4 client-side driver</td>
- </tr>
- <tr>
- <td><code>jdbc_type4</code></td>
- <td></td>
- </tr>
- <tr>
- <td><code>odb</code></td>
- <td></td>
- </tr>
- <tr>
- <td><code>odbc</code></td>
- <td></td>
- </tr>
- <tr>
- <td><code>security_dll</code></td>
- <td></td>
- </tr>
- <tr>
- <td><code>unixodbc</code></td>
- <td></td>
- </tr>
- </table>
-</span>
+# Connectivity
+
+Directory | Contains
+------------------------------------------------|----------------------------------------------
+**```core/conn/jdbc_type2```** | JDBC type-4 client-side driver
+**```jdbc_type4````** | |
+**```odb```** | |
+**```odbc```** | |
+**```security_dll```** | |
+**```unixodbc```** | |
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/markdown/contribute.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/contribute.md b/docs/src/site/markdown/contribute.md
index 81ea3d9..356f398 100644
--- a/docs/src/site/markdown/contribute.md
+++ b/docs/src/site/markdown/contribute.md
@@ -2,9 +2,9 @@
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
-
+
http://www.apache.org/licenses/LICENSE-2.0
-
+
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
@@ -12,57 +12,58 @@
limitations under the
License.
-->
+This page describes how you can contribute to the Trafodion project.
+
<div class="alert alert-dismissible alert-info">
<button type="button" class="close" data-dismiss="alert">&close;</button>
- <p>Contributing to this project is open to every person caring for the improvement of its product(s) and/or its community — anyone willing to further the project.</p>
-
-<p>If you want to do more; for example, be recognized for your commitment or be eligible for privileges (privileges to commit changes to the code base or have a binding vote on the directions of this project), then please follow steps outlined on this page.</p>
+ <p style="color:black">Contributing to this project is open to every person interested in the improvement of its product(s) and/or its community — anyone willing to further the project.</p>
+ <p style="color:black">If you want to do more; for example, be recognized for your commitment or be eligible for privileges (privileges to commit changes to the code base or have a binding vote on the directions of this project), then please follow steps outlined on this page.</p>
</div>
-
-First of all, a big **Thank You** from us for evaluating and/or using our products. We truly appreciate it! Our products exist and continues to improve thanks to you. But you can help us and yourself more!
-
-We are a community of volunteers working with the guidelines and policies of the Apache Software Foundation (the Apache Way) in mind. Therefore, we welcome any kind of input you can provide to create better products. These contributions, whether you think of reporting bugs, supplying code enhancements, improvements to our documentation, answering questions in our mailing lists, or anywhere else are valuable to us. Because these will help us in helping you.
-
-Your first step toward more involvement in our project is to subscribe to one of our [mailing lists](mail-lists.html). Next, please consider making your first contribution by simply sending an e-mail to our community discussing; for example:
-
+
+First of all, a big **Thank You** from us for your interest in evaluating and/or using Trafodion. We truly appreciate it! Trafodion exists and continues to improve thanks to you. But you can help us and yourself more!
+
+We are a community of volunteers working with the guidelines and policies of the Apache Software Foundation (the Apache Way) in mind. In that spirit, we welcome any kind of input you can provide to create better products. These contributions, whether you think of reporting bugs, supplying code enhancements, making improvements to our documentation, answering questions in our mailing lists, or anywhere else are valuable to everyone. Because each of these helps all of us make Trafodion better.
+
+Your first step toward more involvement in our project is to subscribe to one or more of our [mailing lists](mail-lists.html). Next, please consider making your first contribution by simply sending an e-mail to our community discussing; for example:
+
* What you like about Trafodion and its documentation.
* What you find missing.
-* A bug you encountered.
+* An issue you encountered.
Or, help us by writing articles, blog posts, or sharing information about Trafodion at conferences and on social media such as Twitter (\#trafodion).
-
----
+---
+
## Contribution Ideas
-You've made your first contribution. Now, you can get more involved. For example:
-
+You've made your first contribution. Now, we’re eager to help you get more involved. For example, you can:
+
* Reply to questions, and/or share your viewpoint on how to get issues resolved.
* Add to our [FAQ](faq.html), [Web Site](website.html), or [Wiki](wiki.html).
* Share your code and document patches through our [issue tracking system](issue-tracking.html) (Jira).
* Evaluate bugs and proposed improvements provided by others in our team.
* Help with outlining and evaluating the future direction of our project and the development iterations of our products.
-
+
## Contribution Areas
-Want to be even more involved? Some areas you should consider:
-
+Want to be even more involved? Some areas you could consider:
+
* Source code (bugs and improvements) contributions
* Documentation assistance
* Product and feature suggestions
* Detailed and constructive feedback
* Articles (case studies, white papers, etc) and presentations (speeches) about how our products helps or helped you.
-
+
These are just ideas to get you started. If you feel we missed something there, please let us know (via our [mailing lists](mail-lists.html) ). Together, we can grow Trafodion and its community.
-
+
----
-
+
## Becoming a Registered Contributor
-Do you want to be recognized on the [Team page](team-list.html) like many of us are? If so, please do the following:
-
+Do you want to be recognized on the [Team page](team-list.html) like many other contributors? If so, please do the following:
+
1. Send an email to the dev mailing list of the project stating that you, as a contributor, want to do more and be listed on the Team page. Any community member with edit permissions to the source code can then add your details to the list.
2. Send your [**ICLA**](https://www.apache.org/licenses/icla.txt) to the secretary of the Apache Software Foundation. Refer to the [Licenses](http://www.apache.org/licenses/) page for information about this requirement.
-
+
As soon as you have your ICLA registration confirmed, inform the community. You can now be added (by designated space admins) to:
-
+
* The Trafodion Confluence Contributors group, so that you can add new and edit existing wiki pages.
* The Trafodion JIRA Contributors group, so that you can assign yourself to any open issue in order to bring it further to resolution and/or closure.
-
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/markdown/index.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/index.md b/docs/src/site/markdown/index.md
index 19f7a61..973fea7 100644
--- a/docs/src/site/markdown/index.md
+++ b/docs/src/site/markdown/index.md
@@ -15,7 +15,7 @@
[][revolution]
-Trafodion brings enterprise-clas operational workloads to Hadoop! You can now run all of your data workloads on a single platform based on Hadoop.
+Trafodion brings enterprise-class operational workloads to Hadoop! You can now run all of your data workloads on a single platform based on Hadoop.
#### [Hadoop-Scale with SQL Access][scale]
@@ -80,23 +80,23 @@ Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Traf
</center>
<ul>
<li><a href="architecture-overview.html">Architecture</a></li>
-<li>Documentation</li>
-<li>Videos</li>
-<li>Frequently asked questions</li>
+<li><a href="documentation.html">Documentation</a></li>
+<li><a href="faq.html">FAQ</a></li>
+<li><a href="roadmap.html">Roadmap</a></li>
</ul>
</td>
<td width="25%" valign="top">
<center>
<h2>Use</h2>
<img src="images/logos/use.png" width="108" height="108"/>
-<h4>Download and Try Trafodion</h4>
+<h4>Download and try Trafodion</h4>
<div class="customHr">.</div>
</center>
<ul>
-<li><a href="index.html">Features</a> and roadmap</li>
-<li>Release Notes</li>
-<li>Download and install</li>
-<li>Quick Start</li>
+<li><a href="download.html">Download</a></li>
+<li><a href="quick-start.html">Quick Start</a></li>
+<li><a href="features.html">Features</a></li>
+<li><a href="release-notes.html">Release Notes</a></li>
</ul>
</td>
<td width="25%" valign="top">
@@ -107,10 +107,10 @@ Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Traf
<div class="customHr">.</div>
</center>
<ul>
-<li>Development environment</li>
-<li>Software architecture.</li>
-<li>Contribution workflow</li>
-<li>Participation</li>
+<li><a href="develop.html">Develop</a></li>
+<li><a href="test.html">Test</a></li>
+<li><a href="document.html">Document</a></li>
+<li><a href="advocate.html">Advocate</a></li>
</ul>
</td>
<td width="25%" valign="top">
@@ -121,10 +121,10 @@ Trafodion builds on the scalability, elasticity, and flexibility of Hadoop. Traf
<div class="customHr">.</div>
</center>
<ul>
-<li>Join project team</li>
-<li>Community communication</li>
-<li>Conferences and meetups</li>
-<li>Events Calendar</li>
+<li><a href="contribute.html">Join</a></li>
+<li><a href="mail-lists.html">Discuss</a></li>
+<li><a href="calendar.html">Calendar</a></li>
+<li><a href="presentations.html">Presentations</a></li>
</ul>
</td>
</tr>
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/markdown/release-notes-1-3-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-1-3-0.md b/docs/src/site/markdown/release-notes-1-3-0.md
index 26c4257..94e8eb5 100644
--- a/docs/src/site/markdown/release-notes-1-3-0.md
+++ b/docs/src/site/markdown/release-notes-1-3-0.md
@@ -12,12 +12,11 @@
limitations under the License.
-->
-# Release 1.3.0
This is the first release of the Apache Trafodion (incubating) project. In addition to including a number of new features and improvements across the project, the focus of this release is to comply with Apache release guidelines.
Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
-## Supported Platforms
+# Supported Platforms
The following platforms are supported in this release.
<span>
@@ -95,7 +94,7 @@ This release contains the following new features.
</table>
</span>
-## Improvements
+# Improvements
This release contains the following improvements.
<span>
@@ -138,13 +137,13 @@ This release contains the following improvements.
</table>
</span>
-## Fixes
+# Fixes
This release contains fixes for 114 bugs.
-## Known Issues
+# Known Issues
-### HBase Lease Timeout Patch
+## HBase Lease Timeout Patch
HBase uses a lease mechanism to protect against memory leaks in Region Servers caused by potential client instabilities that would open scanners, but die before having the opportunity to close cleanly and release resources. This mechanism relies on a server side timer, configured by the 'hbase.client.scanner.timeout.period' parameter in 'hbase-site.xml'. If a client fails to call 'next()' within the timeout period, the server will assume the client died, and will force close the server side scanner and release resources. However, in Trafodion, there are legitimate use cases where client is busy doing heavy processing, and needs more time than specified in the default scanner timeout value. Increasing the 'hbase.client.scanner.timeout.period' value has the side effect of weakening the safety mechanism previously described.
@@ -154,7 +153,7 @@ The HBase community agrees that the correct behavior of this safety feature shou
<name>hbase.trafodion.patchclientscanner.enabled</name>
<value>true</value>
<description>
- Enable a Trafodion feature to allow a client to reset the HBase scanner and resume where it left off instead of throwing an exception upon expiry of the HBase hbase.client.scanner.timeout.period timer.
+ Enable a Trafodion feature to allow a client to reset the HBase scanner and resume where it left off instead of throwing an exception upon expiration of the HBase hbase.client.scanner.timeout.period timer.
</description>
</property>
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/markdown/release-notes.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes.md b/docs/src/site/markdown/release-notes.md
index 19f46e8..79518d0 100644
--- a/docs/src/site/markdown/release-notes.md
+++ b/docs/src/site/markdown/release-notes.md
@@ -12,20 +12,13 @@
limitations under the License.
-->
-# Release Notes
The following releases have been created for Trafodion.
-<span>
- <table>
- <tr>
- <th>Release</th>
- <th>Description</th>
- <th>Date</th>
- </tr>
- <tr>
- <td><a href="release-notes-1-3-0.html"><strong>1.3.0</strong></a></td>
- <td>First Apache Release.</td>
- <td>November 16, 2015</td>
- </tr>
- </table>
-</span>
\ No newline at end of file
+Release | Description | Date
+--------------------------------------|-----------------------------------------------------------------------|--------------
+**[1.3.0](release-notes-1-3-0.html)** | First Apache release. | November 2015
+**[1.1.0](release-notes-1-1-0.html)** | Major feature enhancements. Non-Apache release. | April 2015
+**[1.0.1](release-notes-1-0-1.html)** | Defect repair. Non-Apache release. | February 2015
+**[1.0.0](release-notes-1-0-0.html)** | Performance, stability, and new features. Non-Apache release. | January 2015
+**[0.9.0](release-notes-0-9-0.html)** | HBase 0.98 and many feature improvements. Non-Apache release. | October 2014
+**[0.8.0](release-notes-0-8-0.html)** | Initial release. Basic SQL and ACID transactions. Non-Apache release. | June 2014
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/markdown/website.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/website.md b/docs/src/site/markdown/website.md
index 4321788..6d98b71 100644
--- a/docs/src/site/markdown/website.md
+++ b/docs/src/site/markdown/website.md
@@ -12,9 +12,18 @@
limitations under the
License.
-->
-# Making Changes
+This page describes how to change the Trafodion web pages. Please refer to the [Contribute](contribute.html) page for information about other ways to contribute to the Trafodion project.
+
+#Organization
+
+**Source**: **```docs/src```** in the Trafodion source tree.
+
+**Publication:** https://git-wip-us.apache.org/repos/asf/incubator-trafodion-site.git
+
+You develop and test all changes in the Trafodion source tree. Once checked in and built, the content of ```docs/target``` plus different [documentation](document.html) are copied to https://git-wip-us.apache.org/repos/asf/incubator-trafodion-site.git. The changes are then pushed out by Apache [svnpubsub](http://svn.apache.org/viewvc/subversion/trunk/tools/server-side/svnpubsub/), thereby populating http://incubator.trafodion.apache.org.
-The Trafodion web site is part of the Trafodion source tree. The following information helps you understand how to make changes to the web-site content.
+# Making Changes
+The following information helps you understand how to make changes to the web-site content.
----
@@ -25,40 +34,55 @@ The Trafodion website uses the following technologies:
* **Framework**: [Apache Maven Site](https://maven.apache.org)
* **Skin**: [Reflow Maven Skin](http://andriusvelykis.github.io/reflow-maven-skin/)
* **Theme**: [Bootswatch Cerulean](http://bootswatch.com/cerulean)
-* **Markup**: [markdown](https://daringfireball.net/projects/markdown/syntax)
+* **Markdown**: [markdown](https://guides.github.com/features/mastering-markdown/)
+
+<a href="#" class="btn btn-primary btn-xs">Note</a> **```markdown```** was chosen since it supports inline HTML, which provides better table control than APT. Asciidoc does not work well with the Reflow Maven Skin — we tested.
-<a href="#" class="btn btn-primary btn-xs">Note</a> **<code>markdown</code>** was chosen since it supports inline HTML, which provides better table control than APT. Asciidoc does not work well with the Reflow Maven Skin — we tested.
+**Note**: Markdown supports basic tables only; that is, you'll need to use ```<table>``` HTML definitions for formatted tables such as cells with bullet lists.
## Code Organization
-The code is located in the **<code>docs</code>** directory. The code organization follows the [Maven standard](https://maven.apache.org/guides/mini/guide-site.html).
+The code is located in the **```docs```** directory. The code organization follows the [Maven standard](https://maven.apache.org/guides/mini/guide-site.html).
-**<code>docs/src/site.xml</code>** is configured per the [Reflow Maven Skin documentation](http://andriusvelykis.github.io/reflow-maven-skin/skin/). Pages and menus are defined and configured in this file. By default, all pages use an automated table of contents; override as needed.
+**```docs/src/site.xml```** is configured per the [Reflow Maven Skin documentation](http://andriusvelykis.github.io/reflow-maven-skin/skin/). Pages and menus are defined and configured in this file. By default, all pages use an automated table of contents; override as needed.
-**<code>docs/src/site/markdown</code>** contains the files that generate the different HTML files.
+**```docs/src/site/markdown```** contains the files that generate the different HTML files.
-**<code>docs/target</code>** contains the generated HTML files after you run a build.
+**```docs/target```** contains the generated HTML files after you run a build.
## Managing Pages
-You add/rename/delete pages in **<code>docs/src/site/markdown</code>**. You make corresponding changes in **<code>docs/src/site.xml</code>** adding/renaming/deleting pages from menus and defining page configuration; for example: removal of the table of contents bar and the special page formatting provided by the Reflow skin. Refer to the [Maven Documentation](http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html) for more information.
+You add/rename/delete pages in **```docs/src/site/markdown```**. You make corresponding changes in **```docs/src/site.xml```** adding/renaming/deleting pages from menus and defining page configuration; for example: removal of the table of contents bar and the special page formatting provided by the Reflow skin. Refer to the [Maven Documentation](http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html) for more information.
## Providing Content
When possible, ensure that you write in active voice and to the point.
-Special functions such as buttons etc. can be access by clicking **Preview** in the theme preview. There's a \<\> feature on each function, which allows you to copy the special **<code>\<div\></code>** you need to insert the selected object.
+Special functions such as buttons etc. can be access by clicking **Preview** in the theme preview. There's a \<\> feature on each function, which allows you to copy the special **```\<div\>```** you need to insert the selected object.
## Development Environment
-Typically, you'll use Eclipse to develop and build the website pages. The configuration goal is: **<code>clean site</code>**. The **<code>pom.xml</code>** file in the top-level directory drives the build steps for the web site.
+Typically, you'll use Eclipse to develop and build the website pages. The configuration goal is: **```clean site```**. The **```pom.xml```** file in the top-level directory drives the build steps for the web site.
## Testing Changes
-The website files are located in **<code>docs/target</code>**. Open **<code>index.html</code>** from your browser and test your changes. For example, you want to validate the page layout, page navigation, links, and review the overall content on the pages you modified or added/deleted.
+The website files are located in **```docs/target```**. Open **```index.html```** from your browser and test your changes. For example, you want to validate the page layout, page navigation, links, and review the overall content on the pages you modified or added/deleted.
----
-# Publishing Web Site
+# Publishing
+
+<div class="alert alert-dismissible alert-info">
+ <button type="button" class="close" data-dismiss="alert">&close;</button>
+ <p style="color:black">Publication is done when a committer is ready to update the external web site. You do <strong>not</strong> perform these steps as part of checking in changes.</p></div>
+
+Do the following:
+
+1. Check in your changes to the Trafodion source tree.
+2. Build Trafodion.
+3. If there are documentation changes: Follow the [documentation publishing](document.html#Publishing) instructions.
+3. ```svn checkout``` https://git-wip-us.apache.org/repos/asf/incubator-trafodion-site.git
+4. Copy content of ```docs/target``` into the svn ```asf-site``` directory.
+5. ```svn commit``` the changes.
-To be written.
\ No newline at end of file
+Once committed, Apache [svnpubsub](http://svn.apache.org/viewvc/subversion/trunk/tools/server-side/svnpubsub/) takes care of populating http://incubator.trafodion.apache.org with your new changes.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/resources/css/site.css
----------------------------------------------------------------------
diff --git a/docs/src/site/resources/css/site.css b/docs/src/site/resources/css/site.css
index 3685589..72806f2 100644
--- a/docs/src/site/resources/css/site.css
+++ b/docs/src/site/resources/css/site.css
@@ -21,8 +21,8 @@
* @@@ END COPYRIGHT @@@
*/
- .color-highlight {
- color: #225E9B;
+.color-highlight {
+ color: red;
}
body {
@@ -41,7 +41,14 @@ body[class*="page-themes-bootswatch"] .color-highlight {
margin-top: 10px;
}
-/*h1, */h2 {
+h1 {
+ margin-top: 50px;
+ color: #1a334c;
+ border-bottom: 1px gray;
+ width:100%;
+}
+
+h2 {
margin-top: 30px;
}
@@ -60,6 +67,14 @@ h3, h4, h5, h6 {
margin-bottom: 10px;
}
+/* Override the default static position to ensure correct placement on small screens */
+/* Bottom gives space between the box and the following text. */
+.carousel-caption {
+ position: relative;
+ bottom: 5px;
+}
+
+/* Color of the heading in the text box */
.carousel-caption a {
color: white;
}
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/resources/images/carousel/processes.png
----------------------------------------------------------------------
diff --git a/docs/src/site/resources/images/carousel/processes.png b/docs/src/site/resources/images/carousel/processes.png
index 3a183c8..772aa50 100644
Binary files a/docs/src/site/resources/images/carousel/processes.png and b/docs/src/site/resources/images/carousel/processes.png differ
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/resources/images/carousel/revolution.png
----------------------------------------------------------------------
diff --git a/docs/src/site/resources/images/carousel/revolution.png b/docs/src/site/resources/images/carousel/revolution.png
index 51d60cf..a90a754 100644
Binary files a/docs/src/site/resources/images/carousel/revolution.png and b/docs/src/site/resources/images/carousel/revolution.png differ
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/resources/images/carousel/scale.png
----------------------------------------------------------------------
diff --git a/docs/src/site/resources/images/carousel/scale.png b/docs/src/site/resources/images/carousel/scale.png
index 8702614..58f488d 100644
Binary files a/docs/src/site/resources/images/carousel/scale.png and b/docs/src/site/resources/images/carousel/scale.png differ
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/resources/images/carousel/stack.png
----------------------------------------------------------------------
diff --git a/docs/src/site/resources/images/carousel/stack.png b/docs/src/site/resources/images/carousel/stack.png
index 553686a..7cb7673 100644
Binary files a/docs/src/site/resources/images/carousel/stack.png and b/docs/src/site/resources/images/carousel/stack.png differ
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/resources/images/carousel/timeline.png
----------------------------------------------------------------------
diff --git a/docs/src/site/resources/images/carousel/timeline.png b/docs/src/site/resources/images/carousel/timeline.png
index c0aedf7..0bfd84c 100644
Binary files a/docs/src/site/resources/images/carousel/timeline.png and b/docs/src/site/resources/images/carousel/timeline.png differ
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/1c617ae3/docs/src/site/site.xml
----------------------------------------------------------------------
diff --git a/docs/src/site/site.xml b/docs/src/site/site.xml
index 4703bc0..a057a09 100644
--- a/docs/src/site/site.xml
+++ b/docs/src/site/site.xml
@@ -66,7 +66,7 @@
<column>About</column>
<column>Using</column>
<column>Features</column>
- <column>Reference</column>
+ <column>Contributing</column>
</bottomNav>
<bottomDescription>
<![CDATA[
@@ -94,9 +94,13 @@
<body />
</sections>
</index>
+ <advocate><shortTitle>Advocate</shortTitle></advocate>
<architecture-overview><shortTitle>Architecture Overview</shortTitle></architecture-overview>
+ <build><shortTitle>Build Trafodion</shortTitle></build>
+ <build-tools-manual><shortTitle>Build Tools Manual Installation</shortTitle></build-tools-manual>
+ <code><shortTitle>Modify Code</shortTitle></code>
<contribute>
- <shortTitle>How to Contribute</shortTitle>
+ <shortTitle>Contribute</shortTitle>
<toc>false</toc>
<sections>
<body />
@@ -104,23 +108,119 @@
<body />
</sections>
</contribute>
+ <cplusplus-coding-guidelines>
+ <shortTitle>C++ Coding Guidelines</shortTitle>
+ <!-- Smaller than standard due to long headings -->
+ <tocTopMax>5</tocTopMax>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </cplusplus-coding-guidelines>
+ <create-dev-environment>
+ <shortTitle>Create Development Environment</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ <!-- Smaller than standard due to long headings -->
+ <tocTopMax>5</tocTopMax>
+ </create-dev-environment>
<develop>
- <shortTitle>How to Develop</shortTitle>
+ <shortTitle>Develop</shortTitle>
<sections>
<body />
</sections>
</develop>
+ <document><shortTitle>Modify Documentation</shortTitle></document>
+ <documentation><shortTitle>Documentation Library</shortTitle></documentation>
+ <download><shortTitle>Download</shortTitle></download>
+ <enable-secure-trafodion><shortTitle>Enabling Security Features in Trafodion</shortTitle></enable-secure-trafodion>
<faq>
<toc>top</toc>
<shortTitle>Frequently Asked Questions</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
<tocTopFlatten>false</tocTopFlatten>
</faq>
+ <install>
+ <shortTitle>Install</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </install>
+ <install-preparation>
+ <shortTitle>Install Preparation</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </install-preparation>
<issue-tracking><toc>false</toc></issue-tracking>
- <license><toc>false</toc></license>
- <mail-lists><toc>false</toc></mail-lists>
+ <ldapcheck><shortTitle>ldapcheck</shortTitle></ldapcheck>
+ <ldapconfigcheck><shortTitle>ldapconfigcheck</shortTitle></ldapconfigcheck>
+ <license><shortTitle>License</shortTitle><toc>false</toc></license>
+ <mail-lists><shortTitle>Mailing Lists</shortTitle><toc>false</toc></mail-lists>
+ <management><shortTitle>Managing Trafodion</shortTitle><toc>false</toc></management>
+ <manage-dev-environment>
+ <shortTitle>Manage Development Environment</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ <!-- Smaller than standard due to long headings -->
+ <tocTopMax>5</tocTopMax>
+ </manage-dev-environment>
+ <new-features><shortTitle>New Features</shortTitle></new-features>
+ <performance><shortTitle>Performance</shortTitle></performance>
+ <presentations><shortTitle>Presentations</shortTitle><toc>false</toc></presentations>
+ <port-assignment>
+ <toc>false</toc>
+ <shortTitle>Port Assignment</shortTitle>
+ </port-assignment>
+ <quickstart><shortTitle>Quick Start</shortTitle></quickstart>
<release-notes><toc>false</toc></release-notes>
+ <release-notes-1-3-0>
+ <shortTitle>Release 1.3.0</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </release-notes-1-3-0>
+ <release-notes-1-1-0>
+ <shortTitle>Release 1.1.0</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </release-notes-1-1-0>
+ <release-notes-1-0-1>
+ <shortTitle>Release 1.0.1</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </release-notes-1-0-1>
+ <release-notes-1-0-0>
+ <shortTitle>Release 1.0.0</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </release-notes-1-0-0>
+ <release-notes-0-9-0>
+ <shortTitle>Release 0.9.0</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </release-notes-0-9-0>
+ <release-notes-0-8-0>
+ <shortTitle>Release 0.8.0</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </release-notes-0-8-0>
+ <roadmap><shortTitle>Roadmap</shortTitle></roadmap>
+ <setup-build-environment>
+ <shortTitle>Setup Build Environment</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ <!-- Smaller than standard due to long headings -->
+ <tocTopMax>5</tocTopMax>
+ </setup-build-environment>
+ <tests>
+ <shortTitle>Modify Tests</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </tests>
+ <testing>
+ <shortTitle>Testing</shortTitle>
+ <!-- Use H1 headings only for the TOC -->
+ <tocTopFlatten>false</tocTopFlatten>
+ </testing>
+ <traf_authentication_config><shortTitle>.traf_authentication_config Configuration File</shortTitle></traf_authentication_config>
<website>
- <shortTitle>How to Update Web Site</shortTitle>
+ <shortTitle>Modify Web Site</shortTitle>
<tocTopFlatten>false</tocTopFlatten>
<sections>
<body />
@@ -137,6 +237,9 @@
<breadcrumbs>
<item name="Trafodion" href="index.html"/>
</breadcrumbs>
+ <links>
+ <item name="Download" href="download.html"/>
+ </links>
<menu name="About">
<item href="index.html" name="Project Overview"/>
<item href="new-features.html" name="New Features"/>
@@ -150,45 +253,67 @@
<item href="source-repository.html" name="Source Repository"/>
<item href="issue-tracking.html" name="Issue Tracking"/>
<item href="license.html" name="License"/>
- <item href="http:divider" name=""/>
- <item href="download.html" name="Download"/>
- <item href="install.html" name="Install"/>
</menu>
<menu name="Using">
- <item href="faq.html" name="F.A.Q."/>
<item href="quickstart.html" name="Quick Start"/>
+ <item href="download.html" name="Download"/>
+ <item href="install.html" name="Install"/>
+ <item href="management.html" name="Managing Trafodion"/>
+ <item href="http:divider" name=""/>
+ <item href="documentation.html" name="Documentation"/>
+ <item href="faq.html" name="FAQ"/>
+ <item href="release-notes.html" name="Release Notes"/>
<item href="http:divider" name=""/>
<item href="udf-tutorial.html" name="UDF API Tutorial"/>
</menu>
<menu name="Features">
<item href="architecture.html" name="Architecture Overview"/>
- <item href="technology-previews.html" name="Technology Preview"/>
- </menu>
- <menu name="Documentation">
- <item href="documentation.html" name="Documenation Library"/>
- <item href="http:divider" name=""/>
- <item href="release-notes.html" name="Release Notes"/>
- <item href="install.html" name="Installation Guide"/>
- <item href="docs/apache_trafodion_client_installation_guide.pdf" name="Client Installation Guide"/>
<item href="http:divider" name=""/>
- <item href="docs/apache_trafodion_reference_guide.pdf" name="SQL Reference Guide"/>
- <item href="connectivity-reference" name="Connectivity Reference Guide"/>
- <item href="docs/apache_trafodion_trafci_guide.pdf" name="Command Interface Guide"/>
- <item href="rest-reference" name="REST Reference Guide"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/security-ansi-schemas" name="ANSI Schema Support"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/ustat-automation" name="Automated Update Statistics"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/bulkunload" name="Bulk Unload"/>
+ <item href="https://wiki.trafodion.org/wiki/index.php/Trafodion_Manageability#Logging_Events" name="Event Handling"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/hybrid-query-cache" name="Hybrid Query Cache"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/identity-column" name="Identity Column"/>
+ <item href="https://wiki.trafodion.org/wiki/index.php/Creating_Statistics_During_Bulk_Load" name="Immediate Update Statistics"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/lob-support" name="Large Object (LOB)"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/ddl-query-invalidation" name="Metadata Query Invalidation"/>
+ <item href="https://cwiki.apache.org/confluence/display/TRAFODION/Cmp-divisioning" name="Multi-Temperature Data"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/access-external-hbase-tables" name="Native HBase Tables"/>
+ <item href="docs/Trafodion_odb_User_Guide.pdf" name="ODB"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/sql-query-cancel" name="Query Cancel"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/security-privilege-updates" name="Privilege Checking"/>
+ <item href="https://wiki.trafodion.org/wiki/index.php/Trafodion_Manageability" name="Repository"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/enable-get-statistics-thru-rms" name="Runtime Management System"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/sequence-numbers" name="Sequence Numbers"/>
+ <item href="https://blueprints.launchpad.net/trafodion/+spec/skew-buster" name="Skew Buster"/>
+ <item href="https://wiki.trafodion.org/wiki/index.php/Tutorial:_The_object-oriented_UDF_interface" name="Table-Oriented UDF"/>
+ <item href="https://wiki.trafodion.org/wiki/index.php/Data_Loading#Trickle_Loading_Data_Into_Trafodion_Tables" name="Trickle Load"/>
<item href="http:divider" name=""/>
- <item href="docs/apache_trafodion_odb_user_guide.pdf" name="ODB User Guide"/>
- <item href="data-loading.html" name="Data Loading Guide"/>
- <item href="open-cart.html" name="Opencart Demo Guide"/>
+ <item href="https://wiki.trafodion.org/wiki/index.php/Backup_and_Restore" name="Backup/Restore Utility"/>
+ <item href="https://wiki.trafodion.org/wiki/index.php/Metadata_Cleanup" name="Metadata Cleanup Utility"/>
</menu>
<menu name="Contributing">
- <item href="contribute.html" name="How to Contribute"/>
- <item href="develop.html" name="How to Develop"/>
- <item href="release.html" name="How to Test"/>
- <item href="release.html" name="How to Release"/>
- <item href="website.html" name="How to Update Web Site"/>
- <item href="wiki.html" name="How to Update Wiki Pages"/>
+ <item href="contribute.html" name="Contribute"/>
+ <item href="advocate.html" name="Advocate"/>
+ <item href="develop.html" name="Develop"/>
+ <item href="testing.html" name="Test"/>
+ <item href="merge.html" name="Merge"/>
+ <item href="release.html" name="Release"/>
+ <item href="http:divider" name=""/>
+ <item href="create-dev-environment.html" name="Create Dev Environment"/>
+ <item href="manage-dev-environment.html" name="Manage Dev Environment"/>
+ <item href="setup-build-environment.html" name="Setup Build Environment"/>
+ <item href="build.html" name="Build Trafodion"/>
+ <item href="http:divider" name=""/>
+ <item href="code.html" name="Modify Code"/>
+ <item href="tests.html" name="Modify Tests"/>
+ <item href="document.html" name="Modify Documentation"/>
+ <item href="website.html" name="Modify Web Site"/>
+ <item href="wiki.html" name="Modify Wiki Pages"/>
<item href="http:divider" name=""/>
- <item href="design-papers.html" name="Design Paper Template"/>
+ <item href="cplusplus-coding-guidelines.html" name="C++ Coding Guidelines"/>
+ <!-- item href="design-papers.html" name="Design Paper Template"/ -->
</menu>
<menu name="Apache">
<item href="http://incubator.apache.org/projects/trafodion.html" name="Status Page" target="_blank"/>
[8/8] incubator-trafodion git commit: Merge [TRAFODION-1507] Second
phase of incubator.trafodion.apache.org
Posted by db...@apache.org.
Merge [TRAFODION-1507] Second phase of incubator.trafodion.apache.org
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/commit/d00c7731
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/tree/d00c7731
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/diff/d00c7731
Branch: refs/heads/master
Commit: d00c7731c3b93959f5c8ed0e5b19e8bb57d40ba7
Parents: 250ee05 b033d33
Author: Dave Birdsall <db...@apache.org>
Authored: Tue Dec 8 18:05:42 2015 +0000
Committer: Dave Birdsall <db...@apache.org>
Committed: Tue Dec 8 18:05:42 2015 +0000
----------------------------------------------------------------------
docs/src/site/markdown/advocate.md | 15 +
docs/src/site/markdown/architecture-overview.md | 3 +
docs/src/site/markdown/build-tools-manual.md | 197 ++++++++++++
docs/src/site/markdown/build.md | 80 +++++
docs/src/site/markdown/code-organization.md | 47 +--
docs/src/site/markdown/code.md | 32 ++
docs/src/site/markdown/contribute.md | 59 ++--
.../markdown/cplusplus-coding-guidelines.md | 310 +++++++++++++++++++
.../src/site/markdown/create-dev-environment.md | 153 +++++++++
docs/src/site/markdown/develop.md | 245 +++++++++++++++
docs/src/site/markdown/document.md | 124 ++++++++
docs/src/site/markdown/documentation.md | 25 ++
docs/src/site/markdown/download.md | 36 +++
.../site/markdown/enable-secure-trafodion.md | 224 ++++++++++++++
docs/src/site/markdown/faq.md | 220 +++++++++++++
docs/src/site/markdown/index.md | 34 +-
docs/src/site/markdown/install-preparation.md | 138 +++++++++
docs/src/site/markdown/install-troubleshoot.md | 21 ++
docs/src/site/markdown/install.md | 201 ++++++++++++
docs/src/site/markdown/ldapcheck.md | 41 +++
docs/src/site/markdown/ldapconfigcheck.md | 48 +++
.../src/site/markdown/manage-dev-environment.md | 51 +++
docs/src/site/markdown/management.md | 62 ++++
docs/src/site/markdown/merge.md | 140 +++++++++
docs/src/site/markdown/new-features.md | 15 +
docs/src/site/markdown/passwordless-ssh.md | 131 ++++++++
docs/src/site/markdown/performance.md | 15 +
docs/src/site/markdown/port-assignment.md | 134 ++++++++
docs/src/site/markdown/presentations.md | 18 ++
docs/src/site/markdown/quickstart.md | 15 +
docs/src/site/markdown/release-notes-0-8-0.md | 165 ++++++++++
docs/src/site/markdown/release-notes-0-9-0.md | 210 +++++++++++++
docs/src/site/markdown/release-notes-1-0-0.md | 256 +++++++++++++++
docs/src/site/markdown/release-notes-1-0-1.md | 250 +++++++++++++++
docs/src/site/markdown/release-notes-1-1-0.md | 181 +++++++++++
docs/src/site/markdown/release-notes-1-3-0.md | 15 +-
docs/src/site/markdown/release-notes.md | 23 +-
docs/src/site/markdown/release.md | 225 ++++++++++++++
docs/src/site/markdown/roadmap.md | 15 +
.../site/markdown/setup-build-environment.md | 160 ++++++++++
docs/src/site/markdown/testing.md | 179 +++++++++++
docs/src/site/markdown/tests.md | 71 +++++
.../site/markdown/traf_authentication_config.md | 96 ++++++
docs/src/site/markdown/website.md | 52 +++-
docs/src/site/markdown/wiki.md | 23 ++
docs/src/site/resources/css/site.css | 21 +-
.../resources/images/carousel/processes.png | Bin 492019 -> 129503 bytes
.../resources/images/carousel/revolution.png | Bin 185424 -> 66062 bytes
.../site/resources/images/carousel/scale.png | Bin 236303 -> 93783 bytes
.../site/resources/images/carousel/stack.png | Bin 408722 -> 102472 bytes
.../site/resources/images/carousel/timeline.png | Bin 322888 -> 115681 bytes
.../site/resources/images/multi-layer-esps.png | Bin 0 -> 116303 bytes
docs/src/site/site.xml | 193 ++++++++++--
53 files changed, 4815 insertions(+), 154 deletions(-)
----------------------------------------------------------------------
[6/8] incubator-trafodion git commit: [TRAFODION-1507] Addressed
review comments from Carol, Dave, and Roberta.
Posted by db...@apache.org.
[TRAFODION-1507] Addressed review comments from Carol, Dave, and Roberta.
Jenkins, skip test.
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/commit/731a5c73
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/tree/731a5c73
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/diff/731a5c73
Branch: refs/heads/master
Commit: 731a5c7338ed35fc70e1a4ab7cbb8826ae027a0b
Parents: 0bfd379
Author: Gunnar Tapper <gt...@esgyn.local>
Authored: Mon Dec 7 18:14:40 2015 -0700
Committer: Gunnar Tapper <gt...@esgyn.local>
Committed: Mon Dec 7 18:14:40 2015 -0700
----------------------------------------------------------------------
docs/src/site/markdown/build.md | 2 +-
docs/src/site/markdown/contribute.md | 4 +-
.../src/site/markdown/create-dev-environment.md | 4 +-
docs/src/site/markdown/develop.md | 46 ++++++++++----------
docs/src/site/markdown/document.md | 29 ++++++------
docs/src/site/markdown/download.md | 4 +-
.../site/markdown/enable-secure-trafodion.md | 2 +-
docs/src/site/markdown/install-preparation.md | 4 +-
docs/src/site/markdown/install.md | 16 +++----
docs/src/site/markdown/merge.md | 15 +++++++
docs/src/site/markdown/release-notes-0-8-0.md | 2 +-
docs/src/site/markdown/release-notes-0-9-0.md | 2 +-
docs/src/site/markdown/release-notes-1-0-0.md | 3 +-
docs/src/site/markdown/release-notes-1-0-1.md | 11 ++---
docs/src/site/markdown/release-notes-1-1-0.md | 6 +--
docs/src/site/markdown/release-notes-1-3-0.md | 2 +-
docs/src/site/markdown/release-notes.md | 2 +-
docs/src/site/markdown/release.md | 10 ++---
.../site/markdown/setup-build-environment.md | 6 +--
docs/src/site/markdown/testing.md | 2 +-
docs/src/site/site.xml | 4 +-
21 files changed, 98 insertions(+), 78 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/build.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/build.md b/docs/src/site/markdown/build.md
index 960b928..3140e1e 100644
--- a/docs/src/site/markdown/build.md
+++ b/docs/src/site/markdown/build.md
@@ -34,7 +34,7 @@ The source code for Apache Trafodion can be downloaded from [Apache Trafodion In
cd <trafodion download directory>
tar -xzf <tar file>
-# Setup Environmental Variables
+# Set Up Environmental Variables
Start a new **```ssh```** session. Use the following commands to set up the Trafodion environmental variables.
cd <Trafodion source directory>
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/contribute.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/contribute.md b/docs/src/site/markdown/contribute.md
index 356f398..c971b57 100644
--- a/docs/src/site/markdown/contribute.md
+++ b/docs/src/site/markdown/contribute.md
@@ -22,7 +22,7 @@ This page describes how you can contribute to the Trafodion project.
First of all, a big **Thank You** from us for your interest in evaluating and/or using Trafodion. We truly appreciate it! Trafodion exists and continues to improve thanks to you. But you can help us and yourself more!
-We are a community of volunteers working with the guidelines and policies of the Apache Software Foundation (the Apache Way) in mind. In that spirit, we welcome any kind of input you can provide to create better products. These contributions, whether you think of reporting bugs, supplying code enhancements, making improvements to our documentation, answering questions in our mailing lists, or anywhere else are valuable to everyone. Because each of these helps all of us make Trafodion better.
+We are a community of volunteers working with the guidelines and policies of the Apache Software Foundation (the Apache Way) in mind. In that spirit, we welcome any kind of input you can provide to create better products. These contributions, whether you think of reporting bugs, supplying code enhancements, making improvements to our documentation, answering questions in our [mailing lists](mail-lists.html), or anywhere else are valuable to everyone. Because each of these helps all of us make Trafodion better.
Your first step toward more involvement in our project is to subscribe to one or more of our [mailing lists](mail-lists.html). Next, please consider making your first contribution by simply sending an e-mail to our community discussing; for example:
@@ -52,7 +52,7 @@ Want to be even more involved? Some areas you could consider:
* Detailed and constructive feedback
* Articles (case studies, white papers, etc) and presentations (speeches) about how our products helps or helped you.
-These are just ideas to get you started. If you feel we missed something there, please let us know (via our [mailing lists](mail-lists.html) ). Together, we can grow Trafodion and its community.
+These are just ideas to get you started. If you feel we missed something there, please let us know via our mailing lists. Together, we can grow Trafodion and its community.
----
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/create-dev-environment.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/create-dev-environment.md b/docs/src/site/markdown/create-dev-environment.md
index acd840d..50eea4d 100644
--- a/docs/src/site/markdown/create-dev-environment.md
+++ b/docs/src/site/markdown/create-dev-environment.md
@@ -108,7 +108,7 @@ Command | Usage
**```install_local_hadoop -p rand```** | Start with any random port number range between 9000 and 49000.
**```install_local_hadoop -p <port>```** | Start with the specified port number.
-For a list of ports that get configured and their default values, please refer to [Port Assignments](port-assignments.html).
+For a list of ports that get configured and their default values, please refer to [Port Assignments](port-assignment.html).
### Sample Procedure
Start a new **```ssh```** session and ensure that the Trafodion environmental variables are loaded.
@@ -150,4 +150,4 @@ You need to do the following each time you download new source code.
sqgen
# Manage
-Please refer to [Manage Development Environment](manage-dev-environment) for instructions.
+Please refer to [Manage Development Environment](manage-dev-environment.html) for instructions.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/develop.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/develop.md b/docs/src/site/markdown/develop.md
index 79656d8..78a5b35 100644
--- a/docs/src/site/markdown/develop.md
+++ b/docs/src/site/markdown/develop.md
@@ -26,23 +26,23 @@ You need to register as a Trafodion contributor before you can help us develop T
<tr>
<td><strong>Individual Contributor License Agreement (ICLA)</strong></td>
<td>You should sign the ICLA before contributing content to the Trafodion source tree. (Required to become a committer.)</td>
- <td><a href="https://www.apache.org/licenses/icla.txt" target="_blank">ICLA Agreement</a><br />
- <a href="http://www.apache.org/licenses/" target="_blank">Approval Process</a>
+ <td><a href="https://www.apache.org/licenses/icla.txt">ICLA Agreement</a><br />
+ <a href="http://www.apache.org/licenses/">Approval Process</a>
</td>
</tr>
<tr>
<td><strong>Source Control</strong></td>
<td>You must have a git account in order to contribute to the Trafodion source. If you haven't already done so, please join git.</td>
- <td><a href="https://github.com/join" target="_blank">Git Signup</a></td>
+ <td><a href="https://github.com/join">Git Signup</a></td>
</tr>
<tr>
<td><strong>Defect Tracking</strong></td>
<td>In order to have certain permissions, including assigning issues to yourself, you need to be a Contributor in the project. Be sure to sign up for a JIRA account if you don't have one.</td>
- <td><a href="https://issues.apache.org/jira/secure/Signup!default.jsp" target="_blank">Jira Signup</a></td>
+ <td><a href="https://issues.apache.org/jira/secure/Signup!default.jspa">Jira Signup</a></td>
</tr>
</table>
-Please send an e-mail to the [Trafodion development list](mail-lists.hmtl) with the approved ICLA attached. Include your git and Jira IDs.
+Please send an e-mail to the [Trafodion development list](mail-lists.html) with the approved ICLA attached. Include your git and Jira IDs.
Wait for the response and then you're ready to help us develop Trafodion.
@@ -61,56 +61,56 @@ You use the following tools and guidelines to develop Trafodion:
<td><strong>Trafodion Architecture</strong></td>
<td>Document</td>
<td>Please review the Trafodion architecture to ensure that you understand how the different components related to each other.</td>
- <td><a href="architecture-overview.html" target="_blank">Trafodion Architecture</a></td>
+ <td><a href="architecture-overview.html">Trafodion Architecture</a></td>
</tr>
<tr>
<td><strong>Defect Tracking</strong></td>
<td>Jira</td>
<td>View all the Trafodion defects and enhancements requests in the Jira system hosted by Apache.</td>
- <td><a href="https://issues.apache.org/jira/browse/TRAFODION" target="_blank">Trafodion Jiras</a></td>
+ <td><a href="https://issues.apache.org/jira/browse/TRAFODION">Trafodion Jiras</a></td>
</tr>
<tr>
<td><strong>Defect Management</strong></td>
<td>Document</td>
<td>Please read about our approach to defect management. Mostly, any changes you'll make will be in response to a defect reported in Jira.</td>
- <td><a href="defect-management.html" target="_blank">Defect Management</a></td>
+ <td><a href="defect-management.html">Defect Management (TBD)</a></td>
</tr>
<tr>
<td><strong>Git Tools</strong></td>
<td>git</td>
- <td><p>Most of the Trafodion development is done on Linux. Development of the web site and/or documentation can successfully be done on Windows.</p><p>Please download the appropriate tool version; Linux or Windows.</p><p>Then, please refer to <a href="https://help.github.com/articles/set-up-git/" target="_blank">GitHub Documentation</a> for information on how to set up your git environment. Ensure that you register your <a href="https://github.com/settings/ssh" target="_blank">ssh keys</a>.</p></td>
- <td><a href="http://git-scm.com/downloads" target="_blank">Download git</a></td>
+ <td><p>Most of the Trafodion development is done on Linux. Development of the web site and/or documentation can successfully be done on Windows.</p><p>Please download the appropriate tool version; Linux or Windows.</p><p>Then, please refer to <a href="https://help.github.com/articles/set-up-git/">GitHub Documentation</a> for information on how to set up your git environment. Ensure that you register your <a href="https://github.com/settings/ssh">ssh keys</a>.</p></td>
+ <td><a href="http://git-scm.com/downloads">Download git</a></td>
</tr>
<tr>
<td><strong>Code Repository</strong></td>
<td>git</td>
<td>The full Trafodion source tree can be retrieved from either of these repositories.</td>
- <td><a href="https://git-wip-us.apache.org/repos/asf/incubator-trafodion.git" target="_blank">Apache Repository</a><br /><a href="https://github.com/apache/incubator-trafodion" target="_blank">GitHub Mirror</a>
+ <td><a href="https://git-wip-us.apache.org/repos/asf/incubator-trafodion.git">Apache Repository</a><br /><a href="https://github.com/apache/incubator-trafodion">GitHub Mirror</a>
</td>
<tr>
</tr>
<td><strong>Code Organization</strong></td>
<td>Document</td>
<td>Please familiarize yourself with the Trafodion code organization.</td>
- <td><a href="code-organization.html" target="_blank">Code Organization</a></td>
+ <td><a href="code-organization.html">Code Organization</a></td>
</tr>
<tr>
<td><strong>C++ Coding Guidelines</strong></td>
<td>Document</td>
<td>Please read the coding guidelines for the Trafodion C++ code before making changes.</td>
- <td><a href="cplusplus-coding-guidelines.html" target="_blank">C++ Coding Guidelines</a></td>
+ <td><a href="cplusplus-coding-guidelines.html">C++ Coding Guidelines</a></td>
</tr>
<tr>
<td><strong>Debugging Tips</strong></td>
<td>Document</td>
<td>Documented tips describing how to debug your code in unit testing.</td>
- <td><a href="debugging-tips.html" target="_blank">Debugging Tips</a></td>
+ <td><a href="debugging-tips.html">Debugging Tips (TBD)</a></td>
</tr>
<tr>
<td><strong>Testing</strong></td>
<td>Document</td>
<td>Trafodion has a rich set of test suites for each of its components. You'll need to run the tests before submitting a code change for review.</td>
- <td><a href="testing.html" target="_blank">How to Test</a></td>
+ <td><a href="testing.html">How to Test</a></td>
</tr>
<tr>
<td><strong>Code Reviews</strong></td>
@@ -118,15 +118,15 @@ You use the following tools and guidelines to develop Trafodion:
<td>
<p>We use GitHub pull-requests for code review. All of the activity on github is captured in ASF JIRA and/or ASF project mail archives by ASF INFRA team automation. In this way, we do not depend on github for accurate history of where contributions come from.</p>
<p>Each pull-request title should start with a JIRA ID in brackets, so that activity can be logged to the correct JIRA issue.</p>
- <p>Regardless of the title, the pull-request activity is also logged to the <a href="http://mail-archives.apache.org/mod_mbox/incubator-trafodion-codereview/" target="_blank">code-review mail list</a>.</p>
+ <p>Regardless of the title, the pull-request activity is also logged to the <a href="http://mail-archives.apache.org/mod_mbox/incubator-trafodion-codereview/">code-review mail list</a>.</p>
</td>
- <td><a href="https://github.com/apache/incubator-trafodion/pulls" target="_blank">Current Pull Requests</a></td>
+ <td><a href="https://github.com/apache/incubator-trafodion/pulls">Current Pull Requests</a></td>
</tr>
</body>
</table>
# Initial Setup
-This set of tasks is performed **after** downloading the git tools. Refer to [Development Tools](#development_tools) above.
+This set of tasks is performed **after** downloading the git tools. Refer to [Development Environment](#development_environment) above.
You should not have to perform these tasks more than once.
@@ -187,7 +187,7 @@ Perform the following steps to commit your changes.
git push trafdeveloper_fork TRAFODION-1507
## Create Pull Request
-You changed code needs to be reviewed by a Trafodion committer. Therefore, you need to create a pull request for your private repository; for example: <https://github.com/trafdeveloper/incubator-trafodion>.
+Your changed code needs to be reviewed by a Trafodion committer. Therefore, you need to create a pull request for your private repositoryc.
# Generate pull request
git pull-request
@@ -204,11 +204,11 @@ Ensure that you include the Jira ID at the beginning of the title in your pull r
The pull request gets reviewed by the committers and once you get a consensus, then the committer merges your changes into the main incubator-trafodion branch.
## Address Review Comments
-Follow the GitHub conversation on you pull request (you should be automatically subscribed). Respond to questions and issues.
+Follow the GitHub conversation on your pull request (you should be automatically subscribed). Respond to questions and issues.
If you need to make additional changes, then do the following:
-1. Checkout the code: **<code>git checkout TRAFODION-1507</code>**
+1. Check out the code: **<code>git checkout TRAFODION-1507</code>**
2. Make the requested changes.
3. Run regression tests.
4. Commit the changes: **<code>git commit -a</code>**
@@ -238,8 +238,8 @@ There are two approaches to reviewing logs.
### Approach 2
* Go to: <http://traf-logs.esgyn.com/PullReq/>
-* Click on the number of the pull request. Example: <http://traf-logs.esgyn.com/PullReq/18/>. The next directory level is the build number. With multiple commits or re-tests, it is possible for a pull request to have multiple builds.
+* Click on the number of the pull request. The next directory level is the build number. With multiple commits or re-tests, it is possible for a pull request to have multiple builds.
* Under the build number is a directory for each specific job. Example: <http://traf-logs.esgyn.com/PullReq/18/35/regress-seabase-ahw2.2/>
## More Information
-The check tests do not include all of the automated daily tests. If you (or another contributor) want, you can run additional tests on the pull request. Refer [automated test setup](automated-tests.html) for more information.
\ No newline at end of file
+The check tests do not include all of the automated daily tests. If you (or another contributor) want, you can run additional tests on the pull request. Refer [automated test setup (TBD)](automated-tests.html) for more information.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/document.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/document.md b/docs/src/site/markdown/document.md
index 021f322..55a1eb9 100644
--- a/docs/src/site/markdown/document.md
+++ b/docs/src/site/markdown/document.md
@@ -21,18 +21,20 @@ Documents do **not** include version information as part of the file name.
Document | Source Format | Source Tree | Output Format
--------------------------|-----------------------|------------------------------------------------|----------------------------
-Client Installation Guide | word | ```docs/src/resources/docs``` | PDF
-Command Interface Guide | word | ```docs/src/resources/docs``` | PDF
+Client Installation Guide | word | External (Word) | PDF
+Command Interface Guide | word | External (Word) | PDF
DCS Reference Guide | asciidoc | ```dcs/src/main/asciidoc``` | Web Book, PDF
DCS APIs | javadoc | ```dcs/src/main/java``` | Web Book
-odb User Guide | word | ```docs/src/resources/docs``` | PDF
+odb User Guide | word | External (Word) | PDF
REST Reference Guide | asciidoc | ```core/rest/src/main/asciidoc``` | Web Book, PDF
REST APIs | javadoc | ```core/rest/src/main/java``` | Web Book
-SQL Reference Manual | word | ```docs/src/resources/docs``` | PDF
+SQL Reference Manual | word | External (Word) | PDF
## Web
-The documentation is copied to the **```docs/target/docs```** directory on a per-release basis. This directory is referred to as the **release document directory** below.
+**```docs/target/docs```** contains the **latest** version of the document. This practice makes it possible to link to a document in instructional text.
+
+In addition, the documentation is copied to the **```docs/target/docs```** directory on a per-release basis. This directory is referred to as the **release document directory** below.
**Example**
@@ -71,11 +73,12 @@ File/Directory | Content
## Word Documents
Do the following:
-1. Edit the document in **```docs/src/resources/docs```**.
-2. Save a PDF version of the document in **```docs/src/resources/docs```**.
+1. Edit the document.
+2. Save a PDF version.
3. Build the web site using **```mvn clean site```** against the **```docs```** directory.
-
-The Word and PDF files will be copied to **```docs/target/docs```** directory. You will need to move the files to the final **Release Document Directory**; refer to [Publishing](#Publishing) below.
+4. Create the **Release Document Directory**, if needed.
+5. Copy the PDF files to the **Release Document Directory**.
+6. Copy and overwrite the PDF to the **```docs/target/docs```** directory — latest version of the document.
## Asciidoc Documents
Please refer to DCS [Contributing to Documentation](https://github.com/apache/incubator-trafodion/blob/master/dcs/src/main/asciidoc/_chapters/appendix_contributing_to_documentation.adoc) guidance for information about working on asciidoc-based documentation.
@@ -102,12 +105,12 @@ You will need to copy/move the documentation from its generated location to the
Document | Populate Release Document Directory
--------------------------|------------------------------------------
-Client Installation Guide | Delete **```.docx```*** file, copy the **```.pdf```** file in **```docs/target/docs```** to the **Release Document Directory**.
-Command Interface Guide | Delete **```.docx```*** file, copy the **```.pdf```** file in **```docs/target/docs```** to the **Release Document Directory**.
+Client Installation Guide | Copy the **```.pdf```** file to **```docs/target/docs```** and **Release Document Directory**.
+Command Interface Guide | Copy the **```.pdf```** file to **```docs/target/docs```** and **Release Document Directory**.
DCS Reference Guide | Copy **```dcs/target/site/```** to the **Release Document Directory**.
-odb User Guide | Delete **```.docx```*** file, copy the **```.pdf```** file in **```docs/target/docs```** to the **Release Document Directory**.
+odb User Guide | Copy the **```.pdf```** file to **```docs/target/docs```** and **Release Document Directory**.
REST Reference Guide | Copy **```core/rest/target/site/```** to the **Release Document Directory**.
-SQL Reference Manual | Delete **```.docx```*** file, copy the **```.pdf```** file in **```docs/target/docs```** to the **Release Document Directory**.
+SQL Reference Manual | Copy the **```.pdf```** file to **```docs/target/docs```** and **Release Document Directory**.
**Example — Publishing the DCS Reference Guide**
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/download.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/download.md b/docs/src/site/markdown/download.md
index ba33c48..d5a68f2 100644
--- a/docs/src/site/markdown/download.md
+++ b/docs/src/site/markdown/download.md
@@ -12,7 +12,7 @@
limitations under the
License.
-->
-This page describes how you download and install the Trafodion product environment. Please refer to [Create Development Environment](create-dev-environment.html] if you want to set up a Trafodion development environment (which includes the installation of a stand-alone Hadoop environment) based on the Trafodion source code.
+This page describes how you download and install the Trafodion product environment. Please refer to [Create Development Environment](create-dev-environment.html) if you want to set up a Trafodion development environment (which includes the installation of a stand-alone Hadoop environment) based on the Trafodion source code.
# Prerequisite
Trafodion is installed onto an existing Hadoop environment.
@@ -27,7 +27,7 @@ Not yet available.
Build your own binaries from the Trafodion source code as follows:
1. [Setup Build Environment](setup-build-environment.html).
-2. [Build Trafodion](build.html) \— use **```make package```**.
+2. [Build Trafodion](build.html) — use **```make package```**.
# Install
Please refer to the [Install](install.html) instructions.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/enable-secure-trafodion.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/enable-secure-trafodion.md b/docs/src/site/markdown/enable-secure-trafodion.md
index 7e23510..f0c73ea 100644
--- a/docs/src/site/markdown/enable-secure-trafodion.md
+++ b/docs/src/site/markdown/enable-secure-trafodion.md
@@ -12,7 +12,7 @@
limitations under the
License.
-->
-This page describes how to Trafodion security.
+This page describes how to enable Trafodion security.
# Introduction
If you do not enable security in Trafodion, a client interface to Trafodion may request a username and password, but Trafodion ignores the user name and password entered in the client interface, and the session runs as the database **```root```** user, **```DB__ROOT```**, without restrictions. If you want to restrict users, restrict access to certain users only, or restrict access to an object or operation, then you must enable security, which enforces authentication and authorization. You can enable security during installation by answering the installer's prompts or after installation by running the **```traf_authentication_setup```** script, which enables both authentication and authorization. For more information, see [Authentication Setup Script](#Authentication_Setup_Script) below.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/install-preparation.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/install-preparation.md b/docs/src/site/markdown/install-preparation.md
index 3848746..40fbce4 100644
--- a/docs/src/site/markdown/install-preparation.md
+++ b/docs/src/site/markdown/install-preparation.md
@@ -34,7 +34,7 @@ Before installing Cloudera Manager, a minimum of 20 GB is needed to support the
Check the available space for **```/var```** as follows:
-* Start a putty or VNC terminal window agains the node where Cloudera Manager will be installed.
+* Start a putty or VNC terminal window against the node where Cloudera Manager will be installed.
* As a user with **```root```** privileges, verify that 20 GB of space is available to **```/var```**.
cd /var
@@ -76,7 +76,7 @@ The Trafodion installer prompts you to set up an authentication configuration fi
If you wish to manually set up the authentication configuration file and enable security, then please refer to [Enabling Security Features in Trafodion](enable-secure-trafodion.html).
-# PC Installation
+# PC Tools
If you are using a Windows PC, then additional PC software may be needed throughout the installation process. It is recommended that you pre-install the PC software that you need before continuing with the Trafodion installation.
Install the following software:
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/install.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/install.md b/docs/src/site/markdown/install.md
index 07fe6af..ec9caca 100644
--- a/docs/src/site/markdown/install.md
+++ b/docs/src/site/markdown/install.md
@@ -19,9 +19,9 @@ The Trafodion product environment is installed using the Trafodion Installer, wh
# Preparation
The Trafodion Installer assumes that you've performed the following steps before a Trafodion install:
-1. **Cluster Requirements**: ensure that you cluster meets the Trafodion requirements.
+1. **Cluster Requirements**: Ensure that your cluster meets the Trafodion requirements.
2. **Security Requirements**: Create the user ID that is used to run the Trafodion Installer. Review and configure LDAP, if desired.
-3. **Prepare PC**: install software used when installing Trafodion on your PC.
+3. **PC Tools**: Install software used when installing Trafodion on your PC.
4. **Install Hadoop**: Install Hadoop software supported by Trafodion.
5. **Validate Hadoop**: Validate that required Hadoop services are running.
@@ -32,10 +32,10 @@ You use the following user IDs and passwords during the Trafodion installation.
Logon | User ID | Password | Description
-----------------------------------|----------------------------|-----------------------------|--------------------------------------------------------
-Cloudera Manager Web GUI logon | **```admin (default)```** | **```admin (default)```** | After installing Cloudera, you will be instructed to log on to the Cloudera Manager Web GUI. Use the default user ID and password (**```admin```**, **```admin```**). If you already had Cloudera installed, please use your previously defined user ID and password.
-Ambari Web GUI logon | **```admin (default)```** | **```admin (default)```** | After downloading and setting up the Ambari repository, you will be instructed to log on to the Ambari Web GUI. Use the default user ID and password (**```admin```**, **```admin```**). If you already had Ambari installed, please use your previously defined user ID and password.
-User ID with sudo Access | **```<sudo-username>```** | **```<password>```** | In the installation steps, you may be instructed to use **```sudo```** or **```sudo userid```** access. You will be using your user ID, which has been enabled with **```sudo```** access and [passwordless ssh](passwordless-ssg.html) to all nodes of the cluster.
-Trafodion Logon | **```trafodion```** | **```traf123 (default)```** | The Trafodion installer **automatically creates** this user IDwhen Trafodion is installed. Do not create this user ID manually.
+Cloudera Manager Web GUI logon | **```admin (default)```** | **```admin (default)```** | Cloudera only. After installing Cloudera, you will be instructed to log on to the Cloudera Manager Web GUI. Use the default user ID and password (**```admin```**, **```admin```**). If you already had Cloudera installed, please use your previously defined user ID and password.
+Ambari Web GUI logon | **```admin (default)```** | **```admin (default)```** | Hortonworks only. After downloading and setting up the Ambari repository, you will be instructed to log on to the Ambari Web GUI. Use the default user ID and password (**```admin```**, **```admin```**). If you already had Ambari installed, please use your previously defined user ID and password.
+User ID with sudo Access | **```<sudo-username>```** | **```<password>```** | In the installation steps, you may be instructed to use **```sudo```** or **```sudo userid```** access. You will be using your user ID, which has been enabled with **```sudo```** access and [passwordless ssh](passwordless-ssh.html) to all nodes of the cluster.
+Trafodion Logon | **```trafodion```** | **```traf123 (default)```** | The Trafodion installer **automatically creates** this user ID when Trafodion is installed. Do not create this user ID manually.
VNC Server Logon | **```trafodion```** | **```traf123 (default)```** | After installing Trafodion, you will be instructed to log on to the VNC server at port 1. Use the **```trafodion```** user ID and **```password```**.
# Install Procedure
@@ -53,9 +53,6 @@ Follow these steps if you have an older version of Trafodion that you want to up
</td></tr></table>
## Installation
-
-<table><tr><td><strong>NOTE</strong><br /> If performing an upgrade: Please refer to [Upgrading Trafodion](#Upgrading_Trafodion) before proceeding.</td></tr></table>
-
At a high level, the following instructions consist of a single step:
Command | User ID | Comments
@@ -188,6 +185,7 @@ Perform a quick sanity check using the Trafodion Conversational Interface (**```
TEST1
--- SQL operation complete.
+ >> drop table test1;
>> exit;
The SQL commands above should run successfully.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/merge.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/merge.md b/docs/src/site/markdown/merge.md
new file mode 100644
index 0000000..5cad622
--- /dev/null
+++ b/docs/src/site/markdown/merge.md
@@ -0,0 +1,15 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page will describe the committer work flow for git merges.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/release-notes-0-8-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-0-8-0.md b/docs/src/site/markdown/release-notes-0-8-0.md
index a6c020b..4966cc9 100644
--- a/docs/src/site/markdown/release-notes-0-8-0.md
+++ b/docs/src/site/markdown/release-notes-0-8-0.md
@@ -14,7 +14,7 @@
This is the initial source-only release of the Apache Trafodion (incubating) project.
-Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+Build instructions are available [here](build.html).
# Supported Platforms
The following platforms are supported in this release.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/release-notes-0-9-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-0-9-0.md b/docs/src/site/markdown/release-notes-0-9-0.md
index a8f0757..f4ad658 100644
--- a/docs/src/site/markdown/release-notes-0-9-0.md
+++ b/docs/src/site/markdown/release-notes-0-9-0.md
@@ -14,7 +14,7 @@
This is the source-only release of the Apache Trafodion (incubating) project. This release provides support for HBase 0.98 and many new product features.
-Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+Build instructions are available [here](build.html).
# Supported Platforms
The following platforms are supported in this release.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/release-notes-1-0-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-1-0-0.md b/docs/src/site/markdown/release-notes-1-0-0.md
index 71abf33..4e2c898 100644
--- a/docs/src/site/markdown/release-notes-1-0-0.md
+++ b/docs/src/site/markdown/release-notes-1-0-0.md
@@ -14,7 +14,7 @@
This is the source-only release of the Apache Trafodion (incubating) project. This release provides a number of new features and improvements across the project plus a large number of bug fixes.
-Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+Build instructions are available [here](build.html).
# Supported Platforms
The following platforms are supported in this release.
@@ -153,6 +153,7 @@ This release contains the following new features.
This release contains fixes to around 85 defects, including 25 critical defects, 54 high defects, and 10 medium and low defects. Those defects were filed through [Launchpad](https://launchpad.net/trafodion/+milestone/r1.1).
# Known Issues
+All defect are located in [Launchpad](https://bugs.launchpad.net/trafodion).
## Getting TM error 97 when tables split or get moved
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/release-notes-1-0-1.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-1-0-1.md b/docs/src/site/markdown/release-notes-1-0-1.md
index 7ec9848..83b2544 100644
--- a/docs/src/site/markdown/release-notes-1-0-1.md
+++ b/docs/src/site/markdown/release-notes-1-0-1.md
@@ -14,7 +14,7 @@
This is the source-only release of the Apache Trafodion (incubating) project. This release provides product-level collection of query statistics and critical bug fixes above [1.0.0](release-notes-1-0-0.html).
-Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+Build instructions are available [here](build.html).
# Supported Platforms
The following platforms are supported in this release.
@@ -76,7 +76,7 @@ This release contains the following new features.
<ul>
<li>[Multi-Temperature Data](https://cwiki.apache.org/confluence/display/TRAFODION/Cmp-divisioning) (Complete But Not Tested)</li>
</ul>
- For more information about automated update statistics and index support enhancements, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ For more information about automated update statistics and index support enhancements, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manual.pdf).
</td>
<td></td>
</tr>
@@ -103,7 +103,7 @@ This release contains the following new features.
<li>[Backup/Restore](https://wiki.trafodion.org/wiki/index.php/Backup_and_Restore). (Complete But Not Tested)</li>
<li>Thread-Safe JDBC Type 2 Driver. (Complete But Not Tested)</li>
</ul>
- For more information about the new UNLOAD statement, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ For more information about the new UNLOAD statement, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manual.pdf).
</td>
<td></td>
</tr>
@@ -116,7 +116,7 @@ This release contains the following new features.
<li>[Event Handling](https://wiki.trafodion.org/wiki/index.php/Trafodion_Manageability#Logging_Events) through UDFs and log4cpp.</li>
<li>Collection of session and query statistics in [Repository Tables](https://wiki.trafodion.org/wiki/index.php/Trafodion_Manageability) (disabled by default)</li>
</ul>
- For more information about gathering SQL runtime statistics and canceling an executing query, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ For more information about gathering SQL runtime statistics and canceling an executing query, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manual.pdf).
</td>
<td></td>
</tr>
@@ -129,7 +129,7 @@ This release contains the following new features.
<li>[Privilege checking for utilities](https://blueprints.launchpad.net/trafodion/+spec/security-privilege-updates).</li>
<li>[Metadata Query Invalidation](https://blueprints.launchpad.net/trafodion/+spec/ddl-query-invalidation) (that is, detection and propagation of privilege changes to SQL compilers).</li>
</ul>
- For more information about ANSI schema support and privilege and authorization updates in this release, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ For more information about ANSI schema support and privilege and authorization updates in this release, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manual.pdf).
</td>
<td></td>
</tr>
@@ -143,6 +143,7 @@ This release contains fixes to around 85 defects, including 25 critical defects,
# Known Issues
Release 1.0.1 provides fixes to these bugs:
+
* **[1415165](https://bugs.launchpad.net/trafodion/+bug/1415165)**: MXOSRVR memory leak when stats are enabled
* **[1421727](https://bugs.launchpad.net/trafodion/+bug/1421727)**: Default/aggregated stats type not publishing query stats
* **[1416539](https://bugs.launchpad.net/trafodion/+bug/1416539)** Snapshot scan installer additions
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/release-notes-1-1-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-1-1-0.md b/docs/src/site/markdown/release-notes-1-1-0.md
index af3a199..6339ea2 100644
--- a/docs/src/site/markdown/release-notes-1-1-0.md
+++ b/docs/src/site/markdown/release-notes-1-1-0.md
@@ -14,7 +14,7 @@
This is the source-only release of the Apache Trafodion (incubating) project. In addition to including a number of new features and improvements across the project, the focus of this release is to comply with Apache release guidelines.
-Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+Build instructions are available [here](build.html).
# Supported Platforms
The following platforms are supported in this release.
@@ -105,7 +105,7 @@ This release contains the following new features.
<ul>
<li>Support for HP Data Services Manager (HP DSM), a unified, browser-based tool for management of Hadoop, Vertica, and now Trafodion data services. **NOTE**: The version of HP DSM that integrates with Trafodion is not yet available.</li>
<li>Stability and overhead optimizations to reduce the overhead of capturing and maintaining query performance information (in repository tables).</li>
- <li>Query cancel for DDL, update statistics, and additional child query operations. For details, see the CONTROL QUERY CANCEL statement in the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).</li>
+ <li>Query cancel for DDL, update statistics, and additional child query operations. For details, see the CONTROL QUERY CANCEL statement in the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manual.pdf).</li>
</ul>
</td>
<td></td>
@@ -117,7 +117,7 @@ This release contains the following new features.
<li>Security subsystem hardening improvements including performance and QA testing.</li>
<li>Security enhancements for the Trafodion metadata, data loader, and Data Connectivity Services (DCS).</li>
<li>Upgrade authorization.</li>
- <li>Ability to grant privileges on behalf of a role using the GRANTED BY clause. For details, see the GRANT statements in the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).</li>
+ <li>Ability to grant privileges on behalf of a role using the GRANTED BY clause. For details, see the GRANT statements in the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manual.pdf).</li>
</ul>
</td>
<td></td>
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/release-notes-1-3-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-1-3-0.md b/docs/src/site/markdown/release-notes-1-3-0.md
index 94e8eb5..62a8f16 100644
--- a/docs/src/site/markdown/release-notes-1-3-0.md
+++ b/docs/src/site/markdown/release-notes-1-3-0.md
@@ -14,7 +14,7 @@
This is the first release of the Apache Trafodion (incubating) project. In addition to including a number of new features and improvements across the project, the focus of this release is to comply with Apache release guidelines.
-Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+Build instructions are available [here](build.html).
# Supported Platforms
The following platforms are supported in this release.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/release-notes.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes.md b/docs/src/site/markdown/release-notes.md
index 79518d0..0be9a26 100644
--- a/docs/src/site/markdown/release-notes.md
+++ b/docs/src/site/markdown/release-notes.md
@@ -16,7 +16,7 @@ The following releases have been created for Trafodion.
Release | Description | Date
--------------------------------------|-----------------------------------------------------------------------|--------------
-**[1.3.0](release-notes-1-3-0.html)** | First Apache release. | November 2015
+**[1.3.0](release-notes-1-3-0.html)** | First Apache release. | Pending
**[1.1.0](release-notes-1-1-0.html)** | Major feature enhancements. Non-Apache release. | April 2015
**[1.0.1](release-notes-1-0-1.html)** | Defect repair. Non-Apache release. | February 2015
**[1.0.0](release-notes-1-0-0.html)** | Performance, stability, and new features. Non-Apache release. | January 2015
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/release.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release.md b/docs/src/site/markdown/release.md
index 8dad451..16e5391 100644
--- a/docs/src/site/markdown/release.md
+++ b/docs/src/site/markdown/release.md
@@ -19,7 +19,7 @@ This page describes how to create a Trafodion release. You have to be a Trafodio
## Create PGP Key
If you haven't done so already, then you need to create a PGP key so that you can sign the release. Please refer to: http://www.apache.org/dev/openpgp.html#generate-key.
-Please remember to store your private key is a secure place.
+Please remember to store your private key in a secure place.
**Example**
@@ -28,7 +28,7 @@ Please remember to store your private key is a secure place.
gpg -K (shows private key)
### Upload Public Key
-Upload your public key to a public key server. We recommend using http://pgp.mit.edu/keyserver.
+Upload your public key to a public key server. We recommend using https://pgp.mit.edu/.
**Example**
@@ -96,7 +96,7 @@ Trafodion uses git as its repository. When a new version is created, mark the r
Once completed, a new source tar file exist in the distribution directory.
### Create Artifact Checksums and Signatures
-**Assumption**: You've already created the signing key and registered it at the http://pgp.mit.edu/public repository.
+**Assumption**: You've already created the signing key and registered it at the https://pgp.mit.edu/ repository.
gpg --armor --output apache-trafodion-x.x.x-incubating-src.tar.gz.asc --detach-sig apache-trafodion-x.x.x-incubating-src.tar.gz
gpg --verify apache-trafodion-x.x.x-incubating-src.tar.gz.asc
@@ -127,7 +127,7 @@ Compare the two versions; for example, by using BCompare and the "Folder Compare
**Note:** The git version will have some additional git folders and the distribution directory.
## Verify Apache Requirements
-Verify checksums and signatures using the [Verify Signature](#Verify_Signature) instructions below.
+Verify checksums and signatures using the [Verify Signature](#Verify_Signatures) instructions below.
Ensure that the high-level directory contains valid version of:
@@ -185,7 +185,7 @@ Check signatures and checksums.
# Expect:
gpg: requesting key A44C5A05 from hkp server pgpkeys.mit.edu
gpg: /home/centos/.gnupg/trustdb.gpg: trustdb created
- gpg: key A44C5A05: public key "Roberta Marton (CODE SIGNING KEY) <rm...@apache.org>" imported
+ gpg: key A44C5A05: public key "Jane Doe (CODE SIGNING KEY) <jd...@apache.org>" imported
# Verify signature
gpg --verify apache-trafodion-x.x.x-incubating-src.tar.gz.asc
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/setup-build-environment.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/setup-build-environment.md b/docs/src/site/markdown/setup-build-environment.md
index 4479397..6de4cd5 100644
--- a/docs/src/site/markdown/setup-build-environment.md
+++ b/docs/src/site/markdown/setup-build-environment.md
@@ -12,7 +12,7 @@
limitations under the
License.
-->
-This page describes how you setup the Trafodion build environment.
+This page describes how you set up the Trafodion build environment.
# Supported Platforms
Red Hat or Centos 6.x (6.4 or later) versions are supported as development and production platforms.
@@ -75,7 +75,7 @@ Trafodion requires that several tools are installed in order to build. These too
Tool | Description
---------------------------------------|-----------------------------------------------------------------
**Bison** | General-purpose parser generator.
-**ICU** | Setup of C/C++ and Java libraries providing Unicode and Globalization support for software applications.
+**ICU** | Set of C/C++ and Java libraries providing Unicode and Globalization support for software applications.
**LLVM** | Collection of modular and reusable compiler and tool-chain technologies.
**Maven** | Build tool that is only installed if compatible version does not exist.
**MPICH** | An implementation of the Message Passing Interface (MPI) standard. For use in Trafodion, MPICH must be built to force sockets to be used in both internode and intranode message passing.
@@ -151,7 +151,7 @@ Please refer to [Build Tools Manual Installation](build-tools-manual.html).
## Verify Maven
Check that Maven is installed.
- maven --version
+ mvn --version
If Maven is not found, then you should add Maven to your **```PATH```** environmental variable in **```.bashrc```** or **```.profile```**.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/markdown/testing.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/testing.md b/docs/src/site/markdown/testing.md
index 0cfee3e..17895de 100644
--- a/docs/src/site/markdown/testing.md
+++ b/docs/src/site/markdown/testing.md
@@ -149,7 +149,7 @@ Further instructions for setting up and running the test can be found in source
# Functional Tests
## Phoenix
-The Phoenix tests provides basic functional tests for Trafodion. These tests were originally adapted from their counterpart at [salesforce.com](salesforce.com).
+The Phoenix tests provides basic functional tests for Trafodion. These tests were originally adapted from their counterpart at salesforce.com.
The tests are executed using Maven with a Python wrapper. You can run them the same way on your own workstation instance just like the way Jenkins runs them. Do the following:
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/731a5c73/docs/src/site/site.xml
----------------------------------------------------------------------
diff --git a/docs/src/site/site.xml b/docs/src/site/site.xml
index a057a09..f09afee 100644
--- a/docs/src/site/site.xml
+++ b/docs/src/site/site.xml
@@ -263,11 +263,13 @@
<item href="documentation.html" name="Documentation"/>
<item href="faq.html" name="FAQ"/>
<item href="release-notes.html" name="Release Notes"/>
+ <!--
<item href="http:divider" name=""/>
<item href="udf-tutorial.html" name="UDF API Tutorial"/>
+ -->
</menu>
<menu name="Features">
- <item href="architecture.html" name="Architecture Overview"/>
+ <item href="architecture-overview.html" name="Architecture Overview"/>
<item href="http:divider" name=""/>
<item href="https://blueprints.launchpad.net/trafodion/+spec/security-ansi-schemas" name="ANSI Schema Support"/>
<item href="https://blueprints.launchpad.net/trafodion/+spec/ustat-automation" name="Automated Update Statistics"/>
[2/8] incubator-trafodion git commit: [TRAFODION-1507] Added new
files.
Posted by db...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/release-notes-1-0-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-1-0-0.md b/docs/src/site/markdown/release-notes-1-0-0.md
new file mode 100644
index 0000000..71abf33
--- /dev/null
+++ b/docs/src/site/markdown/release-notes-1-0-0.md
@@ -0,0 +1,255 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+This is the source-only release of the Apache Trafodion (incubating) project. This release provides a number of new features and improvements across the project plus a large number of bug fixes.
+
+Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+
+# Supported Platforms
+The following platforms are supported in this release.
+
+<span>
+ <table>
+ <tr>
+ <td>**Operating Systems**</td>
+ <td>CentOS 6.5 -- 6.7</td>
+ </tr>
+ <tr>
+ <td>**Hadoop Distributions**</td>
+ <td>Cloudera CDH distribution 5.1 and Hortonworks distribution HDP 2.1</td>
+ </tr>
+ <tr>
+ <td>**Java Version**</td>
+ <td>JDK 1.7.0_67 or newer</td>
+ </tr>
+ <tr>
+ <td>**HBase Version**</td>
+ <td>HBase 0.98.x</td>
+ </tr>
+ </table>
+</span>
+
+# Enhancements
+
+This release contains the following new features.
+
+<span>
+ <table>
+ <tr>
+ <th>Category</th>
+ <th>Feature</th>
+ <th>Defect ID</th>
+ </tr>
+ <tr>
+ <td>**High Availability**</td>
+ <td>Production Ready:
+ <ul>
+ <li>Recovery from Trafodion infrastructure process failures. (Transaction Manager, Monitor)</li>
+ <li>Recovery from HBase Region Server failures.</li>
+ <li>Recovery from node failures.</li>
+ <li>Recovery from catastrophic system failures.</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Performance**</td>
+ <td>Production Ready:
+ <ul>
+ <li>[Automated Update Statistics](https://blueprints.launchpad.net/trafodion/+spec/ustat-automation) (initial, basic support).</li>
+ <li>Nested join enhancements.</li>
+ <li>Index support enhancements.</li>
+ <li>Scan performance.</li>
+ </ul>
+ Technology Preview:
+ <ul>
+ <li>[Multi-Temperature Data](https://cwiki.apache.org/confluence/display/TRAFODION/Cmp-divisioning) (Complete But Not Tested)</li>
+ </ul>
+ For more information about automated update statistics and index support enhancements, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Usability**</td>
+ <td>Technology Preview:
+ <ul>
+ <li>[Native HBase Tables](https://blueprints.launchpad.net/trafodion/+spec/access-external-hbase-tables) — Select/insert/update/delete data. (Complete But Not Tested)</li>
+ <li>[Sequence numbers](https://blueprints.launchpad.net/trafodion/+spec/sequence-numbers) and [IDENTITY column](https://blueprints.launchpad.net/trafodion/+spec/identity-column) (Complete But Not Tested)</li>
+ <li>Oracle compatibility features (disabled by default) (Complete But Not Tested)</li>
+ <li>[Large Objects (LOB)](https://blueprints.launchpad.net/trafodion/+spec/lob-support) support (Work in Progress)</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Database Movement and Connectivity**</td>
+ <td>Production Ready:
+ <ul>
+ <li>[Bulk Unload](https://blueprints.launchpad.net/trafodion/+spec/bulkunload)</li>
+ </ul>
+ Technology Preview:
+ <ul>
+ <li>[Backup/Restore](https://wiki.trafodion.org/wiki/index.php/Backup_and_Restore). (Complete But Not Tested)</li>
+ <li>Thread-Safe JDBC Type 2 Driver. (Complete But Not Tested)</li>
+ </ul>
+ For more information about the new UNLOAD statement, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Manageability**</td>
+ <td>Production Ready:
+ <ul>
+ <li>Visibility of SQL runtime statistics via the [Runtime Management System (RMS)](https://blueprints.launchpad.net/trafodion/+spec/enable-get-statistics-thru-rms).</li>
+ <li>Ability to [Cancel Queries](https://blueprints.launchpad.net/trafodion/+spec/sql-query-cancel) (DML statements only, not DDL, update statistics, and additional child query operations).</li>
+ <li>[Event Handling](https://wiki.trafodion.org/wiki/index.php/Trafodion_Manageability#Logging_Events) through UDFs and log4cpp.</li>
+ </ul>
+ Technology Preview:
+ <ul>
+ <li>Collection of session and query statistics in [Repository Tables](https://wiki.trafodion.org/wiki/index.php/Trafodion_Manageability) (disabled by default)</li>
+ </ul>
+ For more information about gathering SQL runtime statistics and canceling an executing query, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Security**</td>
+ <td>Production Ready:
+ <ul>
+ <li>[ANSI Schema Support](https://blueprints.launchpad.net/trafodion/+spec/security-ansi-schemas).</li>
+ <li>[Privilege checking for SPJs, UDFs, libraries, and sequence generators](https://blueprints.launchpad.net/trafodion/+spec/security-privilege-updates).</li>
+ <li>[Privilege checking for utilities](https://blueprints.launchpad.net/trafodion/+spec/security-privilege-updates).</li>
+ <li>[Metadata Query Invalidation](https://blueprints.launchpad.net/trafodion/+spec/ddl-query-invalidation) (that is, detection and propagation of privilege changes to SQL compilers).</li>
+ </ul>
+ For more information about ANSI schema support and privilege and authorization updates in this release, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Stability**</td>
+ <td>
+ <ul>
+ <li>Fixes for 85 defects.</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ </table>
+</span>
+
+# Fixes
+
+This release contains fixes to around 85 defects, including 25 critical defects, 54 high defects, and 10 medium and low defects. Those defects were filed through [Launchpad](https://launchpad.net/trafodion/+milestone/r1.1).
+
+# Known Issues
+
+## Getting TM error 97 when tables split or get moved
+
+**Defect:** [1274651](https://bugs.launchpad.net/trafodion/+bug/1274651)
+
+**Symptom:** HBase Region Splits, Load Balancing, and Error 97.
+
+**Cause:** As part of an HBase environment’s ongoing operations (and based on the policies configured for the HBase environment), an HBase region can either get split (into two daughter regions) or moved to a different region server. (Please see the blog: [http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/](http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/).) If that happens when a Trafodion transaction is active (and operates on rows within the region that is being split or load-balanced), then a subsequent transaction commit operation by the application might encounter an error 97. Please note that under such conditions the Trafodion Transaction Manager will abort the transaction and will preserve the integrity of the database.
+
+**Solution:** To minimize disruptions when this happens, we suggest that you use one or more of the following approaches:
+
+<ol>
+ <li>Enhance your JDBC application logic to retry when an error 97 is returned for a commit operation.</li>
+ <li>Update the HBase configuration to reduce the times when such disruptions happen. It involves updates to some properties that can be set in <code>hbase-site.xml</code> (or via the manageability interface of your Hadoop distribution).</li>
+ <ul>
+ <li>Set the maximum file size of an HBase Region to 100 GB. For example, set the value of the property <code>hbase.hregion.max.filesize</code> to <code>107374182400</code>.</li>
+ <li><p>Set the HBase region split policy to '<code>ConstantSizeRegionSplitPolicy</code>'. For example, set the value of the property <code>hbase.regionserver.region.split.policy</code> to <code>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</code>.</p>
+ <p><strong>NOTE</strong>: The split policy should already be set to '<code>onstantSizeRegionSplitPolicy</code>' by the Trafodion installer.</p>
+ <p><strong>Summary</strong></p>
+ <p>
+ <span>
+ <table>
+ <tr>
+ <th>Property</th>
+ <th>Value</th>
+ </tr>
+ <tr>
+ <td><code>hbase.hregion.max.filesize</code></td>
+ <td><code>107374182400</code></td>
+ </tr>
+ <tr>
+ <td><code>hbase.regionserver.region.split.policy</code></td>
+ <td><code>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</code></td>
+ </tr>
+ </table>
+ </span>
+ More information: [http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/](http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/)
+ </p>
+ </li>
+ </ul>
+ <li><p>Disable HBase Region Load Balancing. Use the HBase shell command balance_switch false to disable the movement of a region from one server to another.</p>
+ <p><strong>Example</strong></p>
+ <pre>
+hbase shell
+hbase(main):002:0> balance_switch false
+true -- Output will be the last setting of the balance_switch value
+0 row(s) in 0.0080 seconds
+ </pre>
+ </li>
+ <li>
+ Pre-split the table into multiple regions by using the <code>SALT USING n PARTITIONS</code> clause when creating the table. The number of partitions that you specify could be a function of the number of region servers present in the HBase cluster. Here is a simple example in which the table INVENTORY is pre-split into four regions when created:
+ <pre>
+CREATE TABLE INVENTORY
+ (
+ ITEM_ID INT UNSIGNED NO DEFAULT NOT NULL
+ , ITEM_TYPE INT UNSIGNED NO DEFAULT NOT NULL
+ , ITEM_COUNT INT UNSIGNED NO DEFAULT NOT NULL
+ , PRIMARY KEY (ITEM_ID ASC)
+ ) SALT USING 4 PARTITIONS
+ ; </pre>
+ </li>
+</ol>
+
+## EXECUTE.BATCH update creates core-file
+
+**Defect:** [1274962](https://bugs.launchpad.net/trafodion/+bug/1274962)
+
+**Symptom:** <code>EXECUTE.BATCH</code> hangs for a long time doing updates, and the update creates a core file.
+
+**Cause:** To be determined.
+
+**Solution:** Batch updates and ODBC row arrays do not currently work.
+
+## Random update statistics failures with HBase OutOfOrderScannerNextException
+
+**Defect:** [1391271](https://bugs.launchpad.net/trafodion/+bug/1391271)
+
+**Symptom:** While running update statistics commands, you see HBase OutOfOrderScannerNextException errors.
+
+**Cause:** The default <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values might be too low given the size of the tables. Sampling in update statistics is implemented using the HBase Random RowFilter. For very large tables with several billion rows, the sampling ratio required to get a sample of 1 million rows is very small. This can result in HBase client connection timeout errors since there may be no row returned by a RegionServer for an extended period of time.
+
+**Solution:** Increase the <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values. We have found that increasing those values to 600 seconds (10 minutes) might sometimes prevent many timeout-related errors. For more information, see the [HBase Configuration and Fine Tuning Recommendations](https://wiki.trafodion.org/wiki/index.php/Configuration#Recommendations).
+
+If increasing the <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values does not work, try increasing the chosen sampling size. Choose a sampling percentage higher than the default setting of 1 million rows for large tables. For example, suppose table T has one billion rows. The following <code>UPDATE STATISTICS</code> statement will sample a million rows, or approximately one-tenth of one percent of the total rows:
+
+ update statistics for table T on every column sample;
+
+To sample one percent of the rows, regardless of the table size, you must explicitly state the sampling rate as follows:
+
+ update statistics for table T on every column sample random 1 percent;
+
+## Following update statistics, stats do not take effect immediately
+
+**Defect:** [1409937](https://bugs.launchpad.net/trafodion/+bug/1409937)
+
+**Symptom:** Immediately following an update statistics operation, the generated query plan does not seem to reflect the existence of statistics. For example, in a session, you create, and populate a table and then run update statistics on the table, prepare a query, and exit. A serial plan is generated and the estimated cardinality is 100 for both tables. In a new session, you prepare the same query, and a parallel plan is generated where the estimated cardinality reflects the statistics.
+
+**Cause:** This is a day-one issue.
+
+**Solution:** Retry the query after two minutes. Set <code>CQD HIST_NO_STATS_REFRESH_INTERVAL</code> to '<code>0</code>'. Run an <code>UPDATE STATISTICS</code> statement. Perform DML operations in a different session.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/release-notes-1-0-1.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-1-0-1.md b/docs/src/site/markdown/release-notes-1-0-1.md
new file mode 100644
index 0000000..7ec9848
--- /dev/null
+++ b/docs/src/site/markdown/release-notes-1-0-1.md
@@ -0,0 +1,249 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+This is the source-only release of the Apache Trafodion (incubating) project. This release provides product-level collection of query statistics and critical bug fixes above [1.0.0](release-notes-1-0-0.html).
+
+Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+
+# Supported Platforms
+The following platforms are supported in this release.
+
+<span>
+ <table>
+ <tr>
+ <td>**Operating Systems**</td>
+ <td>CentOS 6.5 -- 6.7</td>
+ </tr>
+ <tr>
+ <td>**Hadoop Distributions**</td>
+ <td>Cloudera CDH distribution 5.1 and Hortonworks distribution HDP 2.1</td>
+ </tr>
+ <tr>
+ <td>**Java Version**</td>
+ <td>JDK 1.7.0_67 or newer</td>
+ </tr>
+ <tr>
+ <td>**HBase Version**</td>
+ <td>HBase 0.98.x</td>
+ </tr>
+ </table>
+</span>
+
+# Enhancements
+
+This release contains the following new features.
+
+<span>
+ <table>
+ <tr>
+ <th>Category</th>
+ <th>Feature</th>
+ <th>Defect ID</th>
+ </tr>
+ <tr>
+ <td>**High Availability**</td>
+ <td>Production Ready:
+ <ul>
+ <li>Recovery from Trafodion infrastructure process failures. (Transaction Manager, Monitor)</li>
+ <li>Recovery from HBase Region Server failures.</li>
+ <li>Recovery from node failures.</li>
+ <li>Recovery from catastrophic system failures.</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Performance**</td>
+ <td>Production Ready:
+ <ul>
+ <li>[Automated Update Statistics](https://blueprints.launchpad.net/trafodion/+spec/ustat-automation) (initial, basic support).</li>
+ <li>Nested join enhancements.</li>
+ <li>Index support enhancements.</li>
+ <li>Scan performance.</li>
+ </ul>
+ Technology Preview:
+ <ul>
+ <li>[Multi-Temperature Data](https://cwiki.apache.org/confluence/display/TRAFODION/Cmp-divisioning) (Complete But Not Tested)</li>
+ </ul>
+ For more information about automated update statistics and index support enhancements, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Usability**</td>
+ <td>Technology Preview:
+ <ul>
+ <li>[Native HBase Tables](https://blueprints.launchpad.net/trafodion/+spec/access-external-hbase-tables) — Select/insert/update/delete data. (Complete But Not Tested)</li>
+ <li>[Sequence numbers](https://blueprints.launchpad.net/trafodion/+spec/sequence-numbers) and [IDENTITY column](https://blueprints.launchpad.net/trafodion/+spec/identity-column) (Complete But Not Tested)</li>
+ <li>Oracle compatibility features (disabled by default) (Complete But Not Tested)</li>
+ <li>[Large Objects (LOB)](https://blueprints.launchpad.net/trafodion/+spec/lob-support) support (Work in Progress)</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Database Movement and Connectivity**</td>
+ <td>Production Ready:
+ <ul>
+ <li>[Bulk Unload](https://blueprints.launchpad.net/trafodion/+spec/bulkunload)</li>
+ </ul>
+ Technology Preview:
+ <ul>
+ <li>[Backup/Restore](https://wiki.trafodion.org/wiki/index.php/Backup_and_Restore). (Complete But Not Tested)</li>
+ <li>Thread-Safe JDBC Type 2 Driver. (Complete But Not Tested)</li>
+ </ul>
+ For more information about the new UNLOAD statement, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Manageability**</td>
+ <td>Production Ready:
+ <ul>
+ <li>Visibility of SQL runtime statistics via the [Runtime Management System (RMS)](https://blueprints.launchpad.net/trafodion/+spec/enable-get-statistics-thru-rms).</li>
+ <li>Ability to [Cancel Queries](https://blueprints.launchpad.net/trafodion/+spec/sql-query-cancel) (DML statements only, not DDL, update statistics, and additional child query operations).</li>
+ <li>[Event Handling](https://wiki.trafodion.org/wiki/index.php/Trafodion_Manageability#Logging_Events) through UDFs and log4cpp.</li>
+ <li>Collection of session and query statistics in [Repository Tables](https://wiki.trafodion.org/wiki/index.php/Trafodion_Manageability) (disabled by default)</li>
+ </ul>
+ For more information about gathering SQL runtime statistics and canceling an executing query, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Security**</td>
+ <td>Production Ready:
+ <ul>
+ <li>[ANSI Schema Support](https://blueprints.launchpad.net/trafodion/+spec/security-ansi-schemas).</li>
+ <li>[Privilege checking for SPJs, UDFs, libraries, and sequence generators](https://blueprints.launchpad.net/trafodion/+spec/security-privilege-updates).</li>
+ <li>[Privilege checking for utilities](https://blueprints.launchpad.net/trafodion/+spec/security-privilege-updates).</li>
+ <li>[Metadata Query Invalidation](https://blueprints.launchpad.net/trafodion/+spec/ddl-query-invalidation) (that is, detection and propagation of privilege changes to SQL compilers).</li>
+ </ul>
+ For more information about ANSI schema support and privilege and authorization updates in this release, see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).
+ </td>
+ <td></td>
+ </tr>
+ </table>
+</span>
+
+# Fixes
+
+This release contains fixes to around 85 defects, including 25 critical defects, 54 high defects, and 10 medium and low defects. Those defects were filed through [Launchpad](https://launchpad.net/trafodion/+milestone/r1.1).
+
+# Known Issues
+
+Release 1.0.1 provides fixes to these bugs:
+* **[1415165](https://bugs.launchpad.net/trafodion/+bug/1415165)**: MXOSRVR memory leak when stats are enabled
+* **[1421727](https://bugs.launchpad.net/trafodion/+bug/1421727)**: Default/aggregated stats type not publishing query stats
+* **[1416539](https://bugs.launchpad.net/trafodion/+bug/1416539)** Snapshot scan installer additions
+* **[1413418](https://bugs.launchpad.net/trafodion/+bug/1413418)**: Need metadata upgrade option in installer
+
+## Getting TM error 97 when tables split or get moved
+
+**Defect:** [1274651](https://bugs.launchpad.net/trafodion/+bug/1274651)
+
+**Symptom:** HBase Region Splits, Load Balancing, and Error 97.
+
+**Cause:** As part of an HBase environment’s ongoing operations (and based on the policies configured for the HBase environment), an HBase region can either get split (into two daughter regions) or moved to a different region server. (Please see the blog: [http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/](http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/).) If that happens when a Trafodion transaction is active (and operates on rows within the region that is being split or load-balanced), then a subsequent transaction commit operation by the application might encounter an error 97. Please note that under such conditions the Trafodion Transaction Manager will abort the transaction and will preserve the integrity of the database.
+
+**Solution:** To minimize disruptions when this happens, we suggest that you use one or more of the following approaches:
+
+<ol>
+ <li>Enhance your JDBC application logic to retry when an error 97 is returned for a commit operation.</li>
+ <li>Update the HBase configuration to reduce the times when such disruptions happen. It involves updates to some properties that can be set in <code>hbase-site.xml</code> (or via the manageability interface of your Hadoop distribution).</li>
+ <ul>
+ <li>Set the maximum file size of an HBase Region to 100 GB. For example, set the value of the property <code>hbase.hregion.max.filesize</code> to <code>107374182400</code>.</li>
+ <li><p>Set the HBase region split policy to '<code>ConstantSizeRegionSplitPolicy</code>'. For example, set the value of the property <code>hbase.regionserver.region.split.policy</code> to <code>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</code>.</p>
+ <p><strong>NOTE</strong>: The split policy should already be set to '<code>onstantSizeRegionSplitPolicy</code>' by the Trafodion installer.</p>
+ <p><strong>Summary</strong></p>
+ <p>
+ <span>
+ <table>
+ <tr>
+ <th>Property</th>
+ <th>Value</th>
+ </tr>
+ <tr>
+ <td><code>hbase.hregion.max.filesize</code></td>
+ <td><code>107374182400</code></td>
+ </tr>
+ <tr>
+ <td><code>hbase.regionserver.region.split.policy</code></td>
+ <td><code>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</code></td>
+ </tr>
+ </table>
+ </span>
+ More information: [http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/](http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/)
+ </p>
+ </li>
+ </ul>
+ <li><p>Disable HBase Region Load Balancing. Use the HBase shell command balance_switch false to disable the movement of a region from one server to another.</p>
+ <p><strong>Example</strong></p>
+ <pre>
+hbase shell
+hbase(main):002:0> balance_switch false
+true -- Output will be the last setting of the balance_switch value
+0 row(s) in 0.0080 seconds
+ </pre>
+ </li>
+ <li>
+ Pre-split the table into multiple regions by using the <code>SALT USING n PARTITIONS</code> clause when creating the table. The number of partitions that you specify could be a function of the number of region servers present in the HBase cluster. Here is a simple example in which the table INVENTORY is pre-split into four regions when created:
+ <pre>
+CREATE TABLE INVENTORY
+ (
+ ITEM_ID INT UNSIGNED NO DEFAULT NOT NULL
+ , ITEM_TYPE INT UNSIGNED NO DEFAULT NOT NULL
+ , ITEM_COUNT INT UNSIGNED NO DEFAULT NOT NULL
+ , PRIMARY KEY (ITEM_ID ASC)
+ ) SALT USING 4 PARTITIONS
+ ; </pre>
+ </li>
+</ol>
+
+## EXECUTE.BATCH update creates core-file
+
+**Defect:** [1274962](https://bugs.launchpad.net/trafodion/+bug/1274962)
+
+**Symptom:** <code>EXECUTE.BATCH</code> hangs for a long time doing updates, and the update creates a core file.
+
+**Cause:** To be determined.
+
+**Solution:** Batch updates and ODBC row arrays do not currently work.
+
+## Random update statistics failures with HBase OutOfOrderScannerNextException
+
+**Defect:** [1391271](https://bugs.launchpad.net/trafodion/+bug/1391271)
+
+**Symptom:** While running update statistics commands, you see HBase OutOfOrderScannerNextException errors.
+
+**Cause:** The default <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values might be too low given the size of the tables. Sampling in update statistics is implemented using the HBase Random RowFilter. For very large tables with several billion rows, the sampling ratio required to get a sample of 1 million rows is very small. This can result in HBase client connection timeout errors since there may be no row returned by a RegionServer for an extended period of time.
+
+**Solution:** Increase the <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values. We have found that increasing those values to 600 seconds (10 minutes) might sometimes prevent many timeout-related errors. For more information, see the [HBase Configuration and Fine Tuning Recommendations](https://wiki.trafodion.org/wiki/index.php/Configuration#Recommendations).
+
+If increasing the <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values does not work, try increasing the chosen sampling size. Choose a sampling percentage higher than the default setting of 1 million rows for large tables. For example, suppose table T has one billion rows. The following <code>UPDATE STATISTICS</code> statement will sample a million rows, or approximately one-tenth of one percent of the total rows:
+
+ update statistics for table T on every column sample;
+
+To sample one percent of the rows, regardless of the table size, you must explicitly state the sampling rate as follows:
+
+ update statistics for table T on every column sample random 1 percent;
+
+## Following update statistics, stats do not take effect immediately
+
+**Defect:** [1409937](https://bugs.launchpad.net/trafodion/+bug/1409937)
+
+**Symptom:** Immediately following an update statistics operation, the generated query plan does not seem to reflect the existence of statistics. For example, in a session, you create, and populate a table and then run update statistics on the table, prepare a query, and exit. A serial plan is generated and the estimated cardinality is 100 for both tables. In a new session, you prepare the same query, and a parallel plan is generated where the estimated cardinality reflects the statistics.
+
+**Cause:** This is a day-one issue.
+
+**Solution:** Retry the query after two minutes. Set <code>CQD HIST_NO_STATS_REFRESH_INTERVAL</code> to '<code>0</code>'. Run an <code>UPDATE STATISTICS</code> statement. Perform DML operations in a different session.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/release-notes-1-1-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-1-1-0.md b/docs/src/site/markdown/release-notes-1-1-0.md
new file mode 100644
index 0000000..af3a199
--- /dev/null
+++ b/docs/src/site/markdown/release-notes-1-1-0.md
@@ -0,0 +1,181 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+This is the source-only release of the Apache Trafodion (incubating) project. In addition to including a number of new features and improvements across the project, the focus of this release is to comply with Apache release guidelines.
+
+Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+
+# Supported Platforms
+The following platforms are supported in this release.
+
+<span>
+ <table>
+ <tr>
+ <td>**Operating Systems**</td>
+ <td>CentOS 6.5 -- 6.7</td>
+ </tr>
+ <tr>
+ <td>**Hadoop Distributions**</td>
+ <td>Cloudera distributions CDH 5.3.x<br />Hortonworks distribution HDP 2.2</td>
+ </tr>
+ <tr>
+ <td>**Java Version**</td>
+ <td>JDK 1.7.0_67 or newer</td>
+ </tr>
+ <tr>
+ <td>**HBase Version**</td>
+ <td>HBase 0.98.x</td>
+ </tr>
+ </table>
+</span>
+
+# Enhancements
+
+This release contains the following new features.
+
+<span>
+ <table>
+ <tr>
+ <th>Category</th>
+ <th>Feature</th>
+ <th>Defect ID</th>
+ </tr>
+ <tr>
+ <td>**Marketability, Infrastructure, and Scalability**</td>
+ <td>
+ <ul>
+ <li>Critical and high defect repairs.</li>
+ <li>Infrastructure refresh, including support for HDP 2.2 and CDH 5.3</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Performance**</td>
+ <td>
+ <ul>
+ <li>Query plan quality improvements identified by PoC/benchmarks, such as costing changes to help generate MDAM plans when appropriate.</li>
+ <li>Performance and hardening improvements to user-defined routines (UDRs) (that is, stored procedures and C scalar user-defined functions (UDFs)).</li>
+ <li>[Hybrid Query Cache](https://blueprints.launchpad.net/trafodion/+spec/hybrid-query-cache), which improves transaction performance and efficiency by moving the compiler’s SQL similarity detection check to the parser phase. Query caching allows reuse of pre-existing optimized SQL execution plans thereby eliminating costly compile and optimization overhead.</li>
+ <li>[Skew Buster](https://blueprints.launchpad.net/trafodion/+spec/skew-buster), a patented feature in Trafodion that can recognize situations where data is skewed in intermediate stages of a query and adjust the query plan and execution time redistribution of intermediate data to ensure that all data is evenly distributed over all processing nodes.</li>
+ <li>[Immediate Update Statistics](https://wiki.trafodion.org/wiki/index.php/Creating_Statistics_During_Bulk_Load) for the entire table based on the sample taken during fast data loading. (Technology Preview--Complete But Not Fully Tested)</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**High Availability (HA) and Distributed Transaction Management (DTM)**</td>
+ <td>
+ <ul>
+ <li>Transaction management efficiency and performance enhancements.</li>
+ <li>Improvement of overall cluster HA now that the Trafodion Transaction Manager (TM) process is a persistent process, which eliminates the triggering of a node failure if the TM fails.</li>
+ <li>DTM local transaction support to minimize the overhead of transactions by eliminating interactions with the TM process when the scope is local to the client that began the transaction. (Technology Preview--Work in Progress)</li>
+ <li>Ability to run DDL statements in transactions, thus providing database consistency protection for DDL operations. (Technology Preview--Work in Progress)</li>
+ <li>Stateless/Stateful Concurrency Control (SSCC), which ensures that transactions prevent data contention anomalies that can corrupt the consistency of a database. It works by preventing user transactions that interfere with each other’s data. SSCC is an extension of the Snapshot Isolation (SI) algorithm. SI prevents the majority of anomalies associated with data corruption and provides superior isolation to Multi-Version Concurrency Control (MVCC), which is used by DTM today. (Technology Preview--Work in Progress)</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Usability**</td>
+ <td>
+ <ul>
+ <li>Production-ready version of the [Backup/Restore Utility](https://wiki.trafodion.org/wiki/index.php/Backup_and_Restore), which allows you to backup and restore a Trafodion database while it is offline.</li>
+ <li>Parallel data loader/extractor tool called "[odb](docs/Trafodion_odb_User_Guide.pdf)" for [trickle data loading and extraction](https://wiki.trafodion.org/wiki/index.php/Data_Loading#Trickle_Loading_Data_Into_Trafodion_Tables) to and from Trafodion tables.</li>
+ <li>[Metadata Cleanup Utility](https://wiki.trafodion.org/wiki/index.php/Metadata_Cleanup), which is used to cleanup metadata tables after a failed DDL statement (Technology Preview--Complete But Not Tested)</li>
+ <li>[Table-Mapping User-Defined Functions (TMUDF)](https://wiki.trafodion.org/wiki/index.php/Tutorial:_The_object-oriented_UDF_interface) written in C++. (Technology Preview--Complete But Not Tested)</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Manageability**</td>
+ <td>
+ <ul>
+ <li>Support for HP Data Services Manager (HP DSM), a unified, browser-based tool for management of Hadoop, Vertica, and now Trafodion data services. **NOTE**: The version of HP DSM that integrates with Trafodion is not yet available.</li>
+ <li>Stability and overhead optimizations to reduce the overhead of capturing and maintaining query performance information (in repository tables).</li>
+ <li>Query cancel for DDL, update statistics, and additional child query operations. For details, see the CONTROL QUERY CANCEL statement in the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Security**</td>
+ <td>
+ <ul>
+ <li>Security subsystem hardening improvements including performance and QA testing.</li>
+ <li>Security enhancements for the Trafodion metadata, data loader, and Data Connectivity Services (DCS).</li>
+ <li>Upgrade authorization.</li>
+ <li>Ability to grant privileges on behalf of a role using the GRANTED BY clause. For details, see the GRANT statements in the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manaual.pdf).</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Installer**</td>
+ <td>
+ <ul>
+ <li>Prompts to configure and enable security.</li>
+ <li>Support for the latest distributions, HDP 2.2 and CDH 5.3.</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ </table>
+</span>
+
+# Fixes
+
+This release contains fixes to around 96 defects, including 17 critical defects, 53 high defects, 20 medium defects, and two low defects. Those defects were filed through [Launchpad](https://launchpad.net/trafodion/+milestone/r1.1).
+
+# Known Issues
+
+## EXECUTE.BATCH update creates core-file
+
+**Defect:** [1274962](https://bugs.launchpad.net/trafodion/+bug/1274962)
+
+**Symptom:** EXECUTE.BATCH hangs for a long time doing updates, and the update creates a core file.
+
+**Cause:** To be determined.
+
+**Solution:** Batch updates and ODBC row arrays do not currently work.
+
+## Random update statistics failures with HBase OutOfOrderScannerNextException
+
+**Defect:** [1391271](https://bugs.launchpad.net/trafodion/+bug/1391271)
+
+**Symptom:** While running update statistics commands, you see HBase <code>OutOfOrderScannerNextException</code> errors.
+
+**Cause:** The default <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values might be too low given the size of the tables. Sampling in update statistics is implemented using the HBase Random RowFilter. For very large tables with several billion rows, the sampling ratio required to get a sample of 1 million rows is very small. This can result in HBase client connection timeout errors since there may be no row returned by a RegionServer for an extended period of time.
+
+**Solution:** Increase the <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values. We have found that increasing those values to 600 seconds (10 minutes) might sometimes prevent many timeout-related errors. For more information, see the [HBase Configuration and Fine Tuning Recommendations](https://wiki.trafodion.org/wiki/index.php/Configuration#Recommendations).
+
+If increasing the <code>hbase.rpc.timeout</code> and <code>hbase.client.scanner.timeout.period</code> values does not work, try increasing the chosen sampling size. Choose a sampling percentage higher than the default setting of 1 million rows for large tables. For example, suppose table T has one billion rows. The following <code>UPDATE STATISTICS</code> statement will sample a million rows, or approximately one-tenth of one percent of the total rows:
+
+ update statistics for table T on every column sample;
+
+To sample one percent of the rows, regardless of the table size, you must explicitly state the sampling rate as follows:
+
+ update statistics for table T on every column sample random 1 percent;
+
+## Following update statistics, stats do not take effect immediately
+
+**Defect:** [1409937](https://bugs.launchpad.net/trafodion/+bug/1409937)
+
+**Symptom:** Immediately following an update statistics operation, the generated query plan does not seem to reflect the existence of statistics. For example, in a session, you create, and populate a table and then run update statistics on the table, prepare a query, and exit. A serial plan is generated and the estimated cardinality is 100 for both tables. In a new session, you prepare the same query, and a parallel plan is generated where the estimated cardinality reflects the statistics.
+
+**Cause:** This is a day-one issue.
+
+**Solution:** Retry the query after two minutes. Set <code>CQD HIST_NO_STATS_REFRESH_INTERVAL</code> to <code>'0'</code>. Run an <code>UPDATE STATISTICS</code> statement. Perform DML operations in a different session.
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/release.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release.md b/docs/src/site/markdown/release.md
new file mode 100644
index 0000000..8dad451
--- /dev/null
+++ b/docs/src/site/markdown/release.md
@@ -0,0 +1,225 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to create a Trafodion release. You have to be a Trafodion committer to use these instructions.
+
+# Prerequisites
+
+## Create PGP Key
+If you haven't done so already, then you need to create a PGP key so that you can sign the release. Please refer to: http://www.apache.org/dev/openpgp.html#generate-key.
+
+Please remember to store your private key is a secure place.
+
+**Example**
+
+ gpg --gen-key (verify that sha1 is avoided (last on list – see above web site)
+ gpg -k (shows public key)
+ gpg -K (shows private key)
+
+### Upload Public Key
+Upload your public key to a public key server. We recommend using http://pgp.mit.edu/keyserver.
+
+**Example**
+
+ gpg --send-keys <keyID> --keyserver pgp.mit.edu
+
+### Create Revocation Certificate
+Create a revocation certification using the instructions at: http://www.apache.org/dev/openpgp.html#revocation-certs.
+
+Please remember to store it in a secure place separate from your PGP keys.
+
+**Example**
+
+ gpg --output revoke-<keyD>.asc --armor --gen-revoke <keyID>
+
+# Add PGP to KEYS File
+Do the following:
+
+ svn co https://dist.apache.org/repos/dist/release/incubator/trafodion traf_release
+ cd traf_release
+ gpg --list-sigs <keyID> >> KEYS
+ gpg -armor –export <keyID>
+ svn commit –m “added new public key to KEYS file“
+
+# Prepare Artifacts
+## Prepare New Release
+
+1. Send a message out to the community indicating that a new release is being planned. In this message, indicate what is planned for the release and when the release is scheduled.
+2. Give contributors enough time to assimilate this information so they can make plans to deliver their changes. Recommend giving the community several weeks notice.
+3. Review open issues and planned features; determine what JIRA's should be included in the release.
+
+## Verify Release Requirements
+You need to ensure that:
+
+* A DISCLAIMER file exists in the top level directory containing correct information. Please refer to: http://incubator.apache.org/guides/branding.html#disclaimers.
+* NOTICE and LICENSE files exist in the top level directory which includes all third party licenses used in the product. Please refer to: http://www.apache.org/dev/licensing-howto.html.
+* A README file exists and is up to date in the top level directory describing the release.
+* The source release contains source code only, no binaries.
+* The provenance of all source files is clear.
+* All source files have Apache license headers, where possible. Where not possible, then the exceptions are written up in the RAT_README file located in the top level directory.
+* RAT report is clean.
+* Copyright dates are current.
+* Build instructions are provided and can be run successfully.
+* Test instructions are provided and can be run successfully.
+
+## Create Release Branch
+Prior to releasing, send a message to the community indicating that a new release is imminent and that a new branch will be created to build the artifacts.
+
+After the new release branch is created, send another message to the community indicating that the branch is available and the deliveries will be monitored. Allow deliveries on the main branch to continue.
+
+Verify that all required changes have been delivered.
+
+## Create Artifacts
+Trafodion uses git as its repository. When a new version is created, mark the repository with the tag to make sure it source tar can be recreated.
+
+### Create Tag
+
+**Example: Release x.x.x and release candidate 1 (rc1)**
+
+ git checkout -b tagx.x.x <release branch name>
+ git tag -a x.x.xrc1
+ git show x.x.xrc1
+ git push apache x.x.xrc1
+ git tag
+
+Once completed, a new source tar file exist in the distribution directory.
+
+### Create Artifact Checksums and Signatures
+**Assumption**: You've already created the signing key and registered it at the http://pgp.mit.edu/public repository.
+
+ gpg --armor --output apache-trafodion-x.x.x-incubating-src.tar.gz.asc --detach-sig apache-trafodion-x.x.x-incubating-src.tar.gz
+ gpg --verify apache-trafodion-x.x.x-incubating-src.tar.gz.asc
+ md5sum apache-trafodion-x.x.x-incubating-src.tar.gz > apache-trafodion-x.x.x-incubating-src.tar.gz.md5
+ sha1sum apache-trafodion-x.x.x-incubating-src.tar.gz > apache-trafodion-x.x.x-incubating-src.tar.gz.sha
+
+# Test Artifacts
+
+## Build and Test Source tar File
+Build and test the source tar file using the [Build Trafodion](build.html) instructions. You should perform this test on the following environments:
+
+* Test build on a fresh VM.
+* Test build using the tagged version from git
+
+## Compare Tagged Version with Source tar File
+Compare the code from the source tar file with the tagged version to make sure they match. The follow example assumes that the branch artifacts contains the release candidates.
+
+ mkdir traf_test
+ cd traf_test
+ cp <git dir>/incubator-trafodion/distribution/* .
+ tar zxf apache-trafodion-x.x.x-incubating-src.tar.gz
+
+Compare the two versions; for example, by using BCompare and the "Folder Compare Report" feature:
+
+ old: traf_test/incubator-trafodion
+ new: <git dir>/incubator-trafodion
+
+**Note:** The git version will have some additional git folders and the distribution directory.
+
+## Verify Apache Requirements
+Verify checksums and signatures using the [Verify Signature](#Verify_Signature) instructions below.
+
+Ensure that the high-level directory contains valid version of:
+
+* **```DISCLAIMER.txt```**
+* **```LICENSE.txt```**
+* **```NOTICE.txt```**
+* **```RAT_README.txt```**
+* **```README.txt```**
+
+# Stage Artifacts
+Once all the artifacts have been created and tested, then it's time to stage them. Upload the artifacts to the https://dist.apache.org/repos/dist/dev/incubator/trafodion directory.
+
+1. Make sure **```svn```** exists. (It can be downloaded using **```yum```**.)
+ * **```which svn```**
+ * **```svn --version```** (version 1.6.11 works)
+2. Create a directory to store the **```svn```** repositoy
+3. Checkout source code. This creates a directory called incubator.
+ * **```svn co https://dist.apache.org/repos/dist/dev/incubator```**
+4. **```cd trafodion```**
+5. Create a new directory for the release: **```mkdir apache-trafodion-x.x.x-incubating```**
+6. **```cd <apache-trafodion-x.x.x-incubating>```**
+7. Copy the four files to the incubating directory.
+8. Ensure that you do an **```svn add```** for the new directory and all four files
+9. Ask for a review of the changes
+10. Commit your changes
+ * **```svn status```**
+ * **```svn commit –m "message…"```**
+ * Go to https://dist.apache.org/repos/dist/dev/incubator to see if your changes were committed
+
+# Verification
+All artifacts have been uploaded to the staging area.
+
+## Verify Signatures
+Download all the artifacts from the staging area including:
+
+ apache-trafodion-x.x.x-incubating-src.tar.gz
+ apache-trafodion-x.x.x-incubating-src.tar.gz.asc
+ apache-trafodion-x.x.x-incubating-src.tar.gz.md5
+ apache-trafodion-x.x.x-incubating-src.tar.gz.sha
+
+Check signatures and checksums.
+
+**```apache-trafodion-x.x.x-incubating-src.tar.gz.asc```**
+
+ # View public key
+ gpg apache-trafodion-x.x.x-incubating-src.tar.gz.asc
+
+ # Expect
+ gpg: Signature made Tue 03 Nov 2015 12:59:10 AM UTC using RSA key ID A44C5A05
+ gpg: Can't check signature: No public key
+
+ # Extract public key from key ID returned above
+ gpg --keyserver pgpkeys.mit.edu --recv-key A44C5A05
+
+ # Expect:
+ gpg: requesting key A44C5A05 from hkp server pgpkeys.mit.edu
+ gpg: /home/centos/.gnupg/trustdb.gpg: trustdb created
+ gpg: key A44C5A05: public key "Roberta Marton (CODE SIGNING KEY) <rm...@apache.org>" imported
+
+ # Verify signature
+ gpg --verify apache-trafodion-x.x.x-incubating-src.tar.gz.asc
+ # Expect:
+ gpg: Signature made <date> using RSA key ID A44C5A05
+ gpg: Good signature from "Roberta Marton (CODE SIGNING KEY) <rm...@apache.org>"
+ gpg: WARNING: This key is not certified with a trusted signature!
+ gpg: There is no indication that the signature belongs to the owner.
+
+ **```apache-trafodion-x.x.x-incugating-src.tar.gz.md5```**
+
+ md5sum -c apache-trafodion-x.x.x-incubating-src.tar.gz.md5
+
+ # Expect:
+ apache-trafodion-x.x.x-incubating-src.tar.gz: OK
+
+**```apache-trafodion-x.x.x-incubating-x.x.x-incubating-src.tar.gz.sha```**
+
+ sha1sum -c apache-trafodion-x.x.x-incubating-src.tar.gz.sha
+
+ # Expect:
+ apache-trafodion-x.x.x-incubating-src.tar.gz: OK
+
+## Verify Apache Requirements
+Ensure that the high-level directory contains valid version of:
+
+* **```DISCLAIMER.txt```**
+* **```LICENSE.txt```**
+* **```NOTICE.txt```**
+* **```RAT_README.txt```**
+* **```README.txt```**
+
+Next, run **```rat```** to make sure all files have Apache copyrights.
+
+# Complete Release
+
+To be completed.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/roadmap.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/roadmap.md b/docs/src/site/markdown/roadmap.md
new file mode 100644
index 0000000..125a4c2
--- /dev/null
+++ b/docs/src/site/markdown/roadmap.md
@@ -0,0 +1,15 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page will provide information about future Trafodion releases and their planned content.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/setup-build-environment.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/setup-build-environment.md b/docs/src/site/markdown/setup-build-environment.md
new file mode 100644
index 0000000..4479397
--- /dev/null
+++ b/docs/src/site/markdown/setup-build-environment.md
@@ -0,0 +1,160 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how you setup the Trafodion build environment.
+
+# Supported Platforms
+Red Hat or Centos 6.x (6.4 or later) versions are supported as development and production platforms.
+
+# Install Required Packages
+You need to install the following packages before you can build Trafodion.
+
+ sudo yum install epel-release
+
+ sudo yum install alsa-lib-devel ant ant-nodeps boost-devel cmake \
+ device-mapper-multipath dhcp flex gcc-c++ gd git glibc-devel \
+ glibc-devel.i686 graphviz-perl gzip java-1.7.0-openjdk-devel \
+ libX11-devel libXau-devel libaio-devel \
+ libcurl-devel libibcm.i686 libibumad-devel libibumad-devel.i686 \
+ libiodbc libiodbc-devel librdmacm-devel librdmacm-devel.i686 \
+ libxml2-devel log4cxx log4cxx-devel lua-devel lzo-minilzo \
+ net-snmp-devel net-snmp-perl openldap-clients openldap-devel \
+ openldap-devel.i686 openmotif openssl-devel openssl-devel.i686 \
+ openssl-static perl-Config-IniFiles perl-Config-Tiny \
+ perl-DBD-SQLite perl-Expect perl-IO-Tty perl-Math-Calc-Units \
+ perl-Params-Validate perl-Parse-RecDescent perl-TermReadKey \
+ perl-Time-HiRes protobuf-compiler protobuf-devel python-qpid \
+ python-qpid-qmf qpid-cpp-client \
+ qpid-cpp-client-ssl qpid-cpp-server qpid-cpp-server-ssl \
+ qpid-qmf qpid-tools readline-devel saslwrapper sqlite-devel \
+ unixODBC unixODBC-devel uuid-perl wget xerces-c-devel xinetd
+
+# Verify Java Version
+The Java version must be 1.7.x. Check as following:
+
+ $ java -version
+ java version "1.7.0_85"
+ OpenJDK Runtime Environment (rhel-2.6.1.3.el6_6-x86_64 u85-b01)
+ OpenJDK 64-Bit Server VM (build 24.85-b03, mixed mode)
+
+Ensure that the Java environment exists and points to your JDK installation. By default Java is located in **```/usr/lib/java-\<version\>```**.
+
+ $ echo $JAVA_HOME
+ $ export JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk.x86_64
+
+# Download and Install Source
+The Trafodion source code contains tools that help you set up the build environment.
+## Git
+Please refer to [Making Changes](develop.html#making_changes) on the [Develop](develop.html) page.
+
+## tar file
+The source code for Apache Trafodion can be downloaded from [Apache Trafodion Incubator Release](https://dist.apache.org/repos/dist/release/incubator) as a tar file.
+
+* Download the source tar file to your **```<trafodion download directory>```**.
+* Check the tar file validity by checking signatures, please refer to [Verify Signatures](release.html#Verify_Signatures). The Trafodion releases have been signed using The GNU Privacy Guard.
+
+**Unpack the tar file**
+
+ cd <trafodion download directory>
+ tar -xzf <tar file>
+
+# Install Build Tools
+Trafodion requires that several tools are installed in order to build. These tools are:
+
+Tool | Description
+---------------------------------------|-----------------------------------------------------------------
+**Bison** | General-purpose parser generator.
+**ICU** | Setup of C/C++ and Java libraries providing Unicode and Globalization support for software applications.
+**LLVM** | Collection of modular and reusable compiler and tool-chain technologies.
+**Maven** | Build tool that is only installed if compatible version does not exist.
+**MPICH** | An implementation of the Message Passing Interface (MPI) standard. For use in Trafodion, MPICH must be built to force sockets to be used in both internode and intranode message passing.
+**Thrift** | Communications and data serialization tool.
+**Udis86** | Minimalistic disassembler library (libudis86) for the x86 class of instruction set architectures.
+**Zookeeper** | Coordination service for distributed applications. It exposes common services such as naming, configuration management, synchronization, and group services.
+
+You can perform the required installation using the Trafodion **```traf_tools_setup.sh```** script or by installing each tool manually.
+
+## ```traf_tools_setup.sh```
+**```traf_tools_setup.sh```** is a script that uses **```wget```** to download the appropriate tar file, build, and install the required tool into a directory of your choice for each tool required tools.
+
+The advantage of this method is that all the correct tools are downloaded and built in a single directory. Before building, a single environment variable needs to be set: **```TOOLSDIR```**.
+
+<div class="alert alert-dismissible alert-info">
+ <button type="button" class="close" data-dismiss="alert">&close;</button>
+ <p style="color:black"><strong>Note</strong></p>
+ <p style="color:black">You may want to modify <strong><code>traf_tools_setup.sh</code></strong> for your specific environment. Example: if you already have Zoopkeeper installed, you may not want to re-install it.</p>
+ <p style="color:black">You may need root or sudo access to installs the tools in desired locations.</p>
+ <p style="color:black">In the sections below, <strong><code>incubator-trafodion</code></strong> represents the root directory where you installed the Trafodion source.</p>
+</div>
+
+**Usage**
+
+ cd <Trafodion source directory>/install
+ ./traf_tools_setup.sh -h
+ Usage: ./traf_tools_setup.sh -d <downloaddir> -i <installdir>
+ -d <downloaddir> - location of download directory
+ -i <installdir> - location of install directory
+ -h - help
+ example: traf_tools_setup.sh -d /home/userx/download -i /home/userx/tools
+
+Run **```traf_tools_setup.sh```** to install all dependent tools.
+
+**Example**
+
+ $ mkdir ~/download
+ $ ./traf_tools_setup.sh -d ~/download -i ~/tools
+ INFO: Starting tools build on Fri Nov 6 21:33:53 PST 2015
+ Tools install directory /home/centos/tools does not exist, do you want to to create it? y/n : y
+ INFO: Created directory /home/centos/tools
+ INFO: Tar download location: /home/centos/download
+ INFO: Tool install directory location: /home/centos/tools
+ INFO: LogFile location: /home/centos/incubator-trafodion/install/traf_tools_setup.log
+ ***********************************************************
+ INFO: Installing MPI on Fri Nov 6 21:34:00 PST 2015
+ INFO: downloaded tar file: mpich-3.0.4.tar.gz
+ .
+ .
+ .
+ INFO: downloaded tar file: apache-maven-3.3.3-bin.tar.gz
+ INFO: Maven installation complete
+ ***********************************************************
+ INFO: Completed tools build on Fri Nov 6 22:23:22 PST 2015
+ INFO: List of tools directory:
+ apache-maven-3.3.3
+ bison_3_linux
+ dest-llvm-3.2
+ dest-mpich-3.0.4
+ icu4.4
+ thrift-0.9.0
+ udis86-1.7.2
+ zookeeper-3.4.5
+
+Export **```TOOLSDIR```** in **```.bashrc```** or **```.profile```**.
+
+ export TOOLSDIR=~/tools
+
+## Manual Installation
+Please refer to [Build Tools Manual Installation](build-tools-manual.html).
+
+# Verify Build Environment
+## Verify Maven
+Check that Maven is installed.
+
+ maven --version
+
+If Maven is not found, then you should add Maven to your **```PATH```** environmental variable in **```.bashrc```** or **```.profile```**.
+
+ PATH=$PATH:<tool installation directory>/apache-maven-3.3.3/bin
+
+At this point, your build environment has been set up. You should now be able to [Build Trafodion](build.html).
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/testing.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/testing.md b/docs/src/site/markdown/testing.md
new file mode 100644
index 0000000..0cfee3e
--- /dev/null
+++ b/docs/src/site/markdown/testing.md
@@ -0,0 +1,179 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+This page describes the Trafodion test suites and their usage.
+
+# Component Tests
+Trafodion comes with several component-specific testing libraries.
+
+## SQL Core
+The SQL core components are written in a combination of C++ and Java.
+
+You should ensure that the current set of regression tests pass each time you add or modify a SQL feature.
+
+If adding a new feature, then check that it is either covered by an existing regression test or add a new test to an existing test suite.
+
+### Test Suites
+**Location**: ```core/sql/regress```
+
+Directory | Usage
+-----------------------|---------------------------------------------------------------------------
+**```catman1```** | Tests the Catalog Manager.
+**```charsets```** | Tests Character Sets.
+**```compGeneral```** | Compiler test suite; tests optimizer-specific features.
+**```core```** | Tests a subset/sample of all features from all the test suites.
+**```executor```** | Tests the SQL Executor.
+**```fullstack2```** | Similar to core but a very limited subset.
+**```hive```** | Tests HDFS access to Hive tables.
+**```newregr```** | Unused/Saved repository for some unpublished features. These are not run.
+**```qat```** | Tests basic DDL and DML syntax.
+**```seabase```** | Tests JNI interface to HBase.
+**```tools```** | Regression driver scripts and general regression scripts.
+**```udr```** | Tests the User Defined Routines (UDR) and TMUDF functionality.
+
+### Check Test Results
+On completion, the test run prints out a test summary. All tests should pass, or pass with known diffs.
+
+Test results are written to the **```runregr-sb.log```** file in each component's directory. Therefore, you can check the test results after the fact as follows:
+
+ cd $MY_SQROOT/rundir
+ grep FAIL */runregr-sb.log
+
+A successful test run shows no failures.
+
+### Run Full Test Suite
+This suite tests:
+
+* SQL Compiler
+* SQL Executor
+* Transactions
+* Foundation
+
+
+Do the following:
+
+ cd $MY_SQHOME
+ . ./sqenv.sh
+ cd $MY_SQROOT/../sql/regress
+ tools/runallsb
+
+### Run Individual Test Suites
+You can select individual test suites as follows:
+
+ cd $MY_SQHOME
+ . ./sqenv.sh
+ cd $MY_SQROOT/../sql/regress
+ tools/runallsb <suite1> <suite2>
+
+### Running an Individual Test
+#### If You've Already Run the Test Suite
+If you have already run the suite once, then you will have all your directories set up and you can run one test as follows:
+
+ cd $MY_SQROOT/../sql/regress/<suite>
+ # You can add the following two exports to .bashrc or .profile for convenience
+ export rundir=$MY_SQROOT/rundir
+ export scriptsdir=$MY_SQROOT/../sql/regress
+ # run the test
+ cd $rundir/<suite>
+ $scriptsdir/<suite>/runregr -sb <test>
+
+**Example**
+
+ cd $rundir/executor
+ $scriptsdir/executor/runregr -sb TEST130
+
+#### If You've Not Run the Test Suite
+If you have not run any regression suites so far, then you will not have the required sub directories set up. You manually create them for each suite you want to run.
+
+ cd $MY_SQROOT/../sql/regress/<suite>
+ # You can add the following two exports to .bashrc or .profile for convenience
+ export rundir=$MY_SQROOT/rundir
+ export scriptsdir=$MY_SQROOT/../sql/regress
+ mkdir $rundir
+ cd $rundir
+ # <suitename> should match the name of each directory in $scriptsdir
+ mkdir <suitename>
+ # run the test
+ cd $rundir/<suite>
+ $scriptsdir/<suite>/runregr -sb <test>
+
+### Detecting Failures
+If you see failures in any of your tests, you want to try running that suite or test individually as detailed above.
+
+Open up the DIFF file and correlate them to the LOG and EXPECTED files.
+
+* DIFF files are in **```$rundir/<suite name>```**.
+* LOG files are in **```$rundir/<suite name>```**.
+* EXPECTED files are in **```$scriptsdir/<suite name>```**.
+
+To narrow down the failure, open up the test file (for example: **```TEST130```**) in **```$scriptsdir/executor```**.
+
+Recreate the problem with a smaller set of SQL commands and create a script to run from **```sqlci```**. If it's an issue that can be recreated only by running the whole suite, you can add a line to the test just before the command that fails to include a **```wait```** or a **```sleep```** **```sh sleep 60```** will make the test pause and give you time to attach the **```sqlci```** process to the debugger. (You can find the PID of the **```sqlci```** process using **```sqps```** on the command line)
+
+Introducing a **```wait```** in the test will wait forever until you enter a character. This is another way to make the test pause to attach the debugger to the **```sqlci```** process.
+
+### Modifying an Existing Test
+If you would like to add coverage for your new change, you can modify an existing test.
+
+Run the test after your modifications. If you are satisfied with your results, you need to modify the **```EXPECTED<test number>```** file to reflect your new change. The standard way to do it is to copy the **```LOG<test number>```** file to **```EXPECTED<test number>```** file.
+
+## Database Connectivity Services (DCS)
+The DCS test suite is organized per the Maven standard.
+
+## JDBC T4
+The code is written in Java, and is built and unit tested using Maven. The test suite organization and use follow Maven standards.
+
+Instructions for setting up and running the test can be found in source tree at **```dcs/src/test/jdbc_test```**.
+
+## ODBC Tests
+The code is written for the Python 2.7 [```unittest```](https://docs.python.org/2/library/unittest.html) framework.
+
+It is run via the **```Testr```** and **```Tox```**.
+
+ cd dcs/src/test/pytests
+ ./config.sh -d <host>t:<port> -t <Location of your Linux ODBC driver tar file>
+ tox -e py27
+
+Further instructions for setting up and running the test can be found in source tree at **```dcs/src/test/pytests```**.
+
+# Functional Tests
+
+## Phoenix
+The Phoenix tests provides basic functional tests for Trafodion. These tests were originally adapted from their counterpart at [salesforce.com](salesforce.com).
+
+The tests are executed using Maven with a Python wrapper. You can run them the same way on your own workstation instance just like the way Jenkins runs them. Do the following:
+
+<!-- This part is done in raw HTML because it's too complex to do this level of formatting in markdown. -->
+<ol>
+ <li>Prior to running Phoenix tests, you need to bring up your Trafodion instance and DCS. You need to configure at least 2-4 servers for DCS. The tests need at least two mxosrvrs as they make two connections at any given time. We recommend configuring DCS with four mxosrvrs since we have seen situations that mxosrvrs do not get released in time for the next connection if there are only two mxosrvrs.</li>
+ <li><p>Run the Phoenix tests from source tree</p>
+ <p style="text-indent=20px">
+ <pre>
+cd tests/phx
+phoenix_test.py --target=<host>:<port> --user=dontcare --pw=dontcare --targettype=TR --javahome=<jdk> --jdbccp=<jdir>/jdbcT4.jar</pre>
+ </p>
+ <p style="text-indent=20px">
+ <ul>
+ <li><strong><host></strong>: your workstation name or IP address.</li>
+ <li><strong><port></strong>: your DCS master port number.</li>
+ <li><strong><jdk></strong>: the directory containing the jdk1.7.0_21_64 or later version of the JDK.</li>
+ <li><strong><jdir></strong>: the directory containing your JDBC T4 jar file. (export/lib if you downloaded a Trafodion binary package.)</li>
+ </ul>
+ </p>
+ </li>
+ <li><p>Analyze the results. The test results can be found in <strong><code>phoenix_test/target/surefire-reports</code></strong>. If there are any failures, they would come with file names and line numbers.</p>
+ <p>The source code can be found in <strong><code>phoenix_test/src/test/java/com/trafodion/phoenix/end2end</code></strong>.</p>
+ <p>These are JDBC tests written in java.</p>
+ </li>
+ </ol>
+
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/tests.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/tests.md b/docs/src/site/markdown/tests.md
new file mode 100644
index 0000000..ab9baf4
--- /dev/null
+++ b/docs/src/site/markdown/tests.md
@@ -0,0 +1,71 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+This page describes how to add or modify Trafodion tests and/or test suites. Please refer to the [Contribute](contribute.html) page for information about other ways to contribute to the Trafodion project.
+
+**Note**: The [Test](testing.html) page describes how the different Trafodion test libraries are organized and how you run different test. You should familiarize yourself with that page before modifying the Trafodion tests.
+
+# SQL Tests
+The SQL tests are located in: **```core/sql/regress```**. Please refer to the [Test](testing.html) page for information about each directory. Below, each of these directories is referred to as **```$scriptdir```**.
+
+The default output from **```core/sql/regress/tools/runallsb```** is located in **```$MY_SQROOT/rundir```**. This directory is referred to as **```$rundir```** below.
+
+Files associated with individual tests use the following naming convention: **```\<Type\>\<number\>```**. The files are organized as follows:
+
+Type | Usage | Location
+-----------|------------------------------------|---------------------------------------------
+TEST | The test itself. | **```$scriptdir/<test suite>```**
+EXPECTED | The expected output from the test. | **```$scriptdir/<test suite>```**
+FILTER | Filters out variable results (for example, timestamps) from test results to ensure consistent runs. | **```$scriptdir/<test suite>```**
+LOG | The output from running the test. | **```$rundir/<test suite>```**
+DIFF | Diff between LOG and EXPECTED. | **```$rundir/<test suite>```**
+
+## Modify a Test
+The comments in a test provides information of what it does. Make your changes and then do the following:
+
+* Run the test.
+* Verify that the LOG output is as desired.
+* Copy the LOG output to EXPECTED.
+* Rerun the test and verify that the test passes.
+
+### Output with Variable Data
+If there are time stamps or generated names that may vary from run to run or from user to user, then you need to create a ```FILTER\<test number\>``` file. This will filter out the variable portions of the test results so the test results are consistent.
+
+Example filter file: **```core/sql/regress/core/FILTER024```**
+
+**```core/sql/regress/tools```** contains generic filter files. These cover general/common variables in test output. You will need to add a new test specific filer if it’s specific to your new test output only.
+
+### Check In Changes
+Check in the TEST and EXPECTED files in **```$scriptsdir```**.
+
+## Create New Test
+Creating a test is just a variation of [Modify a Test](#Modify_a_Test). The test should be associated with a test suite that covers the component you want to test. Please contact the [Trafodion Developer List](mail-lists.html) if you need help chosing the correct test suite.
+
+Once you've chosen the test suite and, therefore, the test source directory, you do the following:
+
+* Add the new test file to the test file in the selected test-suite directory.
+ * Use the naming convention found in the directory. (Normally: **```TEST\<nnn\>```**)
+ * Refer to **```core/sql/regress/runregr_\<test suite\>.ksh```** to verify the naming convention used.
+* The test DDL should use the schema name associated with the test suite.
+ * Refer to other test suites for examples.
+* Test and validate as described in [Modify a Test](#Modify_a_Test) above.
+
+## Create New Test Suite
+The test suites cover different SQL components. Most components should be covered with the existing test suites.
+
+Do the following to create a new test suite:
+
+* Create a new directory with the suite name under **```core/sql/regress```**; for example: **```\<new test suite\>```**.
+* Refer to [Create New Test](#Create_New_Test) for instructions on how to add tests to the new test suite.
+* Add a test driver in **```core/sql/regress/tools```** directory with name **```runregr_\<new test suite\>.ksh```**. (Just copy and modify one of the other test drivers.)
+* Add the new test suite to **```core/sql/regress/runallsb/TEST_SUBDIRS```**.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/traf_authentication_config.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/traf_authentication_config.md b/docs/src/site/markdown/traf_authentication_config.md
new file mode 100644
index 0000000..2720428
--- /dev/null
+++ b/docs/src/site/markdown/traf_authentication_config.md
@@ -0,0 +1,96 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes the settings in the **```.traf_authentication_config```** file, which is the configuration file related to [Enabling Security Features in Trafodion](enable-secure-trafodion.html).
+
+# File Location
+By default the Trafodion authentication configuration file is located at **```$MY_SQROOT/sql/scripts/.traf_authentication_config```**. If you want to store the configuration file in a different location and/or use a different filename, then Trafodion supports environment variables to specify the alternate location/name.
+
+Trafodion firsts checks the environment variable **```TRAFAUTH_CONFIGFILE```**. If set, the value is used as the fully qualified Trafodion authentication configuration file.
+
+If the environment variable is not set, then Trafodion next checks the variable **```TRAFAUTH_CONFIGDIR```**. If set, the value is prepended to **```.traf_authentication_config```** and used as the Trafodion authentication file.
+
+If neither is set, Trafodion defaults to **```$MY_SQROOT/sql/scripts/.traf_authentication_config```**.
+
+# Template
+
+ # To use authentication in Trafodion, this file must be configured
+ # as described below and placed in $MY_SQROOT/sql/scripts and be named
+ # .traf_authentication_config. You must also enable authentication by
+ # running the script traf_authentication_setup in $MY_SQROOT/sql/scripts.
+ #
+ # NOTE: the format of this configuration file is expected to change in the
+ # next release of Trafodion. Backward compatibility is not guaranteed.
+ #
+ SECTION: Defaults
+ DefaultSectionName: local
+ RefreshTime: 1800
+ TLS_CACERTFilename:
+ SECTION: local
+ # If one or more of the LDAPHostName values is a load balancing host, list
+ # the name(s) here, one name: value pair for each host.
+ LoadBalanceHostName:
+
+ # One or more identically configured hosts must be specified here,
+ # one name: value pair for each host.
+ LDAPHostName:
+
+ # Default is port 389, change if using 636 or any other port
+ LDAPPort:389
+
+ # Must specify one or more unique identifiers, one name: value pair for each
+ UniqueIdentifier:
+
+ # If the configured LDAP server requires a username and password to
+ # to perform name lookup, provide those here.
+ LDAPSearchDN:
+ LDAPSearchPwd:
+
+ # If configured LDAP server requires TLS(1) or SSL (2), update this value
+ LDAPSSL:0
+
+ # Default timeout values in seconds
+ LDAPNetworkTimeout: 30
+ LDAPTimeout: 30
+ LDAPTimeLimit: 30
+
+ # Default values for retry logic algorithm
+ RetryCount: 5
+ RetryDelay: 2
+ PreserveConnection: No
+ ExcludeBadHosts: Yes
+ MaxExcludeListSize: 3
+
+# Configuration Attributes
+
+Attribute Name | Purpose | Example Value | Notes
+---------------------------|-------------------------------------|---------------------------|---------------------------------------
+**```LDAPHostName```** | Host name of the local LDAP server. | **```ldap.master.com```** | If more than one **```LDAPHostName```** entry is provided, Trafodion will attempt to connect with each LDAP server before returning an authentication error. Also see the description related to **```RetryCount```** and **```RetryDelay```** entries.
+**```LDAPPort```** | Port number of the local LDAP server. | **```345```** | Must be numeric value. Related to **```LDAPSSL```** entry. Standard port numbers for OpenLDAP are as follows: <ul><li>Non-secure: 389</li><li>SSL: 636</li><li>TLS: 389</li></ul>
+**```LDAPSearchDN```** | If a search user is needed, the search user distinguished name is specified here. | **```cn=aaabbb, dc=demo, dc=net```** | If anonymous search is allowed on the local server, this attribute does not need to be specified or can be specified with no value (blank). To date, anonymous search is the normal approach used.
+**```LDAPSearchPWD```** | Password for the **```LDAPSearchDN```** value. See that entry for details. | **```welcome```** | None.
+**```LDAPSSL```** | A numeric value specifying whether the local LDAP server interface is unencrypted or TLS or SSL. Legal values are 0 for unencrypted, 1 for SSL, and 2 for TLS. For SSL/TLS, see the section below on Encryption Support. | **```0```** | None.
+**```UniqueIdentifier```** | The directory attribute that contains the user's unique identifier. | **```uid=,ou=Users,dc=demo,
+dc=net```** | To account for the multiple forms of **```DN```** supported by a given LDAP server, specify the **```UniqueIdentifier```** parameter multiple times with different values. During a search, each **```UniqueIdentifier```** is tried in the order it is listed in the configuration file.
+**```LDAPNetworkTimeout```** | Specifies the timeout (in seconds) after which the next **```LDAPHostName```** entry will be tried, in case of no response for a connection request. This parameter is similar to **```NETWORK_TIMEOUT```** in **```ldap_conf(5)```**. Default value is 30 seconds. | **```20```** | The value must be a positive number or -1. Setting this to -1 results in an infinite timeout.
+**```LDAPTimelimit```** | Specifies the time to wait when performing a search on the LDAP server for the user name. The number must be a positive integer. This parameter is similar to **```TIMELIMIT```** in **```ldap_conf(5)```**. Default value is 30 seconds. | **```15```** | The server may still apply a lower server-side limit on the duration of a search operation.
+**```LDAPTimeout```** | Specifies a timeout (in seconds) after which calls to synchronous LDAP APIs will abort if no response is received. This parameter is similar to **```TIMEOUT```** in **```ldap_conf(5)```**. Default value is 30 seconds. | **```15```** | The value must be a positive number or -1. Setting this to -1 results in an infinite timeout.
+**```RetryCount```** | Number of attempts to establish a successful LDAP connection. Default is 5 retries before returning an error. | **```10```** | When a failed operation is retried, it will be attempted with each configured LDAP server, until the operation is successful or the number of configured retries is exceeded.
+**```RetryDelay```** | Specifies the number of seconds to delay between retries. Default value is 2 seconds. See description of **```RetryCount```**. | **```1```** | None.
+**```PreserveConnection```** | Specifies whether the connection to LDAP server will be maintained (YES) or closed (NO) once the operation finishes. Default value is NO. | **```YES```** | None.
+**```RefreshTime```** | Specifies the number of seconds that must have elapsed before the configuration file is reread. Default is 1800 (30 minutes). | **```3600```** | If set to zero, the configuration file is never read. The connectivity servers must be restarted for changes to take effect if this value is zero. This attribute is not specific to either configuration and must be defined in the DEFAULTS section.
+**```TLS_CACERTFilename```** | Specifies the location of the certificate file for the LDAP server(s). Filename can either be fully qualified or relative to **```$CACERTS_DIR```**. | **```cert.pem```** | This attribute applies to both configurations. If a configuration does not require a certificate, this attribute is ignored. This attribute must be defined in the DEFAULTS section.
+**```DefaultSectionName```** | Specifies the configuration type that will be assigned to a user by the **```REGISTER USER```** command if no authentication type is specified. In the initial Trafodion release, only one configuration is supported. | **```LOCAL```** | This attribute must be defined in the **```DEFAULTS```** section. If the **```DefaultSectionName```** attribute is specified, a section by that name (or equivalent) must be defined in **```.traf_ldapconfig```**. Legal values are **```LOCAL```** and **```ENTERPRISE```**. This syntax is likely to change.
+
+Return to [Enabling Security Features in Trafodion](enable-secure-trafodion.html).
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/wiki.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/wiki.md b/docs/src/site/markdown/wiki.md
new file mode 100644
index 0000000..e583e34
--- /dev/null
+++ b/docs/src/site/markdown/wiki.md
@@ -0,0 +1,23 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to change the Trafodion Wiki. Please refer to the [Contribute](contribute.html) page for information about other ways to contribute to the Trafodion project.
+
+# Getting Access
+
+We use a "white-listing" permissions scheme for editing the Wiki. We do this to prevent anonymous spammers from spamming the site.
+
+If you'd like to contribute to the wiki, just obtain a Confluence user ID on the Apache wiki, then send an e-mail to the dev@incubator.trafodion.org dlist requesting access (and providing your Confluence user ID name).
+
+A friendly administrator will then grant you editing privileges.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/resources/images/multi-layer-esps.png
----------------------------------------------------------------------
diff --git a/docs/src/site/resources/images/multi-layer-esps.png b/docs/src/site/resources/images/multi-layer-esps.png
new file mode 100644
index 0000000..6afa3a8
Binary files /dev/null and b/docs/src/site/resources/images/multi-layer-esps.png differ
[3/8] incubator-trafodion git commit: [TRAFODION-1507] Added new
files.
Posted by db...@apache.org.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/faq.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/faq.md b/docs/src/site/markdown/faq.md
new file mode 100644
index 0000000..a532123
--- /dev/null
+++ b/docs/src/site/markdown/faq.md
@@ -0,0 +1,220 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page provides frequently-asked questions about the Trafodion project and their answers.
+
+# Project
+## What is Project Trafodion?
+Project Trafodion is an open source initiative originally cultivated by HP Labs and HP IT to develop an enterprise-class SQL-on-HBase solution targeted for big data transactional or operational workloads as opposed to analytic workloads.
+
+## When is Trafodion available?
+Trafodion is currently available at downloads.trafodion.org. There, you can find an installer and executable code. For installation instructions, see Installation.
+
+## What are the key features of Trafodion?
+
+The key features are:
+
+* Full-functioned ANSI SQL language support
+* JDBC/ODBC connectivity for Linux/Windows clients
+* Distributed ACID transaction protection across multiple statements, tables and/or rows
+* Transaction recovery to achieve database consistency
+* Optimization for low-latency read and write transactions
+* Support for large data sets using a parallel-aware query optimizer
+* Performance improvements for OLTP workloads with compile-time and run-time optimizations
+* Distributed parallel-processing architecture designed for scalability
+
+## What are the key benefits of Trafodion?
+Trafodion delivers a full-featured and optimized transactional SQL-on-HBase DBMS solution with full transactional data protection. These capabilities help overcome basic Hadoop limitations in supporting transactional workloads.
+
+With Trafodion, users gain the following benefits:
+
+* Ability to leverage in-house SQL expertise versus complex MapReduce programming
+* Seamless support for existing transactional applications
+* Ability to develop next generation highly scalable, real-time transaction processing applications
+* Reduction in data latency for down-steam analytic workloads
+* Adoption of data reuse by different application domains
+
+And operational SQL users also gain the following benefits inherent in Hadoop ecosystem.
+
+* Reduced infrastructure costs
+* Massive scalability and granular elasticity
+* Improved data availability and disaster recovery protection
+
+## Why is it called Trafodion?
+Trafodion is Welsh for transactions.
+
+## What are the primary use cases for Trafodion?
+Primary use cases on Trafodion consist of existing HBase workloads enhanced through SQL with transactional data protection. Another class of use cases consist of new or rehosted existing operational applications to address scalability issues, complex application programming, or prohibitive licensing costs.
+
+## What is the heritage of the Trafodion software?
+Trafodion is based on HP’s 20+ year history in developing database products for OLTP. Building on this heritage, Trafodion provides distributed transaction management protection over multiple SQL statements, multiple tables and multiple rows.
+
+## What do you mean by "Transactional or Operational SQL"?
+Transactional or Operational SQL describe workloads were previously described simply as OLTP (online transaction processing) workloads. This expands that definition from the broad range of enterprise-level transactional applications (ERP, CRM, etc.) to include the new transactions generated from social and mobile data interactions and observations and the new mixing of structured and semi-structured data.
+
+<!-- 20151117 Gunnar Tapper
+
+ Commented out this section since the reference is no longer valid.
+
+ Also, markdown does not like the equal signs in the actual URL, which is why tinyurl
+ is used. Original URL is:
+
+ http://www.gartner.com/technology/reprints.do?id=1-1M9YEHW&ct=131028&st=sb
+
+Further details on Operational DBMS can be found in Gartner’s [Magic Quadrant for Operational Database Management Systems][gartner].
+
+[gartner]: http://tinyurl.com/p5cwass
+
+-->
+
+----
+
+# Using
+## Why would Trafodion be used over a commercial OLTP database?
+Trafodion is an open source product and like other products in the Hadoop ecosystem, it obtains two key advantages over the tradional proprietary OLTP database systems: Cost structure and Data reuse.
+
+## Is Trafodion mainly an extension to HBase?
+Not quite. Trafodion runs on top of HBase using the HBase APIs to perform the typical SQL functions of insert, update, delete, and query data with transactional protection. However, there are plans to include database capabilities using the coprocessor mechanism provided by HBase.
+
+## Besides data access via SQL database connection, what other advantages does Trafodion offer over existing distributed database technologies?
+With Trafodion, users can make use of standard HBase APIs as well as use Trafodion for SQL access to the HBase tables. This includes Trafodion's ability to use powerful SQL capabilities to do joins against both HBase and Trafodion tables and run queries against them while providing transaction management capability.
+
+This allows application developers to choose the best access methods for each particular data usage, based on skill set, data size and usage, and access pattern requirements.
+
+## Can Trafodion modify tables?
+Yes, Trafodion provides full-featured ANSI DML operations including INSERT, UPDATE, DELETE, MERGE, and UPSERT statement support.
+
+## What is the benchmarked performance for a transaction workload?
+Benchmark results will be posted as the community publishes them.
+
+## Where would you position Trafodion according to the CAP theorem? Is it CP (consistent and partition tolerant as HBase) or CA (consistent and highly available)?
+Trafodion is hosted on top of HBase and HDFS. HBase is generally viewed as being CA (Consistent, Available) in the context of the CAP theorem.
+
+Unlike regular HBase, Trafodion extends the definition of consistency to provide ACID protection across transactions comprised of multiple SQL statements, tables, and rows.
+
+## How does Trafodion scale in terms of database size?
+As Trafodion is hosted on HBase/HDFS, in theory, Trafodion’s database should scale as HBase/HDFS scales. To this point (due to available hardware limitations), Trafodion has been tested with configurations up to 10 nodes and 50 terabytes.
+
+## What about high availability? Does Trafodion have a single point of failure?
+HBase and HDFS are considered highly available with many built in features for HA including name node redundancy, HDFS k-safety data replication, HBase replication, HBase snapshots, Zookeeper’s highly reliable distributed coordination of Hadoop hosted services, and so on.
+
+Additionally, the planned release of HBase 1.0 is advertised as having many additional HA features which Trafodion incorporates as it supports HBase 1.0. Furthermore, many Hadoop distributions have added their own HA features at the HBase or HDFS layers.
+
+Trafodion leverages HBase and HDFS capabilities for providing extended HA to the connectivity and SQL layers. For example, Trafodion registers its connection services using Zookeeper to ensure persistent connectivity services. Trafodion is designed as an MPP service with replicated service points for HA and no single points of failure.
+
+## Is Trafodion best suited for reads or for writes?
+Trafodion provides a bulk load capability that interfaces directly with HDFS for high-performance data loading. HBase leverages large-scale cached memory to host data in memory until the HFile buffer becomes filled and is then written to HDFS.
+
+Additionally, Trafodion provides many low-latency read optimizations on top of HBase to significantly improve the both the random and parallel read performance of the database engine. These include:
+
+* Statistics-based plan generation
+* Degree of parallelism optimization
+* In-memory data-flow, scheduler-driven executor
+* Query plan caching
+* Key-based access with SQL “pushdown”
+* Multi-dimensional access method (MDAM)
+* Composite key support
+* Secondary index support
+* Table structure optimizations
+* Salting of row-keys for workload balancing
+
+## Does Trafodion have full text search capabilities?
+Trafodion provides SQL search capabilities using search functions such as POSITION (equivalent to INDEX) and SUBSTRING. Once large object (LOB) support is made available, a user-written or third-party UDF could be plugged in to add search capabilities into documents and images. This is a great area for community contribution.
+
+----
+
+# Transactions
+## Is Trafodion’s transaction management an eventually consistent model?
+No, Trafodion supports full ACID properties. Distributed Transaction Management provides transaction consistency across multiple row updates, updates across multiple tables, and transactions spanning multiple update statements. At the return from a COMMIT WORK statement, all rows and tables are in consistent form with regards to that transaction.
+
+## Does Trafodion provide transaction management for native HBase tables?
+Yes, Trafodion supports transaction management for native HBase tables.
+
+## Does Trafodion support read consistency?
+Yes, all the reads in Trafodion are completely consistent.
+
+## Does Trafodion offer ability to rollback transactions?
+Yes, Trafodion offers full ACID protection across multiple SQL statements, tables, or rows. Transactions can be aborted using the ROLLBACK WORK statement.
+
+## Is there a transaction log and can the log be shipped to a DR site?
+Not really. There are two logs that the transaction manager uses to coordinate transaction history, one at an HBase regionserver level and the other at the transaction manager level. But there is no support for shipping and replaying these logs on a remote DR site in a transactionally consistent manner.
+
+## Does Trafodion support distributed transaction management across multiple data centers?
+There is no support for transaction management between Trafodion instances in different data centers.
+
+## How does two-phase commit scale linearly on large clusters?
+Trafodion employs a Distributed Transaction Manager (DTM) model where a DTM runs on every datanode and each DTM works with its peers in other datanodes to coordinate the two-phase commit protocol. For efficiency purposes, the DTM is invoked only when necessary:
+
+* If the transaction involves only a single region, then two-phase commit coordination is not necessary.
+* The DTM is not involved with read-only transactions.
+* The DTM is not involved in loading data into empty tables or during index creation.
+* If the transaction impacts only a single table row, then standard HBase ACID protection is used instead of the DTM right now. In the future,these transactions might be fast-tracked using a different mechanism.
+
+----
+
+# Hadoop Integration
+## Does Trafodion work as a Hadoop Yarn application?
+Trafodion has not been tested with Yarn yet, but there is nothing in Trafodion that precludes it from being treated as a regular application running in a Yarn container.
+
+## Can Trafodion access Hive stored data?
+Trafodion does provide the capability for SQL statements submitted to Trafodion to access, join, and aggregate a combination of Trafodion database objects, native HBase objects, and Hive tables (via the HCatalog).
+
+## Can we access Trafodion data with MapReduce?
+While theoretically possible since Trafodion data is stored in HBase/HDFS, the data would not be easily interpreted due to the encoding mechanisms Trafodion employs for transaction performance and efficiency.
+
+Trafodion provides automatic access parallelism without the need for writing MapReduce. If the optimized plan calls for parallel execution, the Trafodion Master process divides the work among Executive Server Processes (ESPs) to perform the work in parallel on behalf of the Master process. The results are passed back to the Master for consolidation.
+
+In some situations where there a highly complex plan specified (for example, large n-way joins or aggregations), multiple layers of ESPs may be requested. See the diagram below.
+
+<center><img src="images/multi-layer-esps.png"/></center>
+
+## Can Trafodion data be accessed through Hive? Can we publish a Trafodion table to HCatalog and query it using Hive?
+While theoretically possible since Trafodion data is stored in HBase/HDFS, the data would not be easily interpreted due to the encoding mechanisms Trafodion employs for transaction performance and efficiency.
+
+Trafodion maintains its own catalog for metadata that provides the relational abstraction layer for accessing the physical storage layer via SQL commands. Trafodion objects are complex as they can have tables, indexes, views, constraints, which are represented in Trafodion’s own catalog. HCatalog can represent only simple objects like tables or column families currently but does not contain support for representing other more complex relational objects.
+
+Alternatively, Trafodion data could be loaded into Hive/HDFS and then accessed using Hive specific operations or native MapReduce jobs.
+
+----
+
+# Security
+## How is Database security management supported in Trafodion?
+Currently, Trafodion provides security management based on HBase capabilities. There are projects as part of roadmap to provide full GRANT/REVOKE capability at the table and schema level for users and roles, along with support for directory based authentication.
+
+## Does Trafodion have role-based security authorization?
+Yes, Trafodion supports ANSI GRANT/REVOKE on both an individual user and role basis. See Enabling Security Features in Trafodion. For details on the GRANT/REVOKE syntax, see the Trafodion SQL Reference Manual (pdf, 3.98 MB).
+
+## What is Trafodion’s security authorization granularity?
+Trafodion supports authorization (that is, privileges) at the system and database-object level. System privileges are valid across SQL, such as the ability to create schemas and objects. Object privileges include tables, views, and other databse objects. Views can be used to restrict access to the subset of table rows referenced within the view.
+
+----
+
+# Infrastructure
+## What hardware do I need to run Trafodion? Is it hardware vendor neutral?
+Trafodion is designed to be hosted on vendor neutral, commodity hardware. As Trafodion runs on top of HBase and HDFS, a vendor's recommended reference architectur such as HP Reference Architecture for Hadoop or similar server configuration is recommended as a starting point for a new installation.
+
+## Does Trafodion need to be installed on all the Hadoop cluster nodes?
+Trafodion needs to be installed on all nodes that host an HBase RegionServer. Trafodion comes with an install script to make the installation process easy. For more information, see the Trafodion installation instructions.
+
+## What does Trafodion software require?
+Trafodion software requires an x86-64 bit hardware platform running RedHat Enterprise Linux or CentOS 6.x kernel (64-bit). It supports Cloudera and Hortonworks Hadoop distributions; for details, see Supported Hadoop Distributions. The software is intended to be Linux and Hadoop distribution neutral, but other distributions have not been tested at this time.
+
+## Are there any recommended configurations in terms of nodes, memory, etc.?
+Recommended sizings for Trafodion are still being developed, and vary based on the amount of data, anticipated query workload (types, rates/respose times, concurrency) and the peak number of supported concurrent connections).
+
+What’s the process like when we add a new node to the cluster? Does the system grow elastically?
+The underlying HBase/HDFS infrastructure supports elastic scalability allowing for incremental node expansion, that is, datanode expansion. Trafodion could then access the HBase tables (or ‘regions’ of the HBase tables) that now span the new node(s). Trafodion services (that is, connection, compiler, master, ESP) can be made to leverage these additional nodes by restarting Trafodion with a new coniguration.
+
+## Does Trafodion need dedicated hardware?
+Trafodion can run on dedicated hardware, cloud or VM configurations. For best and consistent performance, dedicated hardware is recommended where feasible.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/install-preparation.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/install-preparation.md b/docs/src/site/markdown/install-preparation.md
new file mode 100644
index 0000000..3848746
--- /dev/null
+++ b/docs/src/site/markdown/install-preparation.md
@@ -0,0 +1,138 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes the steps you need to perform before installing Trafodion.
+
+# Cluster Requirements
+The following configuration settings have been tested and are known to work with the Trafodion installation:
+
+Setting | Value
+------------------------------|-------------------------------------------------
+**Hardware Platform** | x86-64
+**Operating System** | RedHat Enterprise Linux, 6.x kernel (64 bit) or CentOS, 6.x kernel (64 bit)
+**Install User IDs** | A user ID with passwordless and sudo access. Please refer to [Install User ID](#Install User ID) below.
+**Cluster Size** | A cluster consisting of 1 to N nodes. There is currently no upper limit. Two nodes is the recommended minimum, but a single node cluster should work.
+**Disk Space** | Minimum of 20 GB. Please refer to [Checking Disk Space](#Checking_Disk_Space) below.
+**Memory** | Minimal 1 GB * number of connectivity servers (MXOSRVR processes) configured per cluster.
+
+## Checking Disk Space
+### Cloudera Manager
+This step is required for Cloudera distributions only.
+
+Before installing Cloudera Manager, a minimum of 20 GB is needed to support the Cloudera management database. Default location: **```/var/lib/cloudera-scm-server-db```**.
+
+Check the available space for **```/var```** as follows:
+
+* Start a putty or VNC terminal window agains the node where Cloudera Manager will be installed.
+* As a user with **```root```** privileges, verify that 20 GB of space is available to **```/var```**.
+
+ cd /var
+ df -hP
+
+If the **```/var```** space is insufficient, then you can provide a soft link to another drive for your Cloudera Manager database.
+
+* Locate a drive with sufficient disk space.
+* Create the soft link.
+
+```
+cd <new drive> # (e.g. cd /DATA)
+mkdir cloudera-scm-server-db
+chmod 777 cloudera-scm-server-db
+cd /var/lib
+ln -s <new drive>/cloudera-scm-server-db .
+```
+
+**Considerations**
+
+* If **```/var```** is a sub-directory in your cluster's root filesystem, then the Cloudera Manager database should have sufficient space available.
+* If Cloudera Manager has already been installed and it is showing red for log directories, it means that Cloudera Manager was installed using **```/var/lib```** and may not have a large enough **```/var```** file system. In this case, there is an unsupported script that can be used to move the directories. Please refer to the **```clouderaMoveDB.sh```** script in the **```installer/tools```** directory, which is created when the installer tar file is unpacked. Run **```clouderaMoveDB.sh```** without syntax to display help information.
+
+# Security Requirements
+## Install User ID
+The Trafodion installation requires a user ID (referred to as **```<sudo-user>```**) with these attributes on all nodes where Trafodion is installed:
+
+* **```/etc/sudoers```* on all nodes:
+ * **```sudo```** access — allows the install scripts to run privileged commands.
+ * **requiretty** disabled — allows Trafodion install scripts to use embedded **```sudo```** commands
+* passwordless ssh to all nodes — allows Trafodion install scripts to communicate with remote nodes without prompting for password.
+
+Please create a the **```<sudo-user>```** per the practices of your environment. For example, you may need to request permission from your cluster-management team to obtain this type of access. [Passwordless SSH(passwordless-ssh.html) describes how to set up passwordless ssh.
+
+## Configure LDAP Identity Store
+If you plan to enable Trafodion authentication, then you need to have an LDAP identity store available to perform authentication.
+
+The Trafodion installer prompts you to set up an authentication configuration file that points to an LDAP server (or servers), which enables security (that is, authentication and authorization) in the Trafodion system.
+
+If you wish to manually set up the authentication configuration file and enable security, then please refer to [Enabling Security Features in Trafodion](enable-secure-trafodion.html).
+
+# PC Installation
+If you are using a Windows PC, then additional PC software may be needed throughout the installation process. It is recommended that you pre-install the PC software that you need before continuing with the Trafodion installation.
+
+Install the following software:
+
+* putty and puttygen (download from the [PuTTY website](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html))
+* VNC client (download from http://www.realvnc.com)
+* Firefox or Chrome browser
+* SFTP client to transfer files from your PC to the server: WinSCP or FileZilla
+
+# Install Hadoop Distribution
+Trafodion requires that the following Hadoop services are installed:
+
+* HDFS
+* MapReduce
+* ZooKeeper
+* HBase
+* Hive
+
+Please ensure that these services are installed for one of the following Hadoop distributions.
+
+<table><tr><td><strong>IMPORTANT</strong><br />Trafodion does not support a Hadoop server running on a node that is not part of the Trafodion cluster. You must specify the Hadoop nodes to be part of the Trafodion list of nodes during the installation of Trafodion (using the <strong><code>--nodes</code></strong> parameter). The Trafodion installer needs to run from the same node where you installed the Hadoop distribution).</td></tr></table>
+
+<table>
+ <tr>
+ <th>Distribution</th>
+ <th>Version</th>
+ <th>HBase Version</th>
+ <th>Installation</th>
+ <th>Notes</th>
+ </tr>
+ <tr>
+ <td><strong>Cloudera</strong></td>
+ <td>CDH 5.2 or 5.3</td>
+ <td>0.98.6</td>
+ <td>Refer to <a href="http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/installation.html" target="_blank">CDH 5.3.x Installation and Upgrade Guide</a> for installation instructions.</td>
+ <td>
+ <ul>
+ <li>Select <strong>Cloudera Standard</strong> edition.</li>
+ <li>Install using <strong>packages</strong>. Do not install using tarballs and parcels. Trafodion does not currently support tarball/parcel installation.</li>
+ <li>CDH 5.2 is supported but has not been officially tested with Trafodion Release 1.3.</li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><strong>Hortonworks Data Platform (HDP)</strong></td>
+ <td>HDP 2.2</td>
+ <td>0.98.4</td>
+ <td>
+ <ul>
+ <li><strong>Install</strong>: <a href="http://docs.hortonworks.com/HDPDocuments/Ambari-1.7.0.0/Ambari_Install_v170/Ambari_Install_v170.pdf">Ambari 1.7.0 Install Guide</a></li>
+ <li><strong>Upgrade:</strong> <a href="http://docs.hortonworks.com/HDPDocuments/Ambari-1.7.0.0/Ambari_Upgrade_v170/Ambari_Upgrade_v170.pdf">Ambari 1.7.0 Upgrade Guide</a></li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+</table>
+
+# Validation
+Once the Hadoop distribution has been installed and started, please ensure that the required services are running. At this point, you're ready to [Install Trafodion](install.html).
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/install.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/install.md b/docs/src/site/markdown/install.md
new file mode 100644
index 0000000..07fe6af
--- /dev/null
+++ b/docs/src/site/markdown/install.md
@@ -0,0 +1,203 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to install the Trafodion product environment. [Create Development Environment](create-dev-environment.html) describes how to create the Trafodion Development Test Environment.
+
+The Trafodion product environment is installed using the Trafodion Installer, which operates on Trafodion binaries only. Refer to the [Download](download.html) page for instructions about how you download/create the Trafodion binaries.
+
+# Preparation
+The Trafodion Installer assumes that you've performed the following steps before a Trafodion install:
+
+1. **Cluster Requirements**: ensure that you cluster meets the Trafodion requirements.
+2. **Security Requirements**: Create the user ID that is used to run the Trafodion Installer. Review and configure LDAP, if desired.
+3. **Prepare PC**: install software used when installing Trafodion on your PC.
+4. **Install Hadoop**: Install Hadoop software supported by Trafodion.
+5. **Validate Hadoop**: Validate that required Hadoop services are running.
+
+Please refer to [Install Preparation](install-preparation.html) for information about how to perform the steps above.
+
+# Security Considerations
+You use the following user IDs and passwords during the Trafodion installation.
+
+Logon | User ID | Password | Description
+-----------------------------------|----------------------------|-----------------------------|--------------------------------------------------------
+Cloudera Manager Web GUI logon | **```admin (default)```** | **```admin (default)```** | After installing Cloudera, you will be instructed to log on to the Cloudera Manager Web GUI. Use the default user ID and password (**```admin```**, **```admin```**). If you already had Cloudera installed, please use your previously defined user ID and password.
+Ambari Web GUI logon | **```admin (default)```** | **```admin (default)```** | After downloading and setting up the Ambari repository, you will be instructed to log on to the Ambari Web GUI. Use the default user ID and password (**```admin```**, **```admin```**). If you already had Ambari installed, please use your previously defined user ID and password.
+User ID with sudo Access | **```<sudo-username>```** | **```<password>```** | In the installation steps, you may be instructed to use **```sudo```** or **```sudo userid```** access. You will be using your user ID, which has been enabled with **```sudo```** access and [passwordless ssh](passwordless-ssg.html) to all nodes of the cluster.
+Trafodion Logon | **```trafodion```** | **```traf123 (default)```** | The Trafodion installer **automatically creates** this user IDwhen Trafodion is installed. Do not create this user ID manually.
+VNC Server Logon | **```trafodion```** | **```traf123 (default)```** | After installing Trafodion, you will be instructed to log on to the VNC server at port 1. Use the **```trafodion```** user ID and **```password```**.
+
+# Install Procedure
+## Upgrade
+Follow these steps if you have an older version of Trafodion that you want to upgrade:
+
+1. *Shutdown Trafodion*: Please refer to [Manage Trafodion](management.html).
+2. *Backup Data*: Backup metadata and user objects. Please refer to [Backup/Restore](backuprestore.html).
+3. *Install Trafodion*: The **```trafodion_install```** script automatically detects the previous version of Trafodion and performs an upgrade operation, including initializing Trafodion, upgrading the metadata, and restarting all processes. Please refer to [Installation](#Installation) below for more information about **```trafodion_install```**.
+
+ If something goes wrong during the installation, restore your data from the backed up objects and repeat the previous step.
+
+<table><tr><td><strong>NOTE</strong>
+ <p>If you are doing an upgrade outside of the installation environment, then you will need to restart your services and processes, such as sqlci, the DCS server, and the qms servers. If you do not restart those services and processes, your system will not work properly.</p>
+</td></tr></table>
+
+## Installation
+
+<table><tr><td><strong>NOTE</strong><br /> If performing an upgrade: Please refer to [Upgrading Trafodion](#Upgrading_Trafodion) before proceeding.</td></tr></table>
+
+At a high level, the following instructions consist of a single step:
+
+Command | User ID | Comments
+----------------------------|---------------------------|---------------------------------------------------------------------------------------------------------
+**```trafodion_install```** | **```<sudo-username>```** | Installs necessary RPMs, creates the **```trafodion```** user ID, sets up passwordless ssh for the **```trafodion```** user ID, copies the Trafodion distribution files across the cluster, generates startup files, and starts Trafodion, including Database Connectivity Services (DCS) (the ODBC/JDBC server), among other things.
+
+
+<table><tr><td>
+ <strong>IMPORTANT</strong>
+ <p>The Trafodion commands should all be done from the first node of the cluster. Do not run them from a machine that is not part of the Trafodion cluster. Trafodion must be installed on all nodes that host an HBase RegionServer (that is, where a supported Hadoop distribution is installed).</p>
+ <p>For example, if Cloudera or Hortonworks is installed on nodes <strong><code>n001</code></strong>, <strong><code>n002</code></strong>, and <strong><code>n003</code></strong>, then you must install Trafodion on those same nodes (<strong><code>--nodes "n001 n002 n003"</code></strong>).</p>
+</td></tr></table>
+
+<table>
+ <tr>
+ <th width="5%">Step</th>
+ <th width="35%">Description</th>
+ <th width="60%">Commands</th>
+ </tr>
+ <tr>
+ <td><strong>Download</strong></td>
+ <td>If you haven't done so already, then please download the Trafodion software.</td>
+ <td>Please refer to <a href="download.html">Download</a>.</td>
+ </tr>
+ <tr>
+ <td><strong>Upgrade</strong></td>
+ <td>
+ <p>If you are upgrading to a newer version of Trafodion, copy the installation files for the previous version to a directory outside of <strong><code>$HOME/trafodion_downloads</code></strong>.</p>
+ <p>For example:</p>
+ <pre>mkdir $HOME/trafodion_downloads_v1.0</pre>
+ </td>
+ <td><pre>cp –r $HOME/trafodion_downloads/* $HOME/trafodion_downloads_v1.0
+rm –rf $HOME/trafodion_downloads/*</pre>
+ </td>
+ </tr>
+ <tr>
+ <td><strong>Create <code>trafodion_downloads</code></strong></td>
+ <td>Create the <strong><code>trafodion_downloads</code></strong> directory if you have not done so already and place the downloaded <strong><code>trafodion-1.1.<n>.tar.gz</code></strong> and <strong><code>installer-1.1.<n>_v<num>.tar.gz</code></strong> tar files into it.</td>
+ <td>
+ <pre>
+mkdir $HOME/trafodion_downloads
+mv <your-download-path>/trafodion-1.1.<n>.tar.gz $HOME/trafodion_downloads
+mv <your-download-path>/installer-1.1.<n>_v<num>.tar.gz $HOME/trafodion_downloads
+cd $HOME/trafodion_downloads
+ </pre>
+ </td>
+ </tr>
+ <tr>
+ <td><strong>Unpack tar File</strong></td>
+ <td>Untar the downloaded installer file.</td>
+ <td><pre>tar -xzf installer-1.1.<n>_v<num>.tar.gz</pre></td>
+ </tr>
+ <tr>
+ <td><strong>Run <code>trafodion_install</code></strong></td>
+ <td>
+ <p>The scripts is run without parameters. Instead, you'll be prompted for information.</p>
+ <p><strong>NOTE</strong></p>
+ <p>The trafodion_install script automatically invokes the <a href="scanner.html">Trafodion Scanner</a> to check the cluster for attributes that commonly cause installation issues, runtime performance problems, and so on. Also, various system information is collected for future reference, such as to aid with troubleshooting. The installation will abort if any configuration errors are discovered. You will need to correct such errors before re-running the <strong><code>trafodion_install</code></strong>script.</p>
+ </td>
+ <td>
+ <pre>
+cd installer
+./trafodion_install
+ </pre>
+ <p>Type "accept" to accept the license agreement when prompted.</p>
+ <p>Provide the requested information according to the prompts.</p>
+ <p><strong>NOTE</strong></p>
+ <p>If you choose not to start Trafodion after the installation (that is, if you enter <strong><code>N</code></strong> for <strong><code>Start Trafodion after install (Y/N)</code></strong>), you will need to manually start and initialize Trafodion after <strong><code>trafodion_install</code></strong> completes.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><strong><code>trafodion_install</code> Completion</strong></td>
+ <td>Wait for <strong><code>trafodion_install</code></strong> to complete. </td>
+ <td><p>You will see the following message:</p><pre>***INFO: Installation completed successfully.</pre></td>
+ </tr>
+ <tr>
+ <td><strong>Connect</strong></td>
+ <td>Once <strong><code>trafodion_install</code></strong> completes without error, your Trafodion system should be up and running.</td>
+ <td>
+ <p>Start a new VNC session using port :1.</p>
+ <p>Log in as the <strong><code>trafodion</code></strong> user with the password for the VNC, which is <strong><code>traf123</code></strong> by default unless you changed it.</p>
+ </td>
+ </tr>
+</table>
+
+## Start and Initialize
+If you chose not to start Trafodion after the installation, start and initialize Trafodion as follows:
+
+ cds
+ sqstart
+
+ [trafodion@n001 ~]$ sqlci
+ Trafodion Conversational Interface 1.1.0
+ (c) Copyright 2015 Apache Software Foundation
+ >>initialize trafodion ;
+ .
+ .
+ .
+
+## Validate Installation
+Perform a quick sanity check using the Trafodion Conversational Interface (**```sqlci```**). Create a table with a couple of records.
+
+**Example**
+
+ [trafodion@n001 ~]$ sqlci
+ Trafodion Conversational Interface 1.1.0
+ (c) Copyright 2015 Apache Software Foundation
+ >> create table test1 (f1 int, f2 int);
+
+ --- SQL operation complete.
+ >> insert into test1 values(1,1);
+
+ --- 1 row(s) inserted.
+ >> insert into test1 values(2,2);
+
+ --- 1 row(s) inserted.
+ >> select * from test1;
+
+ F1 F2
+ ----------- -----------
+ 1 1
+ 2 2
+
+ --- 2 row(s) selected.
+ >> get tables;
+
+ Tables in Schema TRAFODION.SEABASE
+ ==================================
+
+ TEST1
+
+ --- SQL operation complete.
+ >> exit;
+
+The SQL commands above should run successfully.
+
+## Install Client Software
+Download and install the Trafodion JDBC and/or ODBC drivers on your client workstation to be able to connect to Trafodion from a client application. Please refer to the [Trafodion Client Installation Guide](docs/Trafodion_Client_Installation_Guide.html), which describes how to install the JDBC and ODBC drivers, how to connect to Trafodion, and how to run sample programs to test the connection.
+
+# Troubleshooting
+Please refer to [Troubleshoot Trafodion Installation](install-troubleshoot.html).
+
+# Uninstall
+Please refer to [Unistall Trafodion](uninstall.html).
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/ldapcheck.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/ldapcheck.md b/docs/src/site/markdown/ldapcheck.md
new file mode 100644
index 0000000..f5f4d1a
--- /dev/null
+++ b/docs/src/site/markdown/ldapcheck.md
@@ -0,0 +1,41 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes ldapcheck, which is a tool that is used to validate the Trafodion authentication configuration and attempt to connect to a configured LDAP server.
+
+# Usage
+
+```
+ldapcheck [<option>]...
+<option> ::= --help|-h display usage information
+ --username=<LDAP-username>
+ --password[=<password>]
+ --primary Use first configuration
+ --local Use first configuration
+ --enterprise Use first configuration
+ --secondary Use second configuration
+ --remote Use second configuration
+ --cluster Use second configuration
+ --verbose Display non-zero retry counts
+ and LDAP errors
+```
+
+# Considerations
+
+* Aliases for primary include enterprise and local. Aliases for secondary include cluster and remote. If no configuration is specified, primary is assumed.
+* The equals sign is required when supplying a value to username or password.
+* To be prompted for a password value with no echo, specify the password argument but omit the equals sign and value.
+* Passwords that contain special characters may need to be escaped if the password is specified on the command line or within a script file.
+* If the password keyword is not specified, only the username will be checked. The tool can therefore be used to test the LDAP configuration and connection to the configured LDAP server(s) without knowing a valid username or password.
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/ldapconfigcheck.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/ldapconfigcheck.md b/docs/src/site/markdown/ldapconfigcheck.md
new file mode 100644
index 0000000..806150f
--- /dev/null
+++ b/docs/src/site/markdown/ldapconfigcheck.md
@@ -0,0 +1,48 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes the **```ldapconfigcheck```** tool, which validates the syntactic correctness of a Trafodion authentication configuration file. Trafodion does not need to be running to run the tool.
+
+# Considerations
+If the configuration filename is not specified, the tool will look for a file using environment variables. Those environment variables and the search order are:
+
+1. TRAFAUTH_CONFIGFILE
+
+ A fully qualified name is expected.
+2. TRAFAUTH_CONFIGDIR
+
+ Filename **```.traf_authentication_config/```** is appended to the specified directory
+3. MY_SQROOT
+
+ **```/sql/scripts/.traf_authentication_config```** is appended to the value of **```MY_SQROOT```**.
+
+# Errors
+One of the following is output when the tool is run. Only the first error encountered is reported.
+
+Code | Text
+-----------------|--------------------------------------------------------------------------------
+**```0```** | File *filename* is valid.
+**```1```** | File *filename* not found.
+**```2```** | File: *filename*<br /><br />Invalid attribute name on line *line-number*.
+**```3```** | File: *filename*<br /><br />Missing required value on line *line-number*.
+**```4```** | File: *filename*<br /><br />Value out of range on line *line-number*.
+**```5```** | File: *filename*<br /><br />Open of traf_authentication_config file failed.
+**```6```** | File: *filename*<br /><br />Read of traf_authentication_config file failed.
+**```7```** | No file provided. Either specify a file parameter or verify environment variables.
+**```8```** | TLS was requested in at least one section, but TLS_CACERTFilename was not provided.
+**```9```** | Missing host name in at least one section.<br /><br />Each LDAP connection configuration section must provide at least one host name.
+**```10```** | Missing unique identifier in at least one section.<br /><br />Each LDAP connection configuration section must provide at least one unique identifier.
+**```11```** | At least one LDAP connection configuration section must be specified.
+**```12```** | Internal error parsing . traf_authentication_config.
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/manage-dev-environment.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/manage-dev-environment.md b/docs/src/site/markdown/manage-dev-environment.md
new file mode 100644
index 0000000..2559c8d
--- /dev/null
+++ b/docs/src/site/markdown/manage-dev-environment.md
@@ -0,0 +1,51 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how you manage the Trafodion development test environment, which is intended for people that are contributing to the Trafodion source tree. Please refer to [Download](download.html) if you want to try the Trafodion product environment.
+
+# Prerequisites
+You must have created the [Trafodion Development Environment](create-dev-environment.html) before using the instructions on this page.
+
+# Hadoop Enviroment
+## Pre-Existing Hadoop
+If you are doing Trafodion development on a pre-existing Hadoop distribution, then do the following:
+
+* **Distribution**: Use the distribution management too. For example: Apache Ambari or Cloudera Manager.
+* **Regular Hadoop**: Use the start/stop script for each Hadoop environment.
+
+## Local Hadoop
+Use the following commands to manage the Hadoop environment.
+
+Command | Usage
+-----------------------------------|-----------------------------------------
+**```swstartall```** | Start the complete Hadoop environment.
+**```swstopall```** | Stops the complete Hadoop environment.
+**```swstatus```** | Checks the status of the Hadoop environment.
+**```swuninstall_local_hadoop```** | Removes the Hadoop installation.
+
+# Trafodion
+Please refer to [Trafodion Management](management.html).
+
+# New Source Download
+You need to do the following each time you download new source code.
+
+ cd <Trafodion source directory>
+ source ./env.sh
+ cd $MY_SQROOT/etc
+ # delete ms.env, if it exists
+ rm ms.env
+ cd $MY_SQROOT/sql/scripts
+ sqgen
+
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/management.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/management.md b/docs/src/site/markdown/management.md
new file mode 100644
index 0000000..e651cc4
--- /dev/null
+++ b/docs/src/site/markdown/management.md
@@ -0,0 +1,62 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how you manage Trafodion.
+
+# Management Scripts
+The following table provides an overview of the different Trafodion management scripts.
+
+Component | Start | Stop | Status
+--------------------------------------|----------------------|---------------------|---------------------
+All of Trafodion | **```sqstart```** | **```sqstop```** | **```sqcheck```**
+DCS (Database Connectivity Services) | **```dcsstart```** | **```dcsstop```** | **```dcscheck```**
+REST Server | **```reststart```** | **```reststop```** | —
+LOB Server | **```lobstart```** | **```lobstop```** | —
+RMS Server | **```rmsstart```** | **```rmsstop```** | **```rmscheck```**
+
+**Example: Start Trafodion**
+
+ cd $MY_SQROOT/sql/scripts
+ sqstart
+ sqcheck
+
+# Validate Trafodion Installation
+You can use **```sqlci```** or **```trafci```** (connects via DCS) to validate your installation.
+
+ get schemas;
+ create table table1 (a int);
+ invoke table1;
+ insert into table1 values (1), (2), (3), (4);
+ select * from table1;
+ exit;
+
+Assuming no errors, your installation has been successful. You can start working on your modifications.
+
+# Troubleshooting Tips
+If you are not able to start up the environment or if there are problems running **```sqlci```** or **```trafci```**, then verify that the all the processes are up and running.
+
+* **```swstatus```** should show at 6 java servers and 2 mysql processes.
+* **```sqcheck```** should indicate all processes are running.
+
+If processes are not running as expected, then:
+
+* **```sqstop```** to shut down Traodion. If some Trafodion processes do not terminate cleanly, then run **```ckillall```**.
+* **```swstopall```** to shut down the Hadoop ecosystem.
+* **```swstartall```** to restart the Hadoop ecosystem.
+* **```sqstart```** to restart Trafodion.
+
+If problems persist please review logs:
+
+* **```$MY_SQROOT/sql/local_hadoop/\*/log```**: Hadoop, HBase, and Hive logs.
+* **```$MY_SQROOT/logs```**: Trafodion logs.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/new-features.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/new-features.md b/docs/src/site/markdown/new-features.md
new file mode 100644
index 0000000..ada9081
--- /dev/null
+++ b/docs/src/site/markdown/new-features.md
@@ -0,0 +1,15 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page will provide information about features that have recently been added to Trafodion.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/passwordless-ssh.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/passwordless-ssh.md b/docs/src/site/markdown/passwordless-ssh.md
new file mode 100644
index 0000000..9935d8b
--- /dev/null
+++ b/docs/src/site/markdown/passwordless-ssh.md
@@ -0,0 +1,131 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to setup passwordless ssh for a Trafodion user.
+
+# Overview
+Please use these commands to enable passwordless ssh access for a user ID; for example: **```trafodion```**
+
+You need to define the authorization keys on each node on the instance. To simplify this procedure, this procedure starts from scratch; that is, it removes the **```ssh```** configuration so that new files can be created. The procedure on this page defines what you need to do to set up passwordless ssh manually:
+
+* Run all commands from a single node in the instance. This node is labeled **master node** in the procedure.
+* The commands will reach out to all other nodes in the instance. You will have to provide the correct password manually until the procedure has been completed.
+* Ensure that you run the validation step. If passwordless ssh isn't working, then you likely missed a step in the procedure; you'll have to start over.
+
+<table>
+ <tr>
+ <td><strong>Note</strong> <br /><br />You run these commands for each node in the instance, including the master node; that is, you run these commands as well if you are on a single-node instance.
+ </td>
+ </tr>
+</table>
+
+In this procedure, you perform the following steps:
+
+* Generate the **```~/.ssh/id_dsa.pub```** file.
+* Populate the local **```~/.ssh/authorized_keys```** file.
+* Copy files to all nodes in the instance.
+* Add **```localhost```** key to each node's **```~/.ssh/known_hosts```** file.
+* Turn on **```NoHostAuthenticationForLocalhost```** on each node.
+* Secure the files for passwordless ssh access.
+* Validate passwordless ssh access.
+
+The result of the above procedure should be that the content of the **```~/.ssh/authorized_keys```** file is the same on all nodes in your instance and that the security is set up the same way. This allows you to use ssh to login in to any node from any node in the instance without having to specify a password. This is key for many scripts and support commands, which assume that passwordless ssh is working properly. For example, most support commands uses the **```pdsh $MY_NODES```** or **```pdsh $MY_HADOOP_NODES```** command for status checks.
+
+# Command Summary
+A summary of the commands used in this procedures to help experienced users:
+
+ # Skip this step if logged in as a user that has run EsgynDB sqenv.sh, which defines NODE_LIST.
+ # Modify the NODE_LIST content to list the nodes on which you are installing Trafodion.
+ export NODE_LIST="node01.host.com node02.host.com node03.host.com node04.host.com node05.host.com"
+
+ # Get the user ID we're doing this work for. Makes the rest of the commands cleaner.
+ user=$(whoami)
+
+ # Generate ~/.ssh/id_dsa.pub on each node in the instance
+ for node in $NODE_LIST; do ssh $user@$node "rmdir ~/.ssh; mkdir ~/.ssh; cd ~/.ssh; echo -e 'y\n' | ssh-keygen -t rsa -N '' -f $~/.ssh/id_rsa"; done
+
+ # Populate ~/.ssh/authorized_keys file on the master node.
+ for node in $NODE_LIST; do ssh $user@$node "cat ~/.ssh/id_dsa.pub" >> ~/.ssh/authorized_keys; done
+
+ # Copy files to all nodes in the instance but the master node.
+ my_node=$(echo $HOSTNAME | cut -d '.' -f 1)
+ for node in $NODE_LIST; do if [ $node <> $my_node ]; then scp ~/.ssh/authorized_keys ~/.ssh/known_hosts $user@$node:~/.ssh/.; fi; done
+
+ # Add localhost public key to each node's ~/.ssh/known_hosts file.
+ for node in $NODE_LIST; do ssh $user@$node "echo localhost $(cat /etc/ssh/ssh_host_rsa_key.pub) >> ~/.ssh/known_hosts"; done
+
+ # Turn on NoHostAuthenticationForLocalhost on each node.
+ for node in $NODE_LIST; do ssh $user@$node "echo "NoHostAuthenticationForLocalhost=yes" >> ~/.ssh/config"; done
+
+ # Change security of ~/.ssh directory and key files.
+ for node in $NODE_LIST; do ssh $user@$node "chmod 755 ~/.ssh; chmod 600 ~/.ssh/authorized_keys; cd ~/.ssh; chmod 700 .."; done
+
+ # Validate that passwordless ssh works. No password prompts should be seen. Try from all or some nodes in the instance.
+ for node in $NODE_LIST; do ssh $user@$node "ls -al /etc/passwd"; done
+
+
+# Detailed Commands
+
+## Define ```NODE_LIST```
+The steps below assumes that the **```NODE_LIST```** environmental variable contains the node names onto which Trafodion should be installed. You populate this variable using one of the following methods:
+
+1. Invoke the Trafodion **```sqenv.sh```** script, which is present after Trafodion has been installed.
+2. Create **```NODE_LIST```** manually; for example:
+
+ export NODE_LIST="node01.host.com node02.host.com node03.host.com node04.host.com node05.host.com"
+
+## Generate the ```~/.ssh/id_dsa.pub file```
+In this step, you create the authorization key for each node in the instance. This key will be located in the **```~/.ssh/id_dsa.pub```** file. Use the following commands for each node of the instance:
+
+ $ user=$(whoami)
+ $ for node in $NODE_LIST; do ssh $user@$node "rmdir ~/.ssh; mkdir ~/.ssh; cd ~/.ssh; echo -e 'y\n' | ssh-keygen -t rsa -N '' -f $~/.ssh/id_rsa"; done
+
+## Populate the local ```~/.ssh/authorized_keys file```
+In this step, you populate the **```~/.ssh/authorized_keys```** file on master node by copying the content from each node's **```~/.ssh/id_dsa.pub```** file.
+
+Use the following command string to copy the content of **```~/.ssh/id_dsa.pub```** file for each node into the **```~/.ssh/authorized_keys```** on the master node:
+
+ $ for node in $NODE_LIST; do ssh $user@$node "cat ~/.ssh/id_dsa.pub" >> ~/.ssh/authorized_keys; done
+
+## Copy Files to All Nodes in the Instance
+In this step, you copy the **```~/.ssh/authorized_keys```** and **```~/.ssh/known_host```** files to all other nodes in the instance. Use the following commands to copy the files to all nodes in the instance '''except''' the master node:
+
+ $ my_node=$(echo $HOSTNAME | cut -d '.' -f 1)
+ $ for node in $NODE_LIST; do if [ $node <> $my_node ]; then scp ~/.ssh/authorized_keys ~/.ssh/known_hosts $user@$node:~/.ssh/.; fi; done
+
+## Add ```localhost``` key to each node's ```~/.ssh/known_hosts file```
+In this step, you add the public key for **```localhost```** to the **```~/.ssh/known_hosts```** file
+
+ $ for node in $NODE_LIST; do ssh $user@$node "echo localhost $(cat /etc/ssh/ssh_host_rsa_key.pub) >> ~/.ssh/known_hosts"; done
+
+## Turn on ```NoHostAuthenticationForLocalhost```
+In this step, you turn the **```NoHostAuthenticationForLocalhost```** on in each node in the instance.
+
+ $ for node in $NODE_LIST; do ssh $user@$node "echo "NoHostAuthenticationForLocalhost=yes" >> ~/.ssh/config"; done
+
+## Secure the Files for Passwordless ```ssh``` Access
+In this step, you change the security of the **```~/.ssh/authorized_keys```** file and the **```~/.ssh```** directory so that passwordless ssh will be allowed. Use the following commands for each node of the instance:
+
+ $ for node in $NODE_LIST; do ssh $user@$node "chmod 755 ~/.ssh; chmod 600 ~/.ssh/authorized_keys; cd ~/.ssh; chmod 700 .."; done
+
+## Validate Passwordless ssh Access
+Test by starting a remote shell on the different nodes in the instance — no password should be necessary. Be sure to check **```ssh```** access to the node itself as well. Use the following command string to check that you can reach each node in the instance without having to provide a password:
+
+ $ for node in $NODE_LIST; do ssh $user@$node "ls -al /etc/passwd"; done
+
+Try the validation command string from all or some nodes in the instance.
+
+# Additional Information
+Passwordless ssh isn't considered secure in some installations. We don't have a solution for this situation yet.
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/performance.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/performance.md b/docs/src/site/markdown/performance.md
new file mode 100644
index 0000000..3151472
--- /dev/null
+++ b/docs/src/site/markdown/performance.md
@@ -0,0 +1,15 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page will provide information about Trafodion performance characteristics.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/port-assignment.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/port-assignment.md b/docs/src/site/markdown/port-assignment.md
new file mode 100644
index 0000000..de27501
--- /dev/null
+++ b/docs/src/site/markdown/port-assignment.md
@@ -0,0 +1,134 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+The following table lists the default ports used by the different Trafodion components plus the configuration file and configuration attribute associated with each port setting.
+
+<table>
+ <tr>
+ <th>Default Port</th>
+ <th>Configuration File</th>
+ <th>Configuration Entry</th>
+ <th>Required</th>
+ <th>Range</th>
+ <th>Protocol</th>
+ <th>Comment</th>
+ </tr>
+ <tr>
+ <td><strong>4200</strong></td>
+ <td><code>rest-site.xml</code></td>
+ <td><code>trafodion.rest.port</code></td>
+ <td>Yes</td>
+ <td>1</td>
+ <td>REST</td>
+ <td>Trafodion REST Server.</td>
+ </tr>
+ <tr>
+ <td><strong>4201</strong></td>
+ <td><code>rest-site.xml</code></td>
+ <td><code>trafodion.rest.https.port</code></td>
+ <td>Yes</td>
+ <td>1</td>
+ <td>HTTPS</td>
+ <td>Trafodion REST Server (HTTPS).</td>
+ </tr>
+ <tr>
+ <td><strong>23400</strong></td>
+ <td><code>dcs-site.xml</code></td>
+ <td><code>dcs.master.port</code></td>
+ <td>Yes</td>
+ <td>n</td>
+ <td>binary</td>
+ <td>Start of Trafodion DCS port range. (37800 for Trafodion 1.1)</td>
+ </tr>
+ <tr>
+ <td><strong>24400</strong></td>
+ <td><code>dcs-site.xml</code></td>
+ <td><code>dcs.master.info.port</code></td>
+ <td>Yes</td>
+ <td>1</td>
+ <td>HTTP</td>
+ <td>DCS master web GUI. (40010 for Trafodion 1.1)</td>
+ </tr>
+ <tr>
+ <td><strong>24410</strong></td>
+ <td><code>dcs-site.xml</code></td>
+ <td><code>dcs.server.info.port</code></td>
+ <td>Yes</td>
+ <td>n</td>
+ <td>HTTP</td>
+ <td>Start of range for DCS server web GUIs. (40020 for Trafodion 1.1)</td>
+ </tr>
+ <tr>
+ <td><strong>50030</strong></td>
+ <td><code>mapred-site.xml</code></td>
+ <td><code>mapred.job.tracker.http.address</code></td>
+ <td>No</td>
+ <td>1</td>
+ <td>HTTP</td>
+ <td>MapReduce Job Tracker web GUI.</td>
+ </tr>
+ <tr>
+ <td><strong>50070</strong></td>
+ <td><code>hdfs-site.xml</code></td>
+ <td><code>dfs.http.address</code></td>
+ <td>No</td>
+ <td>1</td>
+ <td>HTTP</td>.
+ <td>HDFS Name Node web GUI.</td>
+ </tr>
+ <tr>
+ <td><strong>50075</strong></td>
+ <td><code>hdfs-site.xml</code></td>
+ <td><code>dfs.datanode.http.address</code></td>
+ <td>No</td>
+ <td>1</td>
+ <td>HTTP</td>.
+ <td>HDFS Data Node web GUI.</td>
+ </tr>
+ <tr>
+ <td><strong>50090</strong></td>
+ <td><code>hdfs-site.xml</code></td>
+ <td><code>dfs.secondary.http.address</code></td>
+ <td>No</td>
+ <td>1</td>
+ <td>HTTP</td>.
+ <td>HDFS Secondary Name Node web GUI.</td>
+ </tr>
+ <tr>
+ <td><strong>60010</strong></td>
+ <td><code>hbase-site.xml</code></td>
+ <td><code>hbase.master.info.port</code></td>
+ <td>No</td>
+ <td>1</td>
+ <td>HTTP</td>.
+ <td>HBase Master web GUI.</td>
+ </tr>
+ <tr>
+ <td><strong>60030</strong></td>
+ <td><code>hbase-site.xml</code></td>
+ <td><code>hbase.regionserver.info.port</code></td>
+ <td>No</td>
+ <td>1</td>
+ <td>HTTP</td>.
+ <td>HBase Region Server web GUI.</td>
+ </tr>
+</table>
+
+<div class="alert alert-dismissible alert-info">
+ <button type="button" class="close" data-dismiss="alert">&close;</button>
+ <p style="color:black">There are two port ranges used by Trafodion. <ul><li style="color:black">23400 is a range, to allow multiple mxosrvr processes on each node. Allow a range of a few ports, enough to cover all the servers per node that are listed in the "servers" file in the DCS configuration directory.</li> <li style="color:black">24410 is a range as well, enough to cover the DCS servers per node, usually 1 or 2.</li></ul></p>
+<p style="color:black">If you use Trafodion 1.1, then the older port numbers are 37800 and 40010.</p>
+<p style="color:black">On top of that you would need the ports required by your Hadoop distribution. Most of this information comes from a script to sand-box a development install, including the major ports used. The script's name is <strong><code>trafodion/core/sqf/sql/scripts/install_local_hadoop</code></strong>.</p>
+ <p style="color:black">Although not all the ports will be used on every node of the cluster, you would need to open most of them for all the nodes in the cluster that have Trafodion, HBase or HDFS servers on them.</p>
+</div>
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/presentations.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/presentations.md b/docs/src/site/markdown/presentations.md
new file mode 100644
index 0000000..911c6a3
--- /dev/null
+++ b/docs/src/site/markdown/presentations.md
@@ -0,0 +1,18 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+
+Presentation | Description
+-----------------------------------------------------------|----------------------------------------------------
+**[DTM Architecture](presentations/dtm-architecture.pdf)** | In-depth descriptions of the Trafodion Distributed Transaction Management service.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/quickstart.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/quickstart.md b/docs/src/site/markdown/quickstart.md
new file mode 100644
index 0000000..2a8e1f4
--- /dev/null
+++ b/docs/src/site/markdown/quickstart.md
@@ -0,0 +1,15 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page will describe how to get going with Trafodion.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/release-notes-0-8-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-0-8-0.md b/docs/src/site/markdown/release-notes-0-8-0.md
new file mode 100644
index 0000000..a6c020b
--- /dev/null
+++ b/docs/src/site/markdown/release-notes-0-8-0.md
@@ -0,0 +1,165 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+This is the initial source-only release of the Apache Trafodion (incubating) project.
+
+Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+
+# Supported Platforms
+The following platforms are supported in this release.
+
+<span>
+ <table>
+ <tr>
+ <td>**Operating Systems**</td>
+ <td>CentOS 6.5 -- 6.7</td>
+ </tr>
+ <tr>
+ <td>**Hadoop Distributions**</td>
+ <td>Hortonworks distribution HDP 2.0</td>
+ </tr>
+ <tr>
+ <td>**Java Version**</td>
+ <td>JDK 1.7.0_67 or newer</td>
+ </tr>
+ <tr>
+ <td>**HBase Version**</td>
+ <td>HBase 0.94.x</td>
+ </tr>
+ </table>
+</span>
+
+# Enhancements
+
+This release contains the following new features.
+
+<span>
+ <table>
+ <tr>
+ <th>Category</th>
+ <th>Feature</th>
+ <th>Defect ID</th>
+ </tr>
+ <tr>
+ <td>**SQL**</td>
+ <td>
+ <ul>
+ <li>Foreign key (referential integrity), check, and unique constraints in addition to primary key and not null constraints.</li>
+ <li>Stored Procedures in Java (SPJs) (not yet fully tested).</li>
+ <li>User-Defined Functions (UDFs) written in C (not yet fully tested).</li>
+ <li>ACID properties apart from failure recovery.</li>
+ <li>Transactional atomicity and consistency provided by the standard two-phased commit protocol with presumed abort semantics, supporting commit and rollback.</li>
+ <li>Serializability based on a Multi-Version Concurrency Control (MVCC) algorithm in HBase-trx.</li>
+ <li>Distributed/global transaction support across the cluster, including transaction propagation between SQL components.</li>
+ <li>Support for multithreaded SQL clients.</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ </table>
+</span>
+
+# Fixes
+
+## 0.8.0
+Fixes to the Trafodion ODBC driver for Windows and the installer, which handles the installation of the Trafodion software. This release also includes performance fixes and cleanup to the Trafodion software code.
+
+## 0.8.1
+Release 0.8.1 provides these fixes to the Trafodion installer:
+
+* An updated license agreement in the installer.
+* Fix to the installation problem noted in [Launchpad Question #250671](https://answers.launchpad.net/trafodion/+question/250671).
+
+## 0.8.2
+Release 0.8.2 has a corrected license file in the installer.
+
+## 0.8.3
+Release 0.8.3 contains fixes to more than 35 critical and high defects, which were filed through [Launchpad](https://bugs.launchpad.net/trafodion/), and includes some performance enhancements based on DC and YCSB benchmarks. Native Expressions and Transaction Manager Recovery were disabled in order to avoid two critical issues. Those issues will be addressed in an upcoming release.
+
+# Known Issues
+
+## sqlci prints no banner or prompt when used in a su session
+
+**Defect:** [1329001](https://bugs.launchpad.net/trafodion/+bug/1329001)
+
+**Symptom:** <code>sqlci</code> hangs and is missing output after “<code>su</code>” command.
+
+**Cause:** The <code>sqlci</code> program may appear hung (producing no output) when you use the “<code>su</code>” command to switch to another user. This is caused by a permission problem in Linux, making the standard output of <code>sqlci</code> disappear.
+
+**Solution:** There are two possible workarounds:
+
+1. Create a new session for the changed user; for example: with the <code>ssh</code> or <code>xterm</code> commands, or
+2. Invoke the program like this: <code>sqlci | cat</code>
+
+## Getting TM error 97 when tables split or get moved
+
+**Defect:** [1274651](https://bugs.launchpad.net/trafodion/+bug/1274651)
+
+**Symptom:** HBase Region Splits, Load Balancing, and Error 97.
+
+**Cause:** As part of an HBase environment’s ongoing operations (and based on the policies configured for the HBase environment), an HBase region can either get split (into two daughter regions) or moved to a different region server. (Please see the blog: [http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/](http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/).) If that happens when a Trafodion transaction is active (and operates on rows within the region that is being split or load-balanced), then a subsequent transaction commit operation by the application might encounter an error 97. Please note that under such conditions the Trafodion Transaction Manager will abort the transaction and will preserve the integrity of the database.
+
+**Solution:** To minimize disruptions when this happens, we suggest that you use one or more of the following approaches:
+
+<ol>
+ <li>Enhance your JDBC application logic to retry when an error 97 is returned for a commit operation.</li>
+ <li>Update the HBase configuration to reduce the times when such disruptions happen. It involves updates to some properties that can be set in <code>hbase-site.xml</code> (or via the manageability interface of your Hadoop distribution).</li>
+ <ul>
+ <li>Set the maximum file size of an HBase Region to 100 GB. For example, set the value of the property <code>hbase.hregion.max.filesize</code> to <code>107374182400</code>.</li>
+ <li><p>Set the HBase region split policy to '<code>ConstantSizeRegionSplitPolicy</code>'. For example, set the value of the property <code>hbase.regionserver.region.split.policy</code> to <code>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</code>.</p>
+ <p><strong>NOTE</strong>: The split policy should already be set to '<code>onstantSizeRegionSplitPolicy</code>' by the Trafodion installer.</p>
+ <p><strong>Summary</strong></p>
+ <p>
+ <span>
+ <table>
+ <tr>
+ <th>Property</th>
+ <th>Value</th>
+ </tr>
+ <tr>
+ <td><code>hbase.hregion.max.filesize</code></td>
+ <td><code>107374182400</code></td>
+ </tr>
+ <tr>
+ <td><code>hbase.regionserver.region.split.policy</code></td>
+ <td><code>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</code></td>
+ </tr>
+ </table>
+ </span>
+ More information: [http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/](http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/)
+ </p>
+ </li>
+ </ul>
+ <li><p>Disable HBase Region Load Balancing. Use the HBase shell command balance_switch false to disable the movement of a region from one server to another.</p>
+ <p><strong>Example</strong></p>
+ <pre>
+hbase shell
+hbase(main):002:0> balance_switch false
+true -- Output will be the last setting of the balance_switch value
+0 row(s) in 0.0080 seconds
+ </pre>
+ </li>
+ <li>
+ Pre-split the table into multiple regions by using the <code>SALT USING n PARTITIONS</code> clause when creating the table. The number of partitions that you specify could be a function of the number of region servers present in the HBase cluster. Here is a simple example in which the table INVENTORY is pre-split into four regions when created:
+ <pre>
+CREATE TABLE INVENTORY
+ (
+ ITEM_ID INT UNSIGNED NO DEFAULT NOT NULL
+ , ITEM_TYPE INT UNSIGNED NO DEFAULT NOT NULL
+ , ITEM_COUNT INT UNSIGNED NO DEFAULT NOT NULL
+ , PRIMARY KEY (ITEM_ID ASC)
+ ) SALT USING 4 PARTITIONS
+ ; </pre>
+ </li>
+</ol>
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/release-notes-0-9-0.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/release-notes-0-9-0.md b/docs/src/site/markdown/release-notes-0-9-0.md
new file mode 100644
index 0000000..a8f0757
--- /dev/null
+++ b/docs/src/site/markdown/release-notes-0-9-0.md
@@ -0,0 +1,210 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+This is the source-only release of the Apache Trafodion (incubating) project. This release provides support for HBase 0.98 and many new product features.
+
+Build instructions are available [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61316378).
+
+# Supported Platforms
+The following platforms are supported in this release.
+
+<span>
+ <table>
+ <tr>
+ <td>**Operating Systems**</td>
+ <td>CentOS 6.5 -- 6.7</td>
+ </tr>
+ <tr>
+ <td>**Hadoop Distributions**</td>
+ <td>Cloudera CDH distribution 5.1 and Hortonworks distribution HDP 2.1</td>
+ </tr>
+ <tr>
+ <td>**Java Version**</td>
+ <td>JDK 1.7.0_67 or newer</td>
+ </tr>
+ <tr>
+ <td>**HBase Version**</td>
+ <td>HBase 0.98.x</td>
+ </tr>
+ </table>
+</span>
+
+# Enhancements
+
+This release contains the following new features.
+
+<span>
+ <table>
+ <tr>
+ <th>Category</th>
+ <th>Feature</th>
+ <th>Defect ID</th>
+ </tr>
+ <tr>
+ <td>**Performance**</td>
+ <td>
+ <ul>
+ <li>Move to HBase 0.98.</li>
+ <li>Significant improvements in benchmarks over Trafodion 0.8.3:</li>
+ <ul>
+ <li>YCSB</li>
+ <li>Debit/Credit</li>
+ <li>Order Entry</li>
+ <li>Atomics</li>
+ </ul>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Infrastructure and High Availability**</td>
+ <td>
+ <ul>
+ <li>Support on newer Hadoop distributions:
+ <ul>
+ <li>Cloudera CDH 5.1</li>
+ <li>Hortonworks HDP 2.1</li>
+ </ul>
+ </li>
+ <li>Better integration with HBase:
+ <ul>
+ <li>Use of coprocessors</li>
+ <li>Use of HLOG (HBase Write Ahead Log)</li>
+ </ul>
+ </li>
+ <li>Recovery from catastrophic HBase failures.</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Database and Query Performance**</td>
+ <td>
+ <ul>
+ <li>Improvement in scan performance:
+ <ul>
+ <li>Tuning Degree of Parallelism</li>
+ <li>Tuning scan buffer size</li>
+ </ul>
+ </li>
+ <li>Prefetch</li>
+ <li>Enhancements in JNI interface</li>
+ <li>Improved partitioning for salted tables</li>
+ <li>Push down predicates to HBase layer</li>
+ <li>Enhancement in data movement/message traffic by sending compressed (internal format) data from one operator to another</li>
+ <li>Improved memory usage</li>
+ <li>Improvements to query compile time through embedded compilers</li>
+ <li>Improvements in performance of update statistics feature</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Database Movement and Connectivity**</td>
+ <td>
+ <ul>
+ <li>Bulk Loader</li>
+ <li>Support for compression in ODBC drivers</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Security**</td>
+ <td>
+ <ul>
+ <li>Support for Grant/Revoke</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td>**Stability**</td>
+ <td>
+ <ul>
+ <li>Fixes for 140+ defects.</li>
+ </ul>
+ </td>
+ <td></td>
+ </tr>
+ </table>
+</span>
+
+# Fixes
+
+This release contains fixes to 140 defects. Those defects were filed through [Launchpad](https://launchpad.net/trafodion/+milestone/r1.1).
+
+# Known Issues
+
+## Getting TM error 97 when tables split or get moved
+
+**Defect:** [1274651](https://bugs.launchpad.net/trafodion/+bug/1274651)
+
+**Symptom:** HBase Region Splits, Load Balancing, and Error 97.
+
+**Cause:** As part of an HBase environment’s ongoing operations (and based on the policies configured for the HBase environment), an HBase region can either get split (into two daughter regions) or moved to a different region server. (Please see the blog: [http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/](http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/).) If that happens when a Trafodion transaction is active (and operates on rows within the region that is being split or load-balanced), then a subsequent transaction commit operation by the application might encounter an error 97. Please note that under such conditions the Trafodion Transaction Manager will abort the transaction and will preserve the integrity of the database.
+
+**Solution:** To minimize disruptions when this happens, we suggest that you use one or more of the following approaches:
+
+<ol>
+ <li>Enhance your JDBC application logic to retry when an error 97 is returned for a commit operation.</li>
+ <li>Update the HBase configuration to reduce the times when such disruptions happen. It involves updates to some properties that can be set in <code>hbase-site.xml</code> (or via the manageability interface of your Hadoop distribution).</li>
+ <ul>
+ <li>Set the maximum file size of an HBase Region to 100 GB. For example, set the value of the property <code>hbase.hregion.max.filesize</code> to <code>107374182400</code>.</li>
+ <li><p>Set the HBase region split policy to '<code>ConstantSizeRegionSplitPolicy</code>'. For example, set the value of the property <code>hbase.regionserver.region.split.policy</code> to <code>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</code>.</p>
+ <p><strong>NOTE</strong>: The split policy should already be set to '<code>onstantSizeRegionSplitPolicy</code>' by the Trafodion installer.</p>
+ <p><strong>Summary</strong></p>
+ <p>
+ <span>
+ <table>
+ <tr>
+ <th>Property</th>
+ <th>Value</th>
+ </tr>
+ <tr>
+ <td><code>hbase.hregion.max.filesize</code></td>
+ <td><code>107374182400</code></td>
+ </tr>
+ <tr>
+ <td><code>hbase.regionserver.region.split.policy</code></td>
+ <td><code>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</code></td>
+ </tr>
+ </table>
+ </span>
+ More information: [http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/](http://hortonworks.com/blog/apache-hbase-region-splitting-and-merging/)
+ </p>
+ </li>
+ </ul>
+ <li><p>Disable HBase Region Load Balancing. Use the HBase shell command balance_switch false to disable the movement of a region from one server to another.</p>
+ <p><strong>Example</strong></p>
+ <pre>
+hbase shell
+hbase(main):002:0> balance_switch false
+true -- Output will be the last setting of the balance_switch value
+0 row(s) in 0.0080 seconds
+ </pre>
+ </li>
+ <li>
+ Pre-split the table into multiple regions by using the <code>SALT USING n PARTITIONS</code> clause when creating the table. The number of partitions that you specify could be a function of the number of region servers present in the HBase cluster. Here is a simple example in which the table INVENTORY is pre-split into four regions when created:
+ <pre>
+CREATE TABLE INVENTORY
+ (
+ ITEM_ID INT UNSIGNED NO DEFAULT NOT NULL
+ , ITEM_TYPE INT UNSIGNED NO DEFAULT NOT NULL
+ , ITEM_COUNT INT UNSIGNED NO DEFAULT NOT NULL
+ , PRIMARY KEY (ITEM_ID ASC)
+ ) SALT USING 4 PARTITIONS
+ ; </pre>
+ </li>
+</ol>
[5/8] incubator-trafodion git commit: Merge branch 'master' of
git://git.apache.org/incubator-trafodion into TRAFODION-1507
Posted by db...@apache.org.
Merge branch 'master' of git://git.apache.org/incubator-trafodion into TRAFODION-1507
Redone website.
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/commit/0bfd3797
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/tree/0bfd3797
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/diff/0bfd3797
Branch: refs/heads/master
Commit: 0bfd3797781b1eb8a3b9119bd8578180a83b3029
Parents: 286a6e5 0b7112f
Author: Gunnar Tapper <gt...@esgyn.local>
Authored: Mon Dec 7 14:56:40 2015 -0700
Committer: Gunnar Tapper <gt...@esgyn.local>
Committed: Mon Dec 7 14:56:40 2015 -0700
----------------------------------------------------------------------
.../dcs/master/listener/ConnectReply.java | 75 +++++++++-----------
.../org/trafodion/dcs/servermt/ServerUtils.java | 20 +++---
.../servermt/serverHandler/ServerHandler.java | 2 +
3 files changed, 44 insertions(+), 53 deletions(-)
----------------------------------------------------------------------
[7/8] incubator-trafodion git commit: [TRAFODION-1507] Populated
merge.md, added a placeholder page for installation troubleshooting.
Posted by db...@apache.org.
[TRAFODION-1507] Populated merge.md, added a placeholder page for
installation troubleshooting.
Jenkins, skip test
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/commit/b033d335
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/tree/b033d335
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/diff/b033d335
Branch: refs/heads/master
Commit: b033d3352ac987c2c02a5a92357f4604a2aad1ce
Parents: 731a5c7
Author: Gunnar Tapper <gt...@esgyn.local>
Authored: Mon Dec 7 20:33:50 2015 -0700
Committer: Gunnar Tapper <gt...@esgyn.local>
Committed: Mon Dec 7 20:33:50 2015 -0700
----------------------------------------------------------------------
docs/src/site/markdown/install-troubleshoot.md | 21 ++++
docs/src/site/markdown/merge.md | 127 +++++++++++++++++++-
2 files changed, 147 insertions(+), 1 deletion(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/b033d335/docs/src/site/markdown/install-troubleshoot.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/install-troubleshoot.md b/docs/src/site/markdown/install-troubleshoot.md
new file mode 100644
index 0000000..e4b96d0
--- /dev/null
+++ b/docs/src/site/markdown/install-troubleshoot.md
@@ -0,0 +1,21 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+If you follow the [installation](install.html) instructions, then Trafodion should start up correctly. However, since each system has a somewhat different setup, you may encounter problems during or after an install.
+
+This page describes how Trafodion objects are set up, what CLASSPATHs and objects are required, and related topics. It also lists common installation problems and their solutions.
+
+TBD.
+
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/b033d335/docs/src/site/markdown/merge.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/merge.md b/docs/src/site/markdown/merge.md
index 5cad622..ed91a75 100644
--- a/docs/src/site/markdown/merge.md
+++ b/docs/src/site/markdown/merge.md
@@ -12,4 +12,129 @@
limitations under the
License.
-->
-This page will describe the committer work flow for git merges.
\ No newline at end of file
+This page describes how a committer merges changes into the git repository.
+
+Additional information about the Apache committer process can be found on the [Git at the Apache Software Foundation](https://git-wip-us.apache.org/) page.
+
+# Initial Set Up
+
+<table>
+ <tr>
+ <th width="15%">Step</th>
+ <th width="35%">Task</th>
+ <th width="50%">How-To</th>
+ </tr>
+ <tr>
+ <td><strong>Configure git E-Mail</strong></td>
+ <td>Configure <strong><code>git</code></strong> to use your Apache e-mail address.</td>
+ <td><pre>git config --global user.email myusername@apache.org</pre></td>
+ </tr>
+ <tr>
+ <td><strong>Check <code>trafodion-contributors</code> group</strong></td>
+ <td>Check that your github user is a <strong>public</strong> member in the <strong><code>trafodion-contributors</code></strong> group. This allows some permissions with the Jenkins test server.</td>
+ <td><a href="https://github.com/orgs/trafodion-contributors/people">https://github.com/orgs/trafodion-contributors/people</a></td>
+ </tr>
+ <tr>
+ <td><strong>Set Up Work Space</strong></td>
+ <td>Set up your work space so that you can merge pull requests.</td>
+ <td>
+ <ul>
+ <li>In VNC/Gnome environment, either add to <strong><code>.bashrc</code></strong> or type at your current shell: <pre>unset SSH_ASKPASS</pre></li>
+ <li>Pushing code to the Apache repository requires password authentication.</li>
+ <li>Ensure that your work space is cloned from github: <pre>git clone https://github.com/apache/incubator-trafodion</pre></li>
+ <li>Ensure that you have a remote pointing to the Apache repo. (Setting only the push URL with username does not seem to work.) <pre>git remote add apache https://USERNAME@git-wip-us.apache.org/repos/asf/incubator-trafodion.git</pre></li>
+ </ul>
+ </td>
+ </tr>
+</table>
+
+# Automated Testing
+You can interact with Jenkins testing via pull request (PR) comments. All of these commands should start with "jenkins," to not confuse other users. You can add more to the end of the message if you want. Jenkins just pattern matches the string, and will ignore trailing comments.
+
+* If an unknown user submits a PR, then Jenkins automation will post a message to github asking if it is okay to test.
+ * Review the pull request. If the code is not malicious and is okay to test, post a comment <pre>jenkins, ok</pre>
+
+* If the author is a trusted contributor, you can add them to a white-list of known users.
+ * Post a comment <pre>jenkins, add user</pre>
+
+* Consider inviting them to the **```trafodion-contributors```** github group as well.
+ * New commits to the PR will trigger a new build. You can also trigger a retest without a new commit.
+ * Post a comment <pre>jenkins, retest</pre>
+
+# Validate Review Criteria
+The project committee (PPMC) has agreed that the following review criteria are used for contributions:
+
+* Code Review(s)
+* Time available for comments
+* Testing
+ * **Be sure that you wait for all pending tests!**
+ * New commits, even those that are just merging with latest master branch, trigger new test run.
+* Legal
+* Other
+
+# Merge Pull Request
+Use the following procedure to merge a pull request.
+
+<table>
+ <tr>
+ <th width="15%">Step</th>
+ <th width="35%">Task</th>
+ <th width="50%">Commands</th>
+ </tr>
+ <tr>
+ <td><strong>Check Status</strong></td>
+ <td>
+ <p>Check the pull request status on github, at the bottom of the pull request page. It will tell you if there are any merge conflicts with master branch.</p>
+ <p><strong>NOTE</strong></p>
+ <p>If there are conflicts, either ask the contributor to merge up, or be prepared to resolve the conflicts yourself.</p>
+ </td>
+ <td></td>
+ </tr>
+ <tr>
+ <td><strong>Create Local Merge Branch</strong></td>
+ <td>Create a local merge branch, based on the latest, greatest.</td>
+ <td><pre># You will be prompted for your Apache password
+git fetch apache
+git checkout -b mrg_12345 apache/master</pre></td>
+ </tr>
+ <tr>
+ <td><strong>Fetch Pull Request Branch</strong></td>
+ <td>Fetch pull request branch to default destination <strong><code>FETCH_HEAD</code></strong></td>
+ <td><pre>git fetch origin +refs/pull/12345/head</pre></td>
+ </tr>
+ <tr>
+ <td><strong>Merge Locally</strong></td>
+ <td>Merge locally, giving message that includes JIRA ID.</td>
+ <td>
+ <p><pre>git merge --no-ff -m "Merge [TRAFODION-XYZ] PR-12345 Whizbang feature" \
+FETCH_HEAD</pre></p>
+ <p><strong>NOTES</strong></p>
+ <ul>
+ <li>Sometimes you might want to squash their branch into a single commit. If so, add the <strong><code>--squash</code></strong> option.</li>
+ <li>If you forget the <strong><code>-m</code></strong> option, you end up with a less than helpful default comment.
+ <ul>
+ <li><strong>Before you push the commit</strong>, you can fix the comment by:<pre>git commit --amend</pre></li>
+ </ul>
+ </li>
+ </ul>
+ </td>
+ </tr>
+ <tr>
+ <td><strong>Additional Checks</strong></td>
+ <td>Additional checks of what you are preparing to push.</td>
+ <td>
+ <pre>git log apache/master..HEAD
+git diff apache/master HEAD</pre></td>
+ </tr>
+ <tr>
+ <td><strong>Push Changes</strong></td>
+ <td>Push changes to the Apache repository, specifying the source and the destination branch.</td>
+ <td><pre># You will be prompted for your Apache password
+git push apache HEAD:master</pre></td>
+ </tr>
+</table>
+
+# Completion
+
+1. Close Jira, if appropriate, or ask the contributor to do so.
+2. If ASF automation does not close the pull request, ask the contributor to do so.
\ No newline at end of file
[4/8] incubator-trafodion git commit: [TRAFODION-1507] Added new
files.
Posted by db...@apache.org.
[TRAFODION-1507] Added new files.
jenkins, skip test
Project: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/commit/286a6e5c
Tree: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/tree/286a6e5c
Diff: http://git-wip-us.apache.org/repos/asf/incubator-trafodion/diff/286a6e5c
Branch: refs/heads/master
Commit: 286a6e5c1797f725c9942d6bba45540bd3c844af
Parents: 1c617ae
Author: Gunnar Tapper <gt...@esgyn.local>
Authored: Mon Dec 7 14:55:20 2015 -0700
Committer: Gunnar Tapper <gt...@esgyn.local>
Committed: Mon Dec 7 14:55:20 2015 -0700
----------------------------------------------------------------------
docs/src/site/markdown/advocate.md | 15 +
docs/src/site/markdown/build-tools-manual.md | 197 ++++++++++++
docs/src/site/markdown/build.md | 80 +++++
docs/src/site/markdown/code.md | 32 ++
.../markdown/cplusplus-coding-guidelines.md | 310 +++++++++++++++++++
.../src/site/markdown/create-dev-environment.md | 153 +++++++++
docs/src/site/markdown/develop.md | 245 +++++++++++++++
docs/src/site/markdown/document.md | 121 ++++++++
docs/src/site/markdown/documentation.md | 25 ++
docs/src/site/markdown/download.md | 36 +++
.../site/markdown/enable-secure-trafodion.md | 224 ++++++++++++++
docs/src/site/markdown/faq.md | 220 +++++++++++++
docs/src/site/markdown/install-preparation.md | 138 +++++++++
docs/src/site/markdown/install.md | 203 ++++++++++++
docs/src/site/markdown/ldapcheck.md | 41 +++
docs/src/site/markdown/ldapconfigcheck.md | 48 +++
.../src/site/markdown/manage-dev-environment.md | 51 +++
docs/src/site/markdown/management.md | 62 ++++
docs/src/site/markdown/new-features.md | 15 +
docs/src/site/markdown/passwordless-ssh.md | 131 ++++++++
docs/src/site/markdown/performance.md | 15 +
docs/src/site/markdown/port-assignment.md | 134 ++++++++
docs/src/site/markdown/presentations.md | 18 ++
docs/src/site/markdown/quickstart.md | 15 +
docs/src/site/markdown/release-notes-0-8-0.md | 165 ++++++++++
docs/src/site/markdown/release-notes-0-9-0.md | 210 +++++++++++++
docs/src/site/markdown/release-notes-1-0-0.md | 255 +++++++++++++++
docs/src/site/markdown/release-notes-1-0-1.md | 249 +++++++++++++++
docs/src/site/markdown/release-notes-1-1-0.md | 181 +++++++++++
docs/src/site/markdown/release.md | 225 ++++++++++++++
docs/src/site/markdown/roadmap.md | 15 +
.../site/markdown/setup-build-environment.md | 160 ++++++++++
docs/src/site/markdown/testing.md | 179 +++++++++++
docs/src/site/markdown/tests.md | 71 +++++
.../site/markdown/traf_authentication_config.md | 96 ++++++
docs/src/site/markdown/wiki.md | 23 ++
.../site/resources/images/multi-layer-esps.png | Bin 0 -> 116303 bytes
37 files changed, 4358 insertions(+)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/advocate.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/advocate.md b/docs/src/site/markdown/advocate.md
new file mode 100644
index 0000000..425c70e
--- /dev/null
+++ b/docs/src/site/markdown/advocate.md
@@ -0,0 +1,15 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page provides how to contribute to Trafodion via advocacy. Please refer to the [Contribute](contribute.html) page for information about other ways to contribute to the Trafodion project.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/build-tools-manual.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/build-tools-manual.md b/docs/src/site/markdown/build-tools-manual.md
new file mode 100644
index 0000000..6c02481
--- /dev/null
+++ b/docs/src/site/markdown/build-tools-manual.md
@@ -0,0 +1,197 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to perform manual installs of the required [Trafodion Build Tools](setup-build-environment.html#Install_Build_Tools).
+
+In the sections below, the **```<tool installation directory>```** is the directory where you want the tool to be installed.
+
+# MPICH
+**Tested Version**: 3.0.4
+
+**Download**: http://www.mpich.org/static/downloads/3.0.4/mpich-3.0.4.tar.gz (http://www.mpich.org/downloads)
+
+**Considerations**: For more detailed instructions, see the README file that comes with the source.
+
+**Install**:
+
+ tar -xzf mpich-3.0.4.tar.gz
+ cd mpich-3.0.4
+ ./configure --prefix=<tool installation directory>/dest-mpich-3.0.4 --with-device=ch3:sock --disable-f77 --disable-fc
+ make
+ make check
+ make install
+
+**```<tool installation directory>```** is the directory where you want MPICH to be installed. If you do not specify the **```--prefix```** option, the default location is **```/usr/local``**.
+
+# Bison
+**Tested Version**: 3.0
+
+**Download**: http://ftp.gnu.org/gnu/bison/bison-3.0.tar.gz (http://ftp.gnu.org/gnu/bison/)
+
+**Considerations**: Refer to the bison INSTALL file for detailed instructions.
+
+**Determine Bison Version**:
+
+ which bison
+ bison --version
+
+If the version is older than 3.0, then do the following:
+
+ tar -xzf bison-3.0.tar.gz
+ cd bison-3.0
+ ./configure --prefix=<tool installation directory>/bison_3_linux
+ make
+ make check
+ make install
+
+**Note**: The **```make check```** step may return errors like the following that can be ignored:
+
+ make[3]: Entering directory `<mydir>/bison-3.0'
+ YACC examples/calc++/calc++-parser.stamp
+ CXX examples/calc++/examples_calc___calc__-calc++-driver.o
+ LEX examples/calc++/calc++-scanner.cc
+ CXX examples/calc++/examples_calc___calc__-calc++-scanner.o
+ g++: ./examples/calc++/calc++-scanner.cc: No such file or directory
+ g++: no input file
+
+Adjust your **```PATH```** to ensure that the correct version is chosen. Rerun the **```bison --version```** to verify.
+
+# Udis86
+**Tested Version**: 1.7.2
+
+**Download**: http://sourceforge.net/projects/udis86/files/udis86/1.7/udis86-1.7.2.tar.gz (http://udis86.sourceforge.net)
+
+**Consideration**: Udis86 is a prerequisite to building the LLVM product.
+
+**Install**:
+
+ tar xzf udis86-1.7.2.tar.gz
+ cd udis86-1.7.2
+ ./configure --prefix=<tool installation directory>/udis86-1.7.2 --enable-shared
+ make
+ make install
+
+# LLVM
+**Tested Version**: 3.2
+
+**Download**: http://llvm.org/releases/3.2/llvm-3.2.src.tar.gz (http://llvm.org/releases/download.html)
+
+**Consideration**: Udis86 must be installed on the system before LLVM is built and installed. Building LLVM takes some time to complete, be patient.
+
+**Install**:
+
+ # Set BASE_DIR to the top-level directory where the LLVM source will be
+ # unpacked and the objects compiled.
+ BASE_DIR=<your-base-dir>
+ cd $BASE_DIR
+ tar xzf llvm-3.2.src.tar.gz
+
+ export MY_UDIS_INSTALL_DIR=<udis-installation-directory>/udis86-1.7.2
+ export MY_LLVM_INSTALL_DIR=<llvm-installation-directory>/dest-llvm-3.2/
+ export MY_LLVM_SRC_DIR=$BASE_DIR/llvm-3.2.src
+ export MY_LLVM_OBJ_DIR=$BASE_DIR/llvm-3.2.obj/
+ export LD_LIBRARY_PATH=$MY_UDIS_INSTALL_DIR/lib:$LD_LIBRARY_PATH
+ export C_INCLUDE_PATH=$MY_UDIS_INSTALL_DIR/include
+ export CPATH=$MY_UDIS_INSTALL_DIR/include
+
+ mkdir -p $MY_LLVM_OBJ_DIR/release
+ cd $MY_LLVM_OBJ_DIR/release
+
+ $MY_LLVM_SRC_DIR/configure --prefix=$MY_LLVM_INSTALL_DIR/release \
+ --enable-optimized --enable-jit \
+ --enable-shared --enable-targets=x86,x86_64,cpp \
+ --with-udis86=$MY_UDIS_INSTALL_DIR/lib \
+ CFLAGS=-fgnu89-inline
+
+ make libs-only
+ make install-libs
+
+ mkdir -p $MY_LLVM_OBJ_DIR/debug
+ cd $MY_LLVM_OBJ_DIR/debug
+
+ $MY_LLVM_SRC_DIR/configure --prefix=$MY_LLVM_INSTALL_DIR/debug \
+ --enable-optimized --enable-jit \
+ --enable-debug-runtime --enable-debug-symbols \
+ --enable-shared --enable-targets=x86,x86_64,cpp \
+ --with-udis86=$MY_UDIS_INSTALL_DIR/lib \
+ CFLAGS=-fgnu89-inline
+
+ make libs-only
+ make install-libs
+
+# ICU
+**Tested Version**: 4.4.0
+
+**Download**: http://download.icu-project.org/files/icu4c/4.4/icu4c-4_4-src.tgz (http://site.icu-project.org/download)
+
+**Install**:
+
+ tar -xzf icu4c-4_4-src.tgz
+ cd icu/source
+ ./runConfigureICU Linux --with-library-suffix=Nv44 --prefix=<tool installation directory>/icu4.4/linux64
+ make && make check
+ make install
+
+**Note**: The following **```make check```** errors can be ignored.
+
+ [All tests passed successfully...]
+ Elapsed Time: 00:00:12.126
+ make[2]: Leaving directory `/home/centos/icu/source/test/cintltst'
+ ---------------
+ ALL TESTS SUMMARY:
+ ok: testdata iotest cintltst
+ ===== ERRS: intltest
+ make[1]: *** [check-recursive] Error 1
+ make[1]: Leaving directory `/home/centos/icu/source/test'
+ make: *** [check-recursive] Error 2
+
+# Zookeeper
+**Tested Version**: 3.4.5
+
+**Download**: https://archive.apache.org/dist/zookeeper/zookeeper-3.4.5/zookeeper-3.4.5.tar.gz
+
+**Install**:
+
+ tar -xzf zookeeper-3.4.5.tar.gz
+ cd zookeeper-3.4.5/src/c
+ ./configure --prefix=<tool installation directory>/zookeeper-3.4.5
+ make
+ make install
+
+# Thrift
+**Tested Version**: 0.9.0
+
+**Download**: http://archive.apache.org/dist/thrift/0.9.0/
+
+**Consideration**: Behind a firewall, you may need the ant flags to specify a proxy.
+
+**Install**:
+
+ tar -xzf thrift-0.9.0.tar.gz
+ cd thrift-0.9.0
+ ./configure --prefix=<tool installation dir>/thrift-0.9.0 --without-qt
+ make
+ make install
+
+# Maven
+**Tested Version**: 3.3.3
+
+**Download**: http://archive.apache.org/dist/maven/maven-3/3.3.3/binaries/apache-maven-3.3.3-bin.tar.gz.
+
+**Considerations**: Add Maven to your **```PATH```** once it has been installed.
+
+**Install**:
+
+ tar -xzf apache-maven-3.3.3-bin.tar.gz -C <tool installation directory>
+
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/build.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/build.md b/docs/src/site/markdown/build.md
new file mode 100644
index 0000000..960b928
--- /dev/null
+++ b/docs/src/site/markdown/build.md
@@ -0,0 +1,80 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to build the Trafodion source code.
+
+# Prerequisites
+You need to [Setup Build Environment](setup-build-environment.html) before trying to build the Trafodion source code.
+
+# Download Source
+You should already have downloaded the source code when setting up the build environment.
+
+## Git
+Please refer to [Making Changes](develop.html#making_changes) on the [Develop](develop.html) page.
+
+## tar file
+The source code for Apache Trafodion can be downloaded from [Apache Trafodion Incubator Release](https://dist.apache.org/repos/dist/release/incubator) as a tar file.
+
+* Download the source tar file to your **```<trafodion download directory>```**.
+* Check the tar file validity by checking signatures, please refer to [Verify Signatures](release.html#Verify_Signatures). The Trafodion releases have been signed using The GNU Privacy Guard.
+
+**Unpack the tar file**
+
+ cd <trafodion download directory>
+ tar -xzf <tar file>
+
+# Setup Environmental Variables
+Start a new **```ssh```** session. Use the following commands to set up the Trafodion environmental variables.
+
+ cd <Trafodion source directory>
+ export TOOLSDIR=<tools installation directory>
+ source ./env.sh
+
+* **```<Trafodion source directory>```**: Source tree base for Trafodion.
+* **```<tools installation directory>```**: where Trafodion required tools are located. The following example assumes that you installed all the required tools in a single location. If you installed or used pre-installed tools in different directories, then you need to export the location of each tool as described in [Build Tools Manual Installation](build-tools-manual.html) prior to sourcing in **```env.sh```**.
+
+# Build Commands
+Build a debug version of Trafodion using one of the following options.
+
+Command | What It Builds
+------------------------------------|----------------------------------------------------------------------------------
+**```make all```** | Trafodion, DCS, and REST.
+**```make package```** | Trafodion, DCS, REST, and Client Drivers.
+**```make package-all```** | Trafodion, DCS, REST, Client Drivers, and tests for all components.
+
+If the build fails, you might want to rerun the **```make```** step. Trafodion downloads many dependencies and sometimes one of the download operations fail. Rerunning the build generally works.
+
+# Verify Build
+Use **```sqvers -u```** to verify the build.
+
+ $ sqvers -u
+ MY_SQROOT=/home/centos/apache-trafodion-1.3.0-incubating/core/sqf
+ who@host=centos@mysystem
+ JAVA_HOME=/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.91.x86_64
+ SQ_MBTYPE=64d (64-debug)
+ linux=2.6.32-504.1.3.el6.x86_64
+ redhat=6.7
+ NO patches
+ Most common Apache_Trafodion Release 1.3.0 (Build debug [centos], branch -, date 06Nov15)
+ UTT count is 1
+ [6] Release 1.3.0 (Build debug [centos], branch -, date 06Nov15)
+ export/lib/hbase-trx-cdh5_3-1.3.0.jar
+ export/lib/hbase-trx-hbase_98_4-1.3.0.jar
+ export/lib/hbase-trx-hdp2_2-1.3.0.jar
+ export/lib/sqmanvers.jar
+ export/lib/trafodion-dtm-1.3.0.jar
+ export/lib/trafodion-sql-1.3.0.jar
+
+The output from the **```sqvers -u```** commands should show several jar files. The number of files differs based on the version of Trafodion you downloaded.
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/code.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/code.md b/docs/src/site/markdown/code.md
new file mode 100644
index 0000000..71b76ab
--- /dev/null
+++ b/docs/src/site/markdown/code.md
@@ -0,0 +1,32 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how you set up the Trafodion build and development-test environment.
+
+# Supported Platforms
+Red Hat or Centos 6.x (6.4 or later) versions are supported as development and production platforms.
+
+# Setup Build Environment
+Please refer to [Setup Build Environment](setup-build-environment.html).
+
+# Build Trafodion
+Please refer to [Build Trafodion](build.html).
+
+# Setup Test Environment
+Please refer to the [Test Environment](test-environment.html) page.
+
+# Make Changes
+Please refer to [Making Changes](develop.html#Making_Changes). Ensure that you run the [Regression Tests](testing.html) before checking in changes.
+
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/cplusplus-coding-guidelines.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/cplusplus-coding-guidelines.md b/docs/src/site/markdown/cplusplus-coding-guidelines.md
new file mode 100644
index 0000000..3470641
--- /dev/null
+++ b/docs/src/site/markdown/cplusplus-coding-guidelines.md
@@ -0,0 +1,310 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+
+These are the C++ coding guidelines that are part of the acceptance criteria for code submitted to the Trafodion. Trafodion reviewers use these guidelines when reviewing changes.
+
+The guidelines describe practices that are either required or preferred. In addition, areas where there is no preference between two or more practices are described.
+
+Trafodion is composed of several distinct sub-projects, some of which have coding guidelines that differ from the Trafodion standard; for example, a requirement in most areas of the code may be only preferred in others.
+
+There may also be existing code that violates one or more of the published requirements. The intent is to correct these over time, and corrections are encouraged when changing code to make a fix or implement new functionality. However, changes that are solely coding guideline changes are not recommended since this places undue burden on the reviewers.
+
+# Header Files
+Keep **<code>#include</code>** directives to a minimum in header files.
+
+You may forward declare classes and structs when the only use within the header file is a pointer or reference. While includes should be kept to a minimum, if something is used in a header file and cannot be forward declared, it must be explicitly included.
+
+All files, headers and implementation, should include everything they need to be self-sufficient. They should never assume something will be pre-included. In other words, the contents of a header file should compile cleanly by itself. To help ensure this, all implementation files should include their respective header file first.
+
+Header files should not contain declarations for public items that are only used by the implementation file. Public items that are require in the implementation file but not the header file should be declared in the implementation file. The preference is NOT to create header files that consist only of includes of other header files.
+
+Declare as little as possible in the header file and keep as much of the actual implementation private as is reasonable. For instance, don’t include in a header file declarations of types, enums, and functions that are only referenced by the implementation file.
+
+## Including Standard Header Files
+The preference is for C++ style includes over C style includes for standard header files.
+
+ //Preferred
+ #include <cstdio>
+ //Accepted
+ #include <stdio.h>
+
+## Include Guards
+All header files must use include guards. The name of the include guard **<code>#define</code>** should be the filename in all uppercase, with underscore used in place of periods.
+
+For instance, if the header file is named **<code>ServerInterface_ODBC.h</code>**, the header file should begin and end as follows:
+
+ #ifndef SERVERINTERFACE_ODBC_H
+ #define SERVERINTERFACE_ODBC_H
+ ...
+ #endif /* SERVERINTERFACE_ODBC_H */
+
+Comments following the **<code>#endif</code>** indicating the include guard are preferred.
+
+# Variable Declaration and Naming Standards
+Trafodion uses a combination of Pascal and Camel case.
+
+* Pascal case means that the first letter in each word in an identifier is capitalized.
+* Camel case is similar except the first letter is in lower case.
+
+For both, underscores are **not** used to separate words. The general rule is that identifiers with local scope start with a lower case letter and identifiers with global scope start with an upper case letter.
+
+ //Pascal case
+ class AuthenticationMessage;
+ //Camel case (aka lower Camel case or camelCase)
+ int logonCount;
+ Class Names
+
+Class names should be Pascal case and should describe the object contents (not what it does), with as little abbreviation as possible. When names include acronyms, the acronyms should be in all upper case.
+
+**Acceptable Examples**
+
+ //Preferred
+
+ class SQLSessionContext; // an object that contains the context for a SQL session
+ class PrivilegeList; // a list of privileges
+
+**Poor Examples**
+
+ class OutputInfo; // Doesn’t describe class contents, no context
+ class ReadTableDef; // Describes what class does, not contents
+ class Cmdline_Args; // Prefer Pascal case, no underscore, for class names
+
+## Class Member Variable Names
+Private member data variables should be suffixed with an underscore and should use Camel case. When names include acronyms, the acronyms should be in all upper or all lower case, dependent on which case the first letter should be.
+
+**Example**
+
+ class Employee
+ {
+ public:
+ Employee ();
+ private:
+ std::string firstName_;
+ std::string lastName_;
+ uint16_t departmentNumber_;
+ std::string departmentName_;
+ uint32_t irsSSN_;
+ }
+
+## Function Names
+Class member functions and static file functions should use Camel case. External non-class functions should use Pascal case. Except for constructors, destructors, and operators, the function name should include a verb that describes the action the function is performing.
+
+**Good Examples**
+
+ //Class member functions
+ int32_t getSalary() const;
+ int32_t setAuthID();
+ int32_t closeAllCursors();
+
+**Bad Examples**
+
+ // Is it setting break enabled, returning it or ???
+ int32_t SQLCLI_BreakEnabled();
+
+## Enums
+Enum types should use Pascal case and describe the class of enums. If the enum is declared outside of a class, the type name should include an indication of the scope of the enums.
+
+Enums themselves should be declared as all upper case. The names may begin with a common prefix or be independent, depending on the usage.
+
+When enums represent an arbitrary set of return values (that is, error codes, state codes, etc.), then avoid the values -1, 0, and 1 if using weakly typed enums, to reduce the chance of matches with Booleans or uninitialized variables.
+
+The preference is to declare enums as strongly typed.
+
+ enum class EnumName {...};
+
+## Boolean Variables
+Boolean variables names should include a verb, state, and optionally a noun (object whose state is in question) indicating the nature of the Boolean. Any combination is acceptable, however verbState is the most common.
+
+**Good Examples**
+
+ bool isValid; // verbState
+ bool isValidTable; // verbStateNoun
+ bool tableIsDroppable; // nounVerbState
+ bool hasData; // verbState
+
+**Bad Examples**
+
+ bool valid;
+ bool tableState;
+ bool empty;
+
+Functions that return a Boolean should also have names of the form verbState or verbStateNoun if the functions return state information. (This naming standard does not apply to functions returning Boolean as indication of success or failure.)
+
+**Good Examples**
+
+ bool isValidHbaseName();
+ bool isHostNameExcluded();
+ bool canUseCbServer();
+
+**Bad Examples**
+
+ // Don’t use get for Boolean accessors
+ bool getUDRAccessModeViolation();
+
+ // Don’t use integer return for Boolean functions
+ short existsInHBase();
+
+ // Function name implies it is sending settings to the compiler, but it is
+ // actually only returning an indication that settings should be sent.
+ // A better name would be shouldSendSettingsToCompiler().
+ bool sendSettingsToCompiler();
+
+Parts of Trafodion code use one of two Boolean typedefs, **<code>NABoolean</code>** and **<code>ComBoolean</code>**, declared as follows:
+
+ typedef int Int32;
+ typedef Int32 NABoolean;
+ typedef NABoolean ComBoolean;
+ const NABoolean TRUE = (1 == 1);
+ const NABoolean FALSE = (0 == 1);
+
+Exercise care when mixing usage of bool and **<code>NABoolean</code>**/**<code>ComBoolean</code>** types, as the latter are not guaranteed to only contain values of TRUE and FALSE. The use of non-standard Boolean types is gradually being phased out.
+
+## Constants
+All constant names should be all upper case, regardless of how the constant is declared. That is, enums, defines, and variables with the **<code>const</code>** modifier should be named in all upper case.
+
+Defines, enums, and const are all permitted and used throughout Trafodion, although most code in Trafodion uses enum for numerical constants and defines for character constants.
+
+For new code, the use of const char or string is preferred for character constants instead of defines.
+
+## Namespace Names
+The preference is for namespaces to be all lower case, with preference to single words (note the exception to the rule that a name with global scope should start with an upper case).
+
+If a namespace must be dual-worded, use underscores. If mixed case names are used, Pascal case is preferred.
+
+**Examples**
+
+ //Preferred
+
+ namespace compiler
+ //Accepted
+
+ namespace Compiler
+
+# Indentation and Formatting
+## Indentation
+TAB characters are not permitted in source files except for text files (for example, makefiles) that require them.
+
+Trafodion code uses several indenting depths, including 2, 3, 4, and 8 spaces. Most common is 2 and 3.
+
+Use the style found in existing code, and when writing new code, use either 2, 3, or 4, and remain consistent.
+
+A variety of control block indentation styles are used throughout Trafodion, most commonly Allman, Whitesmith, Stroustrup, and GNU. Follow the predominant style when making small to medium changes to existing code. For new code, the Allman style is preferred.
+
+ //Allman
+ if (x > 5)
+ {
+ error = doThis(x);
+ if (error != 0)
+ {
+ return false;
+ }
+ }
+ else
+ {
+ doThat(x);
+ }
+
+ //Whitesmith
+ if (x > 5)
+ {
+ error = doThis(x);
+ if (error != 0)
+ {
+ return false;
+ }
+ }
+ else
+ {
+ doThat(x);
+ }
+
+ //Stroustrup
+ if (x > 5) {
+ error = doThis(x);
+ if (error != 0) {
+ return false;
+ }
+ }
+ else {
+ doThat(x);
+ }
+
+Note that the Stroustrup and the similar K&R formats were popularized by usage in books where conservation of line count was a goal.
+
+ //GNU
+ if (x > 5)
+ {
+ error = doThis(x);
+ if (error != 0)
+ {
+ return false;
+ }
+ }
+ else
+ {
+ doThat(x);
+ }
+
+# Comments
+## Comment Style
+C++ style comments are preferred, but C comments are acceptable as well.
+
+Some code uses Doxygen style comments, but this is not required.
+
+## When/Where Comments Should Be Used
+Every file should have a comment at the beginning describing the purpose of the file.
+
+In header files where classes are declared, there should be a comment describing the class, including purpose and usage. Also describe anything out of the ordinary, such as the use of multiple inheritance.
+
+Within implementation files, in addition to the comment at the beginning of the file, add comments for any global or static variables defined in the file, and how the variable is handled in a multi-threaded environment (if applicable).
+
+Also, for each function defined, describe the purpose and intent of the function. For each parameter, list whether it is input or output (or both), how it is used, and any range restrictions imposed. For functions not returning void, describe the possible return values.
+
+Within the body of the function, there is no need to write comments that document the obvious. But if there is any complexity to the logic, at a minimum document the intent, and consider documenting the details (assumptions, limits, unexpected side effects from function calls, etc.)
+
+If a feature is only partially implemented, add a comment indicating at a high level what work remains. Prefix the comment with //TODO.
+
+ //TODO Code is currently not thread safe. Need to protect allocation of ...
+
+# Error Handling
+## Asserts
+Trafodion uses asserts in the "debug" build. Use asserts freely, but ensure they do not contain any side effects as the code is not present in the "release" build.
+
+## Error Return/Retrieval
+Avoid the use of integer return codes for success and error codes. Instead, use bool for simple succeeded/failed and enum types for returns with multiple conditions.
+
+## Exception Handling
+Trafodion code mixes usage of exceptions and error returns. When using try/catch blocks, keep the scope as small as possible. Ensure all exceptions thrown are handled, potentially in main() if nowhere else.
+
+# General Guidelines
+## Casting
+Avoid using C-style casts. Use C++-style casts instead, as they are often safer and easier to search for.
+
+ //Preferred
+
+ int x = static_cast<int>(shortVariable);
+
+ MyType *myVar = reinterpret_cast<MyType *>(voidPtr);
+
+Don’t blindly cast to remove a compiler error or warning. Ensure the cast is safe.
+
+Use const casting sparingly. Often the use of mutable or changing a function to be const correct is a better solution.
+
+## Types
+Use standard types defined in **<code>\<cstdint\></code>** or **<code>\<stdint.h\></code>**. Note that Trafodion defines and uses many non-standard types (for example, **<code>Int32</code>**, **<code>Lng32</code>**), but this usage is being phased out.
+
+Use types with explicit sizes (for example, **<code>int32_t</code>**, **<code>int64_t</code>**) when size is a factor in the code, such as an external API, or column in a table.
+
+Where size is not a factor (counters, indexes) a non-sized type such as **<code>int</code>** or **<code>long</code>** may be used. However, in general, **<code>size_t</code>** and **<code>ssize_t</code>** are preferred for variables where fixed size is not required.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/create-dev-environment.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/create-dev-environment.md b/docs/src/site/markdown/create-dev-environment.md
new file mode 100644
index 0000000..acd840d
--- /dev/null
+++ b/docs/src/site/markdown/create-dev-environment.md
@@ -0,0 +1,153 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to create the test environment used for Trafodion development, which is intended for people that are contributing to the Trafodion source tree. Please refer to [Download](download.html) if you want to try the Trafodion product environment.
+
+# Prerequisites
+The following prerequisites need to be met in order to create a functional Trafodion test environment.
+
+## Passwordless ```ssh```
+Check to see if you have passwordless SSH setup correctly.
+
+ ssh localhost
+ Last login: Fri Nov 6 22:44:00 2015 from 192.168.1.9
+
+If the **```ssh localhost```** command prompts for a password, then passwordless **```ssh```** is not set up correctly.
+
+The following is an example of setting up passwordless **```ssh```** using **```id_rsa```** keys. You can choose the method that best represents your environment.
+
+If you already have an existing set of **```ssh```** keys. Simply copy both the **```id_rsa.pub```** and **```id_rsa```** to your **```~/.ssh```** directory.
+
+Then, do the following to modify your **```ssh```** environment.
+
+ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
+ chmod 600 ~/.ssh/id_rsa
+ echo "NoHostAuthenticationForLocalhost=yes" >>~/.ssh/config
+ chmod go-w ~/.ssh/config
+ chmod 755 ~/.ssh; chmod 640 ~/.ssh/authorized_keys; cd ~/.ssh; chmod 700 ..
+
+If you need to create your keys first, then do the following.
+
+ ssh-keygen -t rsa -N "" -f ~/.ssh/id_rsa
+ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
+ chmod 600 ~/.ssh/id_rsa.pub
+ echo "NoHostAuthenticationForLocalhost=yes" >>~/.ssh/config
+ chmod go-w ~/.ssh/config
+ chmod 755 ~/.ssh; chmod 640 ~/.ssh/authorized_keys; cd ~/.ssh; chmod 700 ..
+
+## System Limits
+Please check that the system limits in your environment are appropriate for Apache Trafodion. If they are not, then you will need to increase the limits or Trafodion cannot start.
+
+The recommended settings are as follows.
+
+ $ ulimit –a
+ core file size (blocks, -c) 1000000
+ data seg size (kbytes, -d) unlimited
+ scheduling priority (-e) 0
+ file size (blocks, -f) unlimited
+ pending signals (-i) 515196
+ max locked memory (kbytes, -l) 49595556
+ max memory size (kbytes, -m) unlimited
+ open files (-n) 32000
+ pipe size (512 bytes, -p) 8
+ POSIX message queues (bytes, -q) 819200
+ real-time priority (-r) 0
+ stack size (kbytes, -s) 10240
+ cpu time (seconds, -t) unlimited
+ max user processes (-u) 267263
+ virtual memory (kbytes, -v) unlimited
+ file locks (-x) unlimited
+
+Please refer to this [article](http://www.itworld.com/article/2693414/setting-limits-with-ulimit.html) for information on how you change system limits.
+
+# Setup
+You can create a Trafodion test environment using a:
+
+* **Pre-Installed Hadoop**: Trafodion installation on a system that already has a compatible version of Hadoop installed
+* **Local Hadoop**: You install a Hadoop environment using the **```install_local_hadoop```** script
+
+Your installation approach depends on whether you already have installed Hadoop.
+
+## Pre-Installed Hadoop
+Use the following instructions if you're installing Trafodion on a pre-installed Hadoop environment.
+### Build Binary tar Files
+Build the Trafodion binary tar files.
+
+ cd <Trafodion source directory>
+ make package
+
+### Install Trafodion
+Please refer to the installation instructions described in the [Installation](install.html) page.
+
+## Local Hadoop
+Use the following instructions if you need to install a local Hadoop environment.
+### Run ```install_local_hadoop```
+The **```install_local_hadoop```** script downloads compatible versions of Hadoop, HBase, Hive, and MySQL. Then, it starts Trafodion.
+
+<div class="alert alert-dismissible alert-info">
+ <button type="button" class="close" data-dismiss="alert">&close;</button>
+ <p style="color:black"><strong>Time Saver</strong></p>
+ <p style="color:black"><strong>```install_local_hadoop```</strong> downloads Hadoop, HBase, Hive, and MySql jar files from the Internet. To avoid this overhead, you can download the required files into a separate directory and set the environment variable <strong>```MY_LOCAL_SW_DIST```</strong> to point to this directory.</p>
+</div>
+
+Command | Usage
+-----------------------------------------------|--------------------------------------------------------
+**```install_local_hadoop```** | Uses default ports for all services.
+**```install_local_hadoop -p fromDisplay```** | Start Hadoop with a port number range determined from the DISPLAY environment variable.
+**```install_local_hadoop -p rand```** | Start with any random port number range between 9000 and 49000.
+**```install_local_hadoop -p <port>```** | Start with the specified port number.
+
+For a list of ports that get configured and their default values, please refer to [Port Assignments](port-assignments.html).
+
+### Sample Procedure
+Start a new **```ssh```** session and ensure that the Trafodion environmental variables are loaded.
+
+ cd <Trafodion source directory>
+ source ./env.sh
+
+Install the Hadoop software.
+
+ cd $MY_SQROOT/sql/scripts
+ install_local_hadoop
+ ./install_traf_components
+
+Verify installation.
+
+ $ swstatus
+ 6 java servers and 2 mysqld processes are running
+ 713 NameNode
+ 19513 HMaster
+ 1003 SecondaryNameNode
+ 838 DataNode
+ 1173 ResourceManager
+ 1298 NodeManager
+
+Six java servers as shown above and two mysqld processes should be running.
+
+# Install and Build Trafodion
+Please refer to [Modify Code](code.html) for information on how to install and build Trafodion from its source code.
+
+# New Source Download
+You need to do the following each time you download new source code.
+
+ cd <Trafodion source directory>
+ source ./env.sh
+ cd $MY_SQROOT/etc
+ # delete ms.env, if it exists
+ rm ms.env
+ cd $MY_SQROOT/sql/scripts
+ sqgen
+
+# Manage
+Please refer to [Manage Development Environment](manage-dev-environment) for instructions.
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/develop.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/develop.md b/docs/src/site/markdown/develop.md
new file mode 100644
index 0000000..79656d8
--- /dev/null
+++ b/docs/src/site/markdown/develop.md
@@ -0,0 +1,245 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to help develop the Trafodion source tree. Please refer to the [Contribute](contribute.html) page for information about other ways to contribute to the Trafodion project.
+
+# Prerequisites
+You need to register as a Trafodion contributor before you can help us develop Trafodion. Please perform the following registration actions:
+
+<table>
+ <tr>
+ <th style="width:30%;">Area</th>
+ <th style="width:55%;">Notes</th>
+ <th style="width:15%;">URL</th>
+ </tr>
+ <tr>
+ <td><strong>Individual Contributor License Agreement (ICLA)</strong></td>
+ <td>You should sign the ICLA before contributing content to the Trafodion source tree. (Required to become a committer.)</td>
+ <td><a href="https://www.apache.org/licenses/icla.txt" target="_blank">ICLA Agreement</a><br />
+ <a href="http://www.apache.org/licenses/" target="_blank">Approval Process</a>
+ </td>
+ </tr>
+ <tr>
+ <td><strong>Source Control</strong></td>
+ <td>You must have a git account in order to contribute to the Trafodion source. If you haven't already done so, please join git.</td>
+ <td><a href="https://github.com/join" target="_blank">Git Signup</a></td>
+ </tr>
+ <tr>
+ <td><strong>Defect Tracking</strong></td>
+ <td>In order to have certain permissions, including assigning issues to yourself, you need to be a Contributor in the project. Be sure to sign up for a JIRA account if you don't have one.</td>
+ <td><a href="https://issues.apache.org/jira/secure/Signup!default.jsp" target="_blank">Jira Signup</a></td>
+ </tr>
+</table>
+
+Please send an e-mail to the [Trafodion development list](mail-lists.hmtl) with the approved ICLA attached. Include your git and Jira IDs.
+
+Wait for the response and then you're ready to help us develop Trafodion.
+
+# Development Environment
+You use the following tools and guidelines to develop Trafodion:
+
+<table>
+ <body>
+ <tr>
+ <th style="width:15%;">Area</th>
+ <th style="width:15%;">Tool</th>
+ <th style="width:55%;">Notes</th>
+ <th style="width:15%;">Location</th>
+ </tr>
+ <tr>
+ <td><strong>Trafodion Architecture</strong></td>
+ <td>Document</td>
+ <td>Please review the Trafodion architecture to ensure that you understand how the different components related to each other.</td>
+ <td><a href="architecture-overview.html" target="_blank">Trafodion Architecture</a></td>
+ </tr>
+ <tr>
+ <td><strong>Defect Tracking</strong></td>
+ <td>Jira</td>
+ <td>View all the Trafodion defects and enhancements requests in the Jira system hosted by Apache.</td>
+ <td><a href="https://issues.apache.org/jira/browse/TRAFODION" target="_blank">Trafodion Jiras</a></td>
+ </tr>
+ <tr>
+ <td><strong>Defect Management</strong></td>
+ <td>Document</td>
+ <td>Please read about our approach to defect management. Mostly, any changes you'll make will be in response to a defect reported in Jira.</td>
+ <td><a href="defect-management.html" target="_blank">Defect Management</a></td>
+ </tr>
+ <tr>
+ <td><strong>Git Tools</strong></td>
+ <td>git</td>
+ <td><p>Most of the Trafodion development is done on Linux. Development of the web site and/or documentation can successfully be done on Windows.</p><p>Please download the appropriate tool version; Linux or Windows.</p><p>Then, please refer to <a href="https://help.github.com/articles/set-up-git/" target="_blank">GitHub Documentation</a> for information on how to set up your git environment. Ensure that you register your <a href="https://github.com/settings/ssh" target="_blank">ssh keys</a>.</p></td>
+ <td><a href="http://git-scm.com/downloads" target="_blank">Download git</a></td>
+ </tr>
+ <tr>
+ <td><strong>Code Repository</strong></td>
+ <td>git</td>
+ <td>The full Trafodion source tree can be retrieved from either of these repositories.</td>
+ <td><a href="https://git-wip-us.apache.org/repos/asf/incubator-trafodion.git" target="_blank">Apache Repository</a><br /><a href="https://github.com/apache/incubator-trafodion" target="_blank">GitHub Mirror</a>
+ </td>
+ <tr>
+ </tr>
+ <td><strong>Code Organization</strong></td>
+ <td>Document</td>
+ <td>Please familiarize yourself with the Trafodion code organization.</td>
+ <td><a href="code-organization.html" target="_blank">Code Organization</a></td>
+ </tr>
+ <tr>
+ <td><strong>C++ Coding Guidelines</strong></td>
+ <td>Document</td>
+ <td>Please read the coding guidelines for the Trafodion C++ code before making changes.</td>
+ <td><a href="cplusplus-coding-guidelines.html" target="_blank">C++ Coding Guidelines</a></td>
+ </tr>
+ <tr>
+ <td><strong>Debugging Tips</strong></td>
+ <td>Document</td>
+ <td>Documented tips describing how to debug your code in unit testing.</td>
+ <td><a href="debugging-tips.html" target="_blank">Debugging Tips</a></td>
+ </tr>
+ <tr>
+ <td><strong>Testing</strong></td>
+ <td>Document</td>
+ <td>Trafodion has a rich set of test suites for each of its components. You'll need to run the tests before submitting a code change for review.</td>
+ <td><a href="testing.html" target="_blank">How to Test</a></td>
+ </tr>
+ <tr>
+ <td><strong>Code Reviews</strong></td>
+ <td>git</td>
+ <td>
+ <p>We use GitHub pull-requests for code review. All of the activity on github is captured in ASF JIRA and/or ASF project mail archives by ASF INFRA team automation. In this way, we do not depend on github for accurate history of where contributions come from.</p>
+ <p>Each pull-request title should start with a JIRA ID in brackets, so that activity can be logged to the correct JIRA issue.</p>
+ <p>Regardless of the title, the pull-request activity is also logged to the <a href="http://mail-archives.apache.org/mod_mbox/incubator-trafodion-codereview/" target="_blank">code-review mail list</a>.</p>
+ </td>
+ <td><a href="https://github.com/apache/incubator-trafodion/pulls" target="_blank">Current Pull Requests</a></td>
+ </tr>
+ </body>
+</table>
+
+# Initial Setup
+This set of tasks is performed **after** downloading the git tools. Refer to [Development Tools](#development_tools) above.
+
+You should not have to perform these tasks more than once.
+
+## Setting Up the Git Enviroment
+If you have not done so already, now is the time to set up your **<code>git</code>** environment. Refer to the [GitHub Documentation](https://help.github.com/articles/set-up-git/) for information on how to set up your Git environment. Please ensure that you register your [ssh keys](https://github.com/settings/ssh).
+
+## Fork the Trafodion Repository
+You create a private fork of Trafodion on <https://github.com/apache/incubator-trafodion>. Use the **fork** button top-right on the page to create your fork, which will be named **\<your-git-id\>_fork.**
+
+The following examples use **trafdeveloper** to represent **\<your-git-id\>**.
+
+## Clone the Trafodion Repository
+Use the **git shell** to perform this task.
+
+ # Move to the directory where you want to install the Trafodion source code.
+ cd mysource
+ # Clone the Trafodion source code
+ git clone git://git.apache.org/incubator-trafodion.git
+ # Register your fork as a remote branch
+ git remote add trafdeveloper_fork git@github.com:trafdeveloper/incubator-trafodion
+
+At this point, you've finished all preparation steps. Now, you can start making changes.
+
+# Making Changes
+## Create a Task Branch
+You create a task branch to make changes to the Trafodion source. Typically, we name the branches after the Jira we are working on. In this example, the Jira is: **TRAFODION-1507**.
+
+ # Ensure that you have the latest changes
+ git fetch --all
+ # Checkout source
+ git checkout -b TRAFODION-1507 origin/master
+
+## Change Recipes
+The procedure to make changes depends on what type of problem or feature you're working on.
+
+Change Type | Refer To
+---------------------------------|------------------------------------------------------------
+**Code** | [Modify Code](code.html)
+**Documentation** | [Modify Documentation](document.html)
+**QA Tests** | [Modify Tests](tests.html)
+**Web Site** | [Modify Web Site](website.html)
+
+## Commit Changes
+
+<div class="alert alert-dismissible alert-info">
+ <button type="button" class="close" data-dismiss="alert">&close;</button>
+ <p style="color:black"><strong>Reminder</strong></p>
+ <p style="color:black">If making code changes: please ensure that you run the <a href="testing.html">Regression Tests</a> before committing changes.</p>
+</div>
+
+Perform the following steps to commit your changes.
+
+ # Commit changes
+ git commit -a
+ # Dry-run check
+ git push -n trafdeveloper_fork HEAD
+ # Push changes to your private fork
+ git push trafdeveloper_fork TRAFODION-1507
+
+## Create Pull Request
+You changed code needs to be reviewed by a Trafodion committer. Therefore, you need to create a pull request for your private repository; for example: <https://github.com/trafdeveloper/incubator-trafodion>.
+
+ # Generate pull request
+ git pull-request
+
+Ensure that you include the Jira ID at the beginning of the title in your pull request. For example:
+
+ [TRAFODION-1507] Explanation of the changes you made.
+
+[Automated Tests](#automated_tests) are normally triggered to run on every pull request. If you have modified the documentation or the web site, then you can skip the automated testing by adding the following phrase to the comments of the pull request:
+
+ jenkins, skip test
+
+## Review Comments
+The pull request gets reviewed by the committers and once you get a consensus, then the committer merges your changes into the main incubator-trafodion branch.
+
+## Address Review Comments
+Follow the GitHub conversation on you pull request (you should be automatically subscribed). Respond to questions and issues.
+
+If you need to make additional changes, then do the following:
+
+1. Checkout the code: **<code>git checkout TRAFODION-1507</code>**
+2. Make the requested changes.
+3. Run regression tests.
+4. Commit the changes: **<code>git commit -a</code>**
+5. Push the changes back to your private git fork: **<code>git push trafdeveloper_fork TRAFODION-1507</code>**
+
+## Merge Changes
+If all is well, a committer will merge your change into the Apache repository, which is mirrored on github.
+
+You may be asked to close out the JIRA or other follow up.
+
+Your change is done. Thanks for your contribution to Trafodion.
+
+# Automated Tests
+Automated tests take several hours to complete from when your pull-request was approved by a committer or updated with a new commit.
+
+Normally, the Traf-Jenkins user will post a message in the pull-request with a link to the results. You can also check the Jenkins server to see the status even before the tests are finished. Look in the **Build History** table for the build/test job that matches your pull-request. For example, the master branch tests are located at: <https://jenkins.esgyn.com/job/Check-PR-master/>
+
+## Reviewing Logs
+
+There are two approaches to reviewing logs.
+
+### Approach 1
+
+* The first two columns in build-job table are links to the specific sub-job. Clicl on the link to drill down.
+* The console log of each job has a link to the log file directories (close to the top). Look for **Detailed logs**.
+
+### Approach 2
+
+* Go to: <http://traf-logs.esgyn.com/PullReq/>
+* Click on the number of the pull request. Example: <http://traf-logs.esgyn.com/PullReq/18/>. The next directory level is the build number. With multiple commits or re-tests, it is possible for a pull request to have multiple builds.
+* Under the build number is a directory for each specific job. Example: <http://traf-logs.esgyn.com/PullReq/18/35/regress-seabase-ahw2.2/>
+
+## More Information
+The check tests do not include all of the automated daily tests. If you (or another contributor) want, you can run additional tests on the pull request. Refer [automated test setup](automated-tests.html) for more information.
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/document.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/document.md b/docs/src/site/markdown/document.md
new file mode 100644
index 0000000..021f322
--- /dev/null
+++ b/docs/src/site/markdown/document.md
@@ -0,0 +1,121 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to modify the Trafodion documentation. Please refer to the [Contribute](contribute.html) page for information about other ways to contribute to the Trafodion project.
+
+# Organization
+Documents do **not** include version information as part of the file name.
+
+## Source
+
+Document | Source Format | Source Tree | Output Format
+--------------------------|-----------------------|------------------------------------------------|----------------------------
+Client Installation Guide | word | ```docs/src/resources/docs``` | PDF
+Command Interface Guide | word | ```docs/src/resources/docs``` | PDF
+DCS Reference Guide | asciidoc | ```dcs/src/main/asciidoc``` | Web Book, PDF
+DCS APIs | javadoc | ```dcs/src/main/java``` | Web Book
+odb User Guide | word | ```docs/src/resources/docs``` | PDF
+REST Reference Guide | asciidoc | ```core/rest/src/main/asciidoc``` | Web Book, PDF
+REST APIs | javadoc | ```core/rest/src/main/java``` | Web Book
+SQL Reference Manual | word | ```docs/src/resources/docs``` | PDF
+
+## Web
+
+The documentation is copied to the **```docs/target/docs```** directory on a per-release basis. This directory is referred to as the **release document directory** below.
+
+**Example**
+
+Release Document Directory | Content | Web Site Directory
+----------------------------|---------------------------------------------|----------------------------------------------------
+**```docs/target/1.3.0```** | Documentation related to the 1.3.0 release. | **```incubator.trafodion.apache.org/docs/1.3.0```**
+**```docs/target/1.5.0```** | Documentation related to the 1.5.0 release. | **```incubator.trafodion.apache.org/docs/1.5.0```**
+
+The **release document directory** contains a sub-directory per document. The naming convention for these directories is the document name in all lower case without the manual/guide qualifier and with words separated by underscore. Web-based API definitions generated by **```javadoc```** are located under each sub-directory, if applicable.
+
+**Example**
+
+Document | Sub Directory Name
+--------------------------|------------------------------------------
+Client Installation Guide | **```client_installation```**
+Command Interface Guide | **```command_interface```**
+DCS Reference Guide | **```dcs_reference```**
+odb User Guide | **```odb_user```**
+REST Reference Guide | **```rest_reference```**
+SQL Reference Manual | **```sql_reference```**
+
+The sub-directory is organized as follows. More files may be present in the sub-directory depending on document.
+
+File/Directory | Content
+-----------------------------|------------------------------------------------------------------------------------------------------
+**```*.pdf```** | The PDF version of the document. For example, **```Trafodion_SQL_Reference_Guide.pdf```**.
+**```index.html```** | Entry point for the web book. Generated by asciidoc.
+**```_chapters```** | Web book chapters; that is, the actual content.
+**```apidocs```** | API documentation provided as web. Generated by javadoc.
+**```apidocs/index.html```** | Entry point for API documentation.
+**```css```** | CSS definitions used by the web-version of the document.
+**```images```** | Images used by the web-version of the document.
+
+# Making Changes
+
+## Word Documents
+Do the following:
+
+1. Edit the document in **```docs/src/resources/docs```**.
+2. Save a PDF version of the document in **```docs/src/resources/docs```**.
+3. Build the web site using **```mvn clean site```** against the **```docs```** directory.
+
+The Word and PDF files will be copied to **```docs/target/docs```** directory. You will need to move the files to the final **Release Document Directory**; refer to [Publishing](#Publishing) below.
+
+## Asciidoc Documents
+Please refer to DCS [Contributing to Documentation](https://github.com/apache/incubator-trafodion/blob/master/dcs/src/main/asciidoc/_chapters/appendix_contributing_to_documentation.adoc) guidance for information about working on asciidoc-based documentation.
+
+Once you've made the desired changes, then do the following:
+
+1. Build the document using **```mvn clean site```** against the directory containing the document; for example: **```dcs```** or **```core/rest'''**.
+2. Verify the content in the generated **```target```** directory. The **```target/index.html```** file provides the entry point for the web book; the **```target/apidocs/index.html```** file contains the entry point for API documentation.
+
+You will need to move the files to the final **Release Document Directory**; refer to [Publishing](#Publishing) below.
+
+# Publishing
+
+<div class="alert alert-dismissible alert-info">
+ <button type="button" class="close" data-dismiss="alert">&close;</button>
+ <p style="color:black">Publication is done when a committer is ready to update the external web site. You do <strong>not</strong> perform these steps as part of checking in changes.</p></div>
+
+**Prerequisite:** You need to build the web site before using these instructions. Please refer to [Modifying Web Site](website.html).
+
+You will need to copy/move the documentation from its generated location to the **Release Document Directory**.
+
+1. Create the **Release Document Directory** under **```docs/target/docs```** if it doesn't already exist.
+2. Copy the generated document files as follows:
+
+Document | Populate Release Document Directory
+--------------------------|------------------------------------------
+Client Installation Guide | Delete **```.docx```*** file, copy the **```.pdf```** file in **```docs/target/docs```** to the **Release Document Directory**.
+Command Interface Guide | Delete **```.docx```*** file, copy the **```.pdf```** file in **```docs/target/docs```** to the **Release Document Directory**.
+DCS Reference Guide | Copy **```dcs/target/site/```** to the **Release Document Directory**.
+odb User Guide | Delete **```.docx```*** file, copy the **```.pdf```** file in **```docs/target/docs```** to the **Release Document Directory**.
+REST Reference Guide | Copy **```core/rest/target/site/```** to the **Release Document Directory**.
+SQL Reference Manual | Delete **```.docx```*** file, copy the **```.pdf```** file in **```docs/target/docs```** to the **Release Document Directory**.
+
+**Example — Publishing the DCS Reference Guide**
+
+ cd $SQ_HOME/docs/target/docs
+ mkdir 1.3.0
+ cd 1.3.0
+ mkdir dcs_reference
+ cp -r $SQ_HOME/dcs/target/site/ .
+
+Once the update of the **Release Document Directory** is complete, then you can complete the [web-site publication](website.html#Publishing).
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/documentation.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/documentation.md b/docs/src/site/markdown/documentation.md
new file mode 100644
index 0000000..eff2b45
--- /dev/null
+++ b/docs/src/site/markdown/documentation.md
@@ -0,0 +1,25 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page provides links to the per-release Trafodion documentation.
+
+# 1.3.0
+
+Document | Formats
+-----------------------------------------------|-----------------------------------
+Trafodion Client Installation Guide | [PDF](docs/1.3.0/client_installation/Trafodion_Client_Installation_Guide.pdf)
+Trafodion Command Interface Guide | [PDF](docs/1.3.0/command_interface/Trafodion_Command_Interface_Guide.pdf)
+Trafodion Database Connectivity Services Guide | [Web Book](docs/1.3.0/dcs_reference/index.html), [API](docs/1.3.0/dcs_reference/apidocs/index.html)
+Trafodion odb User Guide | [PDF](docs/1.3.0/odb_user/Trafodion_odb_User_Guide.pdf)
+Trafodion SQL Reference Manual | [PDF](docs/1.3.0/sql_reference/Trafodion_SQL_Reference_Manual.pdf)
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/download.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/download.md b/docs/src/site/markdown/download.md
new file mode 100644
index 0000000..ba33c48
--- /dev/null
+++ b/docs/src/site/markdown/download.md
@@ -0,0 +1,36 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how you download and install the Trafodion product environment. Please refer to [Create Development Environment](create-dev-environment.html] if you want to set up a Trafodion development environment (which includes the installation of a stand-alone Hadoop environment) based on the Trafodion source code.
+
+# Prerequisite
+Trafodion is installed onto an existing Hadoop environment.
+
+# Download
+The Trafodion product environment is installed using the Trafodion Installer, which operates on Trafodion binaries only.
+
+## Binaries
+Not yet available.
+
+## Source
+Build your own binaries from the Trafodion source code as follows:
+
+1. [Setup Build Environment](setup-build-environment.html).
+2. [Build Trafodion](build.html) \— use **```make package```**.
+
+# Install
+Please refer to the [Install](install.html) instructions.
+
+
+
http://git-wip-us.apache.org/repos/asf/incubator-trafodion/blob/286a6e5c/docs/src/site/markdown/enable-secure-trafodion.md
----------------------------------------------------------------------
diff --git a/docs/src/site/markdown/enable-secure-trafodion.md b/docs/src/site/markdown/enable-secure-trafodion.md
new file mode 100644
index 0000000..7e23510
--- /dev/null
+++ b/docs/src/site/markdown/enable-secure-trafodion.md
@@ -0,0 +1,224 @@
+<!--
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the
+ License.
+-->
+This page describes how to Trafodion security.
+
+# Introduction
+If you do not enable security in Trafodion, a client interface to Trafodion may request a username and password, but Trafodion ignores the user name and password entered in the client interface, and the session runs as the database **```root```** user, **```DB__ROOT```**, without restrictions. If you want to restrict users, restrict access to certain users only, or restrict access to an object or operation, then you must enable security, which enforces authentication and authorization. You can enable security during installation by answering the installer's prompts or after installation by running the **```traf_authentication_setup```** script, which enables both authentication and authorization. For more information, see [Authentication Setup Script](#Authentication_Setup_Script) below.
+
+Trafodion does not manage user names and passwords internally but does support authentication via directory servers that support the OpenLDAP protocol, also known as LDAP servers. You can configure the LDAP servers during installation by answering the installer's prompts, or you can configure the LDAP servers manually after installation. For more information, please refer to [Configuring LDAP Servers](Configuring_LDAP_Servers) below.
+
+Once authentication and authorization are enabled, Trafodion allows users to be registered in the database and allows privileges on objects to be granted to users and roles (which are granted to users). Trafodion also supports component-level (or system-level) privileges, such as MANAGE_USERS, which can be granted to users and roles. Refer to [Manage Users](#Manage_Users) below.
+
+# Configuring LDAP Servers
+To specify the LDAP server(s) to be used for authentication, you need to configure the text file **```.traf_authentication_config```**, located (by default) in **```$MY_SQROOT/sql/scripts```**. This file is a flat file, organized as a series of attribute/value pairs. Details on all the attributes and values accepted in the authentication configuration file and how to configure alternate locations can be found in [.traf_authentication_config](traf_authentication_config.html).
+
+A sample template file is located in **```$MY_SQROOT/sql/scripts/traf_authentication_config```**.
+
+Attributes and values in the authentication configuration file are separated with a colon immediately following the attribute name. In general white space is ignored, but spaces may be relevant in some values. Attribute names are always case insensitive. Multiple instances of an attribute are specified by repeating the attribute name and providing the new value. For attributes with only one instance, if the attribute is repeated, the last value provided is used.
+
+ Attribute1: valueA
+ Attribute2: valueB
+ Attribute1: valueC
+
+If **```Attribute1```** has only one instance, **```valueC```** is used, otherwise, **```valueA```** and **```valueC```** are both added to the list of values for **```Attribute1```**.
+
+Attributes are grouped into sections; this is for future enhancements. Attributes are declared in the **```LOCAL```** section, unless otherwise specified.
+
+<table><tr><td><strong>Note</strong><br />Section names, attribute names, and the general layout of the authentication configuration file are subject to change in future versions of Trafodion and backward compatibility is not guaranteed.</td></tr></table>
+
+Specification of your directory server(s) requires at a minimum:
+
+<!-- This table is too complex to do in markdown -->
+<table>
+ <tr>
+ <th width="15%">Setting</th>
+ <th width="55%">Description</th>
+ <th width="30%">Example</th>
+ </tr>
+ <tr>
+ <td><strong><code>LDAP Host Name(s)</code></strong></td>
+ <td>One or more names of hosts that support the OpenLDAP protocol must be specified. Trafodion will attempt to connect to all provided host names during the authentication process. The set of user names and passwords should be identical on all hosts to avoid unpredictable results. The attribute name is <strong><code>LDAPHostName</code></strong></td>
+ <td><pre>LDAPHostName: ldap.company.com</pre></td>
+ </tr>
+ <tr>
+ <td><strong><code>LDAP Port Number</code></strong></td>
+ <td>Port number of the LDAP server. Typically this is 389 for servers using no encryption or TLS, and 636 for servers using SSL. The attribute name is <strong><code>LDAPPort</code></strong>.</td>
+ <td><pre>LDAPPort: 389</pre></td>
+ </tr>
+ <tr>
+ <td><strong><code>LDAP Unique Identifier</code></strong></td>
+ <td>Attribute(s) used by the directory server that uniquely identifies the user name. You may provide one or more unique identifier specifiers.</td>
+ <td><pre>UniqueIdentifier: uid=,ou=users,dc=com</pre></td>
+ </tr>
+ <tr>
+ <td><strong><code>Encryption Level</code></strong></td>
+ <td>A numeric value indicating the encryption scheme used by your LDAP server. Values are:
+ <ul>
+ <li>0: Encryption not used</li>
+ <li>1: SSL</li>
+ <li>2: TLS</li>
+ </ul>
+ </td>
+ <td>
+ <pre>LDAPSSL: 2</pre>
+ <p>If your LDAP server uses TLS you must specify a file containing the certificate used to encrypt the password. By default the Trafodion software looks for this file in <strong><code>$MY_SQROOT/cacerts</code></strong>, but you may specify a fully qualified filename, or set the environment variable <strong><code>CACERTS_DIR</code></strong> to another directory. To specify the file containing the certificate, you set the value of the attribute <strong><code>TLS_CACERTFilename</code></strong>, located in the Defaults section.</p>
+ <p><strong>Example</strong></p>
+ <pre>
+TLS_CACERTFilename: mycert.pem
+TLS_CACertFilename: /usr/etc/cert.pem</pre>
+ </td>
+ </tr>
+ <tr>
+ <td><strong><code>Search username and password</code></strong></td>
+ <td>Some LDAP servers require a known user name and password to search the directory of user names. If your environment has that requirement, provide these “search” values.</td>
+ <td>
+ <pre>
+LDAPSearchDN: lookup@company.com
+LDAPSearchPwd: Lookup123</pre>
+ </td>
+ </tr>
+</table>
+
+There are additional optional attributes that can be used to customize Trafodion authentication. As mentioned earlier, they are described in [.traf_authentication_config](traf_authentication_config.html).
+
+You can test the authentication configuration file for syntactic errors using the **```ldapconfigcheck```** tool. If you have loaded the Trafodion environment (**```sqenv.sh```**), then the tool will automatically check the file at **```$MY_SQROOT/sql/scripts/.traf_authentication_config```**. If not, you can specify the file to be checked.
+
+**Example**
+
+ ldapconfigcheck –file myconfigfile
+ File myconfigfile is valid.
+
+If an error is found, the line number with the error is displayed along with the error. Please refer to [ldapconfigcheck](ldapconfigcheck.html) for more information.
+
+<table><tr><td><strong>Note</strong><br />The authentication configuration file needs to be propagated to all nodes, but there is a script that will do that for you described later. For now, you can test your changes on the local node.</td></tr></table>
+
+You can test the LDAP connection using the utility **```ldapcheck```**. To use this utility the Trafodion environment must be loaded (**```sqenv.sh```**), but the Trafodion instance does not need to be running. To test the connection only, you can specify any user name, and a name lookup will be performed using the attributes in **```.traf_authentication_config```**.
+
+ ldapcheck --username=fakename@company.com
+ User fakename@company.com not found
+
+If **```ldapcheck```** reports either that the user was found or the user was not found, the connection was successful. However, if an error is reported, either the configuration file is not setup correctly, or there is a problem either with your LDAP server or the connection to the server. You can get additional error detail by including the **```--verbose```** option. Please refer to [ldapcheck](ldapcheck.html) for more information.
+
+If you supply a password, **```ldapcheck```** will attempt to authenticate the specified **```username```** and **```password```**. The example below shows the password for illustrative purposes, but to avoid typing the password on the command line, leave the password blank (**```--password=```**) and the utility will prompt for the password with no echo.
+
+ ldapcheck --username=realuser@company.com –-password=StrongPassword
+ Authentication successful
+
+# Generate a Trafodion Certificate
+Trafodion clients such as **```trafci```** will encrypt the password before sending it to Trafodion. A self-signed certificate is used to encrypt the password. The certificate and key should be generated when the **```sqgen```** script is invoked. By default, the files **```server.key```** and **```server.crt```** will be located in **```$HOME/sqcert```**. If those files are not present, since Trafodion clients will not send unencrypted passwords, you will need to manually generate those files. To do so, run the script **```sqcertgen```** located in **```$MY_SQROOT/sql/scripts```**. The script runs **```openssl```** to generate the certificate and key.
+
+To run openssl manually, follow the example:
+
+ openssl req -x509 -nodes -days 365 -subj '/C=US/ST=California/L=PaloAlto/CN=host.domain.com/O=Some Company/OU=Service Connection'
+ - newkey rsa:2048 -keyout server.key -out server.crt
+
+Option | Description
+------------------------------------------|-----------------------
+**```-x509```** | Generate a self-signed certificate.
+**```-days <validity of certificate>```** | Make the certificate valid for the days specified.
+**```-newkey rsa:<bytes>```** | Generate a new private key of type RSA of length 1024 or 2048 bytes.
+**```-subj <certificateinfo>```** | Specify the information that will be incorporated in the certificate. Each instance in a cluster should have a unique common name(**```CN```**).
+**```-keyout <filename>```** | Write the newly generated RSA private key to the file specified.
+**```-nodes```** | It is an optional parameter that specifies NOT to encrypt the private key. If you encrypt the private key, then you must enter the password every time the private key is used by an application.
+**```-out <filename>```** | Write the self-signed certificate to the specified file.
+
+Both the public (**```server.crt```**) and private (**```server.key```**) files should be placed in the directory **```$HOME/sqcert```**. If you do not want to use the **```HOME```** directory or if you want to use different names for the private and/or public key files, then Trafodion supports environment variables to specific the alternate locations or names.
+
+* Trafodion first checks the environment variables **```SQCERT_PRIVKEY```** and **```SQCERT_PUBKEY```**. If they are set, Trafodion uses the fully qualified filename value of the environment variable.
+
+ You can specify either one filename environment variable or both.
+
+* If at least one filename environment variable is not set, Trafodion checks the value of the environment variable **```SQCERT_DIR```**. If set, the default filename **```server.key```** or **```server.crt```** is appended to the value of the environment variable **```SQCERT_DIR```**.
+* If the filename environment variable is not set and the directory environment variable is not set, Trafodion uses the default location (**```$HOME/sqcert```**) and the default filename.
+
+# Authentication Setup Script
+The final step to enable security is to change the value of the environment variable **```TRAFODION_ENABLE_AUTHENTICATION```**from **```NO```** to **```YES```** and turn on authorization. This is achieved by invoking the **```traf_authentication_setup```** script, which is located in **```$MY_SQROOT/sql/scripts```**.
+
+**Usage**
+
+Usage: traf_authentication_setup [options]
+
+```
+Options:
+ --file <loc> Optional location of OpenLDAP configuration file
+ --help Prints this message
+ --off Disables authentication and authorization
+ --on Enables authentication and authorization
+ --setup Enables authentication
+ --status Returns status of authentication enablement
+```
+
+<!-- In HTML to control the column widths; markdown table doesn't handle Option correctly. -->
+<table>
+ <tr>
+ <th width="10%">Option</th>
+ <th width="90%">Description</th>
+ </tr>
+ <tr>
+ <td><strong><code>--file</code></strong></td>
+ <td>If specified, then <strong><code>filename</code></strong> is copied to <strong><code>$MY_SQROOT/</code></strong>. Users working in their own private environment can refer to a site-specific configuration file from a central location.</td>
+ </tr>
+ <tr>
+ <td><strong><code>--on</code></strong></td>
+ <td>
+ <p><strong><code>traf_authentication_setup</code></strong> invokes <a href="ldapconfigcheck.html">ldapconfigcheck</a>) to verify the configuration file is syntactically correct. It also invokes <a href="ldapcheck.html">ldapcheck</a> to verify that a connection can be made to an LDAP server.</p>
+ <p>If both checks pass, the script sets the environment variable <strong><code>TRAFODION_ENABLE_AUTHENTICATION</code></strong> to <strong><code>YES</code></strong> in the file <strong><code>$MY_SQROOT/sqenvcom.sh</code></strong>, and propagates <strong><code>sqenvcom.sh</code></strong> and <strong><code>.traf_authentication_config</code></strong> to all nodes in the cluster.</p>
+ <p>The last step is to enable authorization by creating privilege-related metadata tables and set up default permissions with a call to the database. The list of privilege-related metadata tables, users, roles, and component privileges are logged in <strong><code>$MY_SQROOT/logs/authEnable.log</code></strong>.</p>
+ <p>Specifying <strong><code>--on</code></strong> requires that a valid <strong><code>.traf_authentication_config</code></strong> file exists and the Trafodion metadata initialized.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><strong><code>--off</code></strong></td>
+ <td>
+ <p>If specified, then <strong><code>traf_authentication_setup</code></strong> sets the environment variable <strong><code>TRAFODION_ENABLE_AUTHENTICATION</code></strong> to <strong><code>NO</code></strong> in <strong><code>$MY_SQROOT/sqenvcom.sh</code></strong> and propagates the file to all the nodes in the cluster.</p>
+ <p>The last step is to disable authorization by removing any privilege-related metadata and permissions with a call to the database. The results of this operation is logged in <strong><code>$MY_SQROOT/logs/authEnable.log</code></strong>.</p>
+ </td>
+ </tr>
+ <tr>
+ <td><strong><code>--setup</code></strong></td>
+ <td>Use this option if the Trafodion metadata has not been initialized. This option enables authentication but does not call the database to create privilege-related metadata tables. Later, when Trafodion metadata is initialized, privilege-related metadata tables and default permissions are automatically created.
+ </td>
+ </tr>
+ <tr>
+ <td><strong><code>--status</code></strong></td>
+ <td>Reports the value of the environment variable <strong><code>TRAFODION_ENABLE_AUTHENTICATION</code></strong> in <strong><code>$MY_SQROOT/sqenvcom.sh</code></strong> on the current node and reports the status of security features in the database.
+ </td>
+ </tr>
+</table>
+
+**Example**
+
+```
+INFO: Start of security (authentication and authorization) script Wed Mar 25 15:12:50 PDT 2xxx.
+
+INFO: *** Trafodion security (authentication and authorization) status ***
+ Authentication is ENABLED
+ Authorization (grant/revoke) is ENABLED
+
+INFO: End of security (authorization and authentication) script Wed Mar 25 15:12:54 PDT 2xxx.
+```
+
+<table><tr><td><strong>IMPORTANT</strong><br />Any time the environment file (<strong><code>sqenvcom.sh</code></strong>) is changed (and propagated to all nodes), Database Connectivity Services (DCS) must be restarted to pick up the new value. If the configuration file is changed, it will be re-read in 30 minutes (by default), but you can have changes take effect immediately by restarting DCS.</td></tr></table>
+
+To restart DCS, run the scripts **```stop-dcs.sh```** and **```start-dcs.sh```**, located in **```$MY_SQROOT/dcs-<x>.<y>.<z>/bin```**.
+
+# Manage Users
+Users are registered in the Trafodion database and are used to enforce authorization. If security is disabled, any user can register any user at any time. However, once security is enabled, user administration is considered a secure operation, and registration of users is restricted to **```DB__ROOT```** or any user granted the **```MANAGE_USERS```** component privilege. To initially register a user, connect to Trafodion with the external user mapped to **```DB__ROOT```**(also known as the Trafodion ID).
+
+When security is enabled, the **```DB__ROOT```** user is registered as the **```TRAFODION```** external user name. It is recommended that the **```DB__ROOT```** user be mapped to the external user name that will be used to connect for root operations. To do this, start a **```sqlci```** session and perform the **```ALTER USER``*** command, for example:
+
+ ALTER USER DB__ROOT SET EXTERNAL NAME trafodion_rootuser_in_ldap;
+
+To learn more about how to register users, grant object and component privileges, and manage users and roles, please see the [Trafodion SQL Reference Manual](docs/Trafodion_SQL_Reference_Manual.pdf).
\ No newline at end of file