You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by kl...@apache.org on 2016/12/14 17:57:21 UTC

[06/50] [abbrv] geode git commit: GEODE-2187: Docs: bad subnav link in REST Apps > Troubleshooting

GEODE-2187: Docs: bad subnav link in REST Apps > Troubleshooting


Project: http://git-wip-us.apache.org/repos/asf/geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/geode/commit/f58a11d9
Tree: http://git-wip-us.apache.org/repos/asf/geode/tree/f58a11d9
Diff: http://git-wip-us.apache.org/repos/asf/geode/diff/f58a11d9

Branch: refs/heads/feature/GEODE-1930
Commit: f58a11d943bbde29a237968a67392e75690698ee
Parents: 7fb0e68
Author: Dave Barnes <db...@pivotal.io>
Authored: Wed Dec 7 10:15:44 2016 -0800
Committer: Dave Barnes <db...@pivotal.io>
Committed: Wed Dec 7 10:15:44 2016 -0800

----------------------------------------------------------------------
 geode-book/master_middleman/source/subnavs/geode-subnav.erb | 9 ++-------
 geode-docs/rest_apps/troubleshooting.html.md.erb            | 5 +----
 2 files changed, 3 insertions(+), 11 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/geode/blob/f58a11d9/geode-book/master_middleman/source/subnavs/geode-subnav.erb
----------------------------------------------------------------------
diff --git a/geode-book/master_middleman/source/subnavs/geode-subnav.erb b/geode-book/master_middleman/source/subnavs/geode-subnav.erb
index aec611d..16aa1e7 100644
--- a/geode-book/master_middleman/source/subnavs/geode-subnav.erb
+++ b/geode-book/master_middleman/source/subnavs/geode-subnav.erb
@@ -21,7 +21,7 @@ limitations under the License.
     <div class="nav-content">
         <ul>
             <li>
-                <a href="/docs/guide/about_geode.html">Apache Geode 1.0.0-incubating Documentation</a>
+                <a href="/docs/guide/about_geode.html">Apache Geode Documentation</a>
             </li>
             <li class="has_submenu">
                 <a href="/docs/guide/getting_started/book_intro.html">Getting Started with Apache Geode</a>
@@ -1642,13 +1642,8 @@ limitations under the License.
                     <li>
                         <a href="/docs/guide/rest_apps/rest_examples.html">Sample REST Applications</a>
                     </li>
-                    <li class="has_submenu">
+                    <li>
                         <a href="/docs/guide/rest_apps/troubleshooting.html">Troubleshooting and FAQ</a>
-                        <ul>
-                            <li>
-                                <a href="/docs/guide/rest_apps/troubleshooting.html#concept_gsv_zd5_m4">Key Types and JSON Support</a>
-                            </li>
-                        </ul>
                     </li>
                     <li class="has_submenu">
                         <a href="/docs/guide/rest_apps/rest_api_reference.html">Apache Geode REST API Reference</a>

http://git-wip-us.apache.org/repos/asf/geode/blob/f58a11d9/geode-docs/rest_apps/troubleshooting.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/rest_apps/troubleshooting.html.md.erb b/geode-docs/rest_apps/troubleshooting.html.md.erb
index 027e2c6..0f47fff 100644
--- a/geode-docs/rest_apps/troubleshooting.html.md.erb
+++ b/geode-docs/rest_apps/troubleshooting.html.md.erb
@@ -23,10 +23,6 @@ limitations under the License.
 
 This section provides troubleshooting guidance and frequently asked questions about Geode Developer REST APIs.
 
--   **[Key Types and JSON Support](../rest_apps/troubleshooting.html#concept_gsv_zd5_m4)**
-
-    When defining regions (your REST resources), you must only use scalar values for keys and also set value constraints in order to avoid producing JSON that cannot be parsed by Geode.
-
 ## Checking if the REST API Service is Up and Running
 
 Use the ping endpoint to verify whether the REST API server is available.
@@ -52,6 +48,7 @@ If the server is not available, your client will receive an HTTP error code and
 When defining regions (your REST resources), you must only use scalar values for keys and also set value constraints in order to avoid producing JSON that cannot be parsed by Geode.
 
 If Geode regions are not defined with scalar values as keys and value constraints, then you may receive the following error message (even though the JSON is technically valid) in your REST client applications:
+
 ``` pre
 Json doc specified in request body is malformed..!!'
 ```