phoenix 索引相关

淡淡的烟草味﹌ 2022-08-27 04:52 196阅读 0赞

\* Index maintainer that maintains multiple indexes based on '\{@link ColumnGroup\}s'. Each group is a  
 \* fully covered within itself and stores the fully 'pre-joined' version of that values for that  
 \* group of columns.  
 \* <p>  
 \* <h2>Index Layout</h2> The row key for a given index entry is the current state of the all the  
 \* values of the columns in a column group, followed by the primary key (row key) of the original  
 \* row, and then the length of each value and then finally the total number of values. This is then  
 \* enough information to completely rebuild the latest value of row for each column in the group.  
 \* <p>  
 \* The family is always \{@link CoveredColumnIndexCodec\#INDEX\_ROW\_COLUMN\_FAMILY\}  
 \* <p>  
 \* The qualifier is prepended with the integer index (serialized with \{@link Bytes\#toBytes(int)\}) of  
 \* the column in the group. This index corresponds the index of the value for the group in the row  
 \* key.  
 \*   
 \* <pre>  
 \*         ROW                            ||   FAMILY     ||    QUALIFIER     ||   VALUE  
 \* (v1)(v2)...(vN)(pk)(L1)(L2)...(Ln)(\#V) || INDEX\_FAMILY ||     1Cf1:Cq1     ||  null  
 \* (v1)(v2)...(vN)(pk)(L1)(L2)...(Ln)(\#V) || INDEX\_FAMILY ||     2Cf2:Cq2     ||  null  
 \* ...  
 \* (v1)(v2)...(vN)(pk)(L1)(L2)...(Ln)(\#V) || INDEX\_FAMILY ||     NCfN:CqN     ||  null  
 \* </pre>  
 \*   
 \* <h2>Index Maintenance</h2>  
 \* <p>  
 \* When making an insertion into the table, we also attempt to cleanup the index. This means that we  
 \* need to remove the previous entry from the index. Generally, this is completed by inserting a  
 \* delete at the previous value of the previous row.  
 \* <p>  
 \* The main caveat here is when dealing with custom timestamps. If there is no special timestamp  
 \* specified, we can just insert the proper \{@link Delete\} at the current timestamp and move on.  
 \* However, when the client specifies a timestamp, we could see updates out of order. In that case,  
 \* we can do an insert using the specified timestamp, but a delete is different...  
 \* <p>  
 \* Taking the simple case, assume we do a single column in a group. Then if we get an out of order  
 \* update, we need to check the current state of that column in the current row. If the current row  
 \* is older, we can issue a delete as normal. If the current row is newer, however, we then have to  
 \* issue a delete for the index update at the time of the current row. This ensures that the index  
 \* update made for the 'future' time still covers the existing row.  
 \* <p>  
 \* <b>ASSUMPTION:</b> all key-values in a single \{@link Delete\}/\{@link Put\} have the same timestamp.  
 \* This dramatically simplifies the logic needed to manage updating the index for out-of-order  
 \* \{@link Put\}s as we don't need to manage multiple levels of timestamps across multiple columns.  
 \* <p>  
 \* We can extend this to multiple columns by picking the latest update of any column in group as the  
 \* delete point.  
 \* <p>  
 \* <b>NOTE:</b> this means that we need to do a lookup (point \{@link Get\}) of the entire row

\* <i>every time there is a write to the table</i>.

at org.apache.phoenix.hbase.index.covered.data.LazyValueGetter.getLatestValue(LazyValueGetter.java:71)  
at org.apache.phoenix.index.IndexMaintainer.buildRowKey(IndexMaintainer.java:328)  
at org.apache.phoenix.index.IndexMaintainer.buildDeleteMutation(IndexMaintainer.java:473)  
at org.apache.phoenix.index.PhoenixIndexCodec.getIndexDeletes(PhoenixIndexCodec.java:170)  
at org.apache.phoenix.hbase.index.covered.CoveredColumnsIndexBuilder.addDeleteUpdatesToMap(CoveredColumnsIndexBuilder.java:405)  
at org.apache.phoenix.hbase.index.covered.CoveredColumnsIndexBuilder.addCleanupForCurrentBatch(CoveredColumnsIndexBuilder.java:286)  
at org.apache.phoenix.hbase.index.covered.CoveredColumnsIndexBuilder.addMutationsForBatch(CoveredColumnsIndexBuilder.java:237)  
at org.apache.phoenix.hbase.index.covered.CoveredColumnsIndexBuilder.batchMutationAndAddUpdates(CoveredColumnsIndexBuilder.java:134)  
at org.apache.phoenix.hbase.index.covered.CoveredColumnsIndexBuilder.getIndexUpdate(CoveredColumnsIndexBuilder.java:97)  
at org.apache.phoenix.hbase.index.builder.IndexBuildManager$1.call(IndexBuildManager.java:134)  
at org.apache.phoenix.hbase.index.builder.IndexBuildManager$1.call(IndexBuildManager.java:130)  
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)  
at java.util.concurrent.FutureTask.run(FutureTask.java:138)  
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)  
at java.lang.Thread.run(Thread.java:662)  
: 1 time, servers with issues: nobida145:60020, (state=,code=0)