JAVA-1685: Clarify recommendation on preparing SELECT *

olim7t · olim7t · commit abed4c2e0347 · 2018-01-04T11:13:59.000-08:00
diff --git a/changelog/README.md b/changelog/README.md
@@ -4,6 +4,7 @@
 
 - [improvement] JAVA-1671: Remove unnecessary test on prepared statement metadata.
 - [bug] JAVA-1694: Upgrade to jackson-databind 2.7.9.2 to address CVE-2015-15095.
+- [documentation] JAVA-1685: Clarify recommendation on preparing SELECT *.
 
 Merged from 3.3.x:
 
diff --git a/manual/statements/prepared/README.md b/manual/statements/prepared/README.md
@@ -249,10 +249,9 @@ is currently no mechanism for Cassandra to invalidate the existing metadata.  Be
 the driver is not able to properly react to these changes and will improperly read rows after
 a schema change is made.
 
-Therefore it is currently recommended to not create prepared statements
-for 'SELECT *' queries if you plan on making schema changes involving
-adding or dropping columns. Alternatively you should list all columns of interest
-in your statement, i.e.: `SELECT a, b, c FROM tbl`.
+Therefore it is currently recommended to list all columns of interest in
+your prepared statements (i.e. `SELECT a, b, c FROM table`), instead of
+relying on `SELECT *`.
 
 This will be addressed in a future release of both Cassandra and the driver.  Follow
 [CASSANDRA-10786] and [JAVA-1196] for more information.
@@ -264,4 +263,4 @@ This will be addressed in a future release of both Cassandra and the driver.  Fo
 [execute]:              http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/Session.html#execute-com.datastax.driver.core.Statement-
 [executeAsync]:         http://docs.datastax.com/en/drivers/java/3.2/com/datastax/driver/core/Session.html#executeAsync-com.datastax.driver.core.Statement-
 [CASSANDRA-10786]:      https://issues.apache.org/jira/browse/CASSANDRA-10786
-[JAVA-1196]:            https://datastax-oss.atlassian.net/browse/JAVA-1196
+[JAVA-1196]:            https://datastax-oss.atlassian.net/browse/JAVA-1196
