Author: vincentpoon
Date: Tue Oct  9 20:20:31 2018
New Revision: 1843338

URL: http://svn.apache.org/viewvc?rev=1843338&view=rev
Log:
Update to reflect PHOENIX-3925

Modified:
    phoenix/site/publish/atomic_upsert.html
    phoenix/site/source/src/site/markdown/atomic_upsert.md

Modified: phoenix/site/publish/atomic_upsert.html
URL: 
http://svn.apache.org/viewvc/phoenix/site/publish/atomic_upsert.html?rev=1843338&r1=1843337&r2=1843338&view=diff
==============================================================================
--- phoenix/site/publish/atomic_upsert.html (original)
+++ phoenix/site/publish/atomic_upsert.html Tue Oct  9 20:20:31 2018
@@ -207,7 +207,7 @@ ON DUPLICATE KEY UPDATE
   <li>The CURRENT_SCN property may not be set on connection when this clause 
is used as HBase does not handle atomicity unless the latest value is being 
updated.</li> 
   <li>The same column should not be updated more than once in the same 
statement.</li> 
   <li>No aggregation or references to sequences are allowed within the 
clause.</li> 
-  <li>Although global indexes on columns being atomically updated are 
supported, it’s not recommended as a potentially a separate RPC across the 
wire would be made while the row is under lock to maintain the secondary 
index.</li> 
+  <li>Global indexes on columns being atomically updated are not supported, as 
potentially a separate RPC across the wire would be made while the row is under 
lock to maintain the secondary index.</li> 
  </ul> 
 </div>
                        </div>

Modified: phoenix/site/source/src/site/markdown/atomic_upsert.md
URL: 
http://svn.apache.org/viewvc/phoenix/site/source/src/site/markdown/atomic_upsert.md?rev=1843338&r1=1843337&r2=1843338&view=diff
==============================================================================
--- phoenix/site/source/src/site/markdown/atomic_upsert.md (original)
+++ phoenix/site/source/src/site/markdown/atomic_upsert.md Tue Oct  9 20:20:31 
2018
@@ -52,7 +52,5 @@ The following limitations are enforced f
   does not handle atomicity unless the latest value is being updated.
 * The same column should not be updated more than once in the same statement.
 * No aggregation or references to sequences are allowed within the clause.
-* Although global indexes on columns being atomically updated are supported, 
it's not recommended
-  as a potentially a separate RPC across the wire would be made while the row 
is under lock to
-  maintain the secondary index.
+* Global indexes on columns being atomically updated are not supported, as 
potentially a separate RPC across the wire would be made while the row is under 
lock to maintain the secondary index.
 


Reply via email to