Hi Everyone, I am trying to upgrade HBase version (client and server) from 1.2.0 to 2.2.6 and started seeing some unexpected behavior around discovery of ambiguous row in filter during StoreFileScans.
*Is it a valid case that filters and Comparators might see a fake cell passed to them if that row is set as an inclusive(by default) start row to skip preceding row during Store file scans during client side execution?* I have added more details on what I have been seeing https://issues.apache.org/jira/browse/HBASE-27691 Appreciate if some one could shed some light if this is expected or a potential bug? Thanks, Tej -- Regards, Tej Kiran Meka
