Unexpected behaviour when VisibilityController coprocessor is used

[Suresh Subbiah]

Hi,

When I run the following script from hbase shell the last scan returns no
rows

create 'visibilityTest', 'f1'
put 'visibilityTest', 'r1', 'f1:c1', 'value1'
deleteall 'visibilityTest', 'r1'
put 'visibilityTest', 'r1', 'f1:c1', 'value2'
scan 'visibilityTest'

*hbase(main):013:0> scan 'visibilityTest'*
*ROW                   COLUMN+CELL
      *
*0 row(s) in 0.0100 seconds*


However if I run
scan 'visibilityTest' , {RAW=>TRUE}

I see that the second row that I put is indeed there and has a timestamp
value higher that the previous delete

*hbase(main):014:0> scan 'visibilityTest', {RAW=>TRUE}*
*ROW                   COLUMN+CELL
      *
* r1                   column=f1:, timestamp=1444516578296,
type=DeleteFamily    *
* r1                   column=f1:c1, timestamp=1444516647655, value=value2
      *
*1 row(s) in 0.0110 seconds*



This is on hbase 0.98.6.  Problem is seen only when hbase-site.xml has
these lines. No other coprocessors were used during this test.

<property>
    <name>hbase.coprocessor.region.classes</name>

 <value>org.apache.hadoop.hbase.security.visibility.VisibilityController</value>
   </property>
   <property>
     <name>hbase.coprocessor.master.classes</name>

 <value>org.apache.hadoop.hbase.security.visibility.VisibilityController</value>
   </property>
   <property>
     <name>hfile.format.version</name>
     <value>3</value>
   </property>

Any suggestions of what I may be doing incorrectly? Or is this a bug?

Thank you
Suresh