Merge pull request #262393 from v-akarnase/patch-33

Update apache-hbase-phoenix-performance.md

Author: prmerger-automator[bot]

articles/hdinsight/hbase/apache-hbase-phoenix-performance.md

@@ -4,7 +4,7 @@ description: Best practices to optimize Apache Phoenix performance for Azure HDI
 ms.service: hdinsight
 ms.topic: how-to
 ms.custom: hdinsightactive
-ms.date: 12/26/2022
+ms.date: 01/04/2024
 ---
 
 # Apache Phoenix performance best practices
@@ -42,7 +42,7 @@ With this new primary key the row keys generated by Phoenix would be:
 |  Dole-John-111|1111 San Gabriel Dr.|1-425-000-0002|    John|Dole| 111 |
 |  Raji-Calvin-222|5415 San Gabriel Dr.|1-230-555-0191|  Calvin|Raji| 222 |
 
-In the first row above, the data for the rowkey is represented as shown:
+In the first row of given table, the data for the rowkey is represented as shown:
 
 |rowkey|       key|   value|
 |------|--------------------|---|
@@ -107,7 +107,7 @@ Secondary indexes can improve read performance by turning what would be a full t
 
 Covered indexes are indexes that include data from the row in addition to the values that are indexed. After finding the desired index entry, there's no need to access the primary table.
 
-For example, in the example contact table you could create a secondary index on just the socialSecurityNum column. This secondary index would speed up queries that filter by socialSecurityNum values, but retrieving other field values will require another read against the main table.
+For example, in the example contact table you could create a secondary index on just the socialSecurityNum column. This secondary index would speed up queries that filter by socialSecurityNum values, but retrieving other field values require another read against the main table.
 
 |rowkey|       address|   phone| firstName| lastName| socialSecurityNum |
 |------|--------------------|--------------|-------------|--------------| ---|
@@ -145,7 +145,7 @@ The main considerations in query design are:
 
 ### Understand the query plan
 
-In [SQLLine](http://sqlline.sourceforge.net/), use EXPLAIN followed by your SQL query to view the plan of operations that Phoenix will perform. Check that the plan:
+In [SQLLine](http://sqlline.sourceforge.net/), use EXPLAIN followed by your SQL query to view the plan of operations that Phoenix performs. Check that the plan:
 
 * Uses your primary key when appropriate.
 * Uses appropriate secondary indexes, rather than the data table.
@@ -155,13 +155,13 @@ In [SQLLine](http://sqlline.sourceforge.net/), use EXPLAIN followed by your SQL
 
 As an example, say you have a table called FLIGHTS that stores flight delay information.
 
-To select all the flights with an airlineid of `19805`, where airlineid is a field that isn't in the primary key or in any index:
+To select all the flights with an `airlineid` of `19805`, where `airlineid` is a field that isn't in the primary key or in any index:
 
 ```sql
 select * from "FLIGHTS" where airlineid = '19805';
 ```
 
-Run the explain command as follows:
+Run the explained command as follows:
 
 ```sql
 explain select * from "FLIGHTS" where airlineid = '19805';
@@ -196,13 +196,13 @@ CLIENT 1-CHUNK PARALLEL 1-WAY ROUND ROBIN RANGE SCAN OVER FLIGHTS [2014,1,2,'AA'
 
 The values in square brackets are the range of values for the primary keys. In this case, the range values are fixed with year 2014, month 1, and dayofmonth 2, but allow values for flightnum starting with 2 and on up (`*`). This query plan confirms that the primary key is being used as expected.
 
-Next, create an index on the FLIGHTS table named `carrier2_idx` that is on the carrier field only. This index also includes flightdate, tailnum, origin, and flightnum as covered columns whose data is also stored in the index.
+Next, create an index on the FLIGHTS table named `carrier2_idx` that is on the carrier field only. This index also includes `flightdate`, `tailnum`, `origin`, and `flightnum` as covered columns whose data is also stored in the index.
 
 ```sql
 CREATE INDEX carrier2_idx ON FLIGHTS (carrier) INCLUDE(FLIGHTDATE,TAILNUM,ORIGIN,FLIGHTNUM);
 ```
 
-Say you want to get the carrier along with the flightdate and tailnum, as in the following query:
+Say you want to get the carrier along with the `flightdate` and `tailnum`, as in the following query:
 
 ```sql
 explain select carrier,flightdate,tailnum from "FLIGHTS" where carrier = 'AA';