We have been using house grown secondary indexes on HBase tables in our
application.
I am wondering if we switch to Phoenix and let Phoenix creates and
maintains new secondary
indexes, can a MapReduce job take advantage of these indexes without using
the Phoenix
API?

Reply via email to