Thanks for the information Rajesh Babu, this is really helpful! On Jun 29, 2017 11:00 PM, "rajeshb...@apache.org" <chrajeshbab...@gmail.com> wrote:
> Yes Neelesh, at present need to touch all the regions and there is a JIRA > for the optimization[1 > <https://issues.apache.org/jira/browse/PHOENIX-3941>] > > [1] https://issues.apache.org/jira/browse/PHOENIX-3941 > > Thanks, > Rajeshbbu. > > On Fri, Jun 30, 2017 at 11:16 AM, Neelesh <neele...@gmail.com> wrote: > >> 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-seco >> ndary-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 >>> >>> >> >> >
