Thanks for the slides, Rajesh Babu. Does this mean any read path will have to scan all regions of a table? Is there an optimization available if the primary key and the index share a common prefix, thus reducing the number of regions to look at?
Thanks again! On Jun 29, 2017 7:24 PM, "rajeshb...@apache.org" <chrajeshbab...@gmail.com> wrote: 9,10 slides gives details how read path works. https://www.slideshare.net/rajeshbabuchintaguntla/local- secondary-indexes-in-apache-phoenix Let's know if you need more information. Thanks, Rajeshbabu. On Fri, Jun 30, 2017 at 4:20 AM, Neelesh <neele...@gmail.com> wrote: > Hi, > The documentation says - "From 4.8.0 onwards we are storing all local > index data in the separate shadow column families in the same data table". > > It is not quite clear to me how the read path works with local indexes. Is > there any document that has some details on how it works ? PHOENIX-1734 has > some (shadow CFs), but not enough. > > Any pointers are appreciated! > > Thanks > >
