Re: Phoenix Index Scrutiny Tool

2019-08-13 Thread Aleksandr Saraseka
upd: yeah, my first example of output seems to be wrong. Re-run my test and now seems right: +--+---+++ |

Re: Phoenix Index Scrutiny Tool

2019-08-13 Thread Aleksandr Saraseka
@Vincent - I dropped columns from an index table. Thank you for pointing me to "partial rebuild", will try it. On Mon, Aug 12, 2019 at 8:51 PM Vincent Poon wrote: > @Aleksandr did you delete rows from the data table, or the index table? > The output you're showing says that you have orphaned

Re: Phoenix Index Scrutiny Tool

2019-08-12 Thread Vincent Poon
@Aleksandr did you delete rows from the data table, or the index table? The output you're showing says that you have orphaned rows in the index table - i.e. rows that exist only in the index table and have no corresponding row in the data table. If you deleted the original rows in the data table

Re: Phoenix Index Scrutiny Tool

2019-08-09 Thread Alexander Batyrshin
I have familiar question - how to partially rebuild indexes by timestamps interval like many MapReduce has —starttime/—endttime > On 9 Aug 2019, at 17:21, Aleksandr Saraseka wrote: > > Hello community! > I'm testing scrutiny tool to check index consistency. > I hard-deleted from HBase a couple

Phoenix Index Scrutiny Tool

2019-08-09 Thread Aleksandr Saraseka
Hello community! I'm testing scrutiny tool to check index consistency. I hard-deleted from HBase a couple of rows from global index, then ran Scrutiny tool, it showed me some output like: SOURCE_TABLE TARGET_TABLE SCRUNITY_EXECUTE_TIME SOURCE_ROW_PK_HASH SOURCE_TS TARGET_TS HAS_TARGET_ROW