Re: Runtime DDL supported?

As we discussed, indexes across views are stored in a single HBase table associated with the original table (_IDX_). That's grand for limiting the number of HBase tables created, but I just realized that the actual index data within is differentiated by the 16-bit "viewIndexId", which limits us to

Re: Secondary index question

I believe this is the same bug we encountered with local indexes where Phoenix 4.13.1 failed to join back to the main table if the local index is not covering for all columns referenced in the WHERE. > On Feb 27, 2018, at 9:36 AM, James Taylor wrote: > > Please file a

Re: Secondary index question

Please file a JIRA and include the Phoenix and HBase version. Sounds like you’ve found a bug. On Tue, Feb 27, 2018 at 9:21 AM Jonathan Leech wrote: > I’ve done what you’re looking for by selecting the pk from the index in a > nested query and filtering the other column

Re: Secondary index question

I’ve done what you’re looking for by selecting the pk from the index in a nested query and filtering the other column separately. > On Feb 27, 2018, at 6:39 AM, Alexey Karpov wrote: > > Thanks for quick answer, but my case is a slightly different. I've seen these > links

Re: Secondary index question

Thanks for quick answer, but my case is a slightly different. I've seen these links and already use local index. All cases, described in faq, index_usage and any other, I've found in this user list, are about SELECT clause. In WHERE clause there is always field from the index. In my case in WHERE