I had an idea a while back that I’ll share here because it’s relevant. It’s
basically a combined index, or index group, and it would work in this case. It
could be implemented in both global and local indexes. The data for two or more
indexes would be interleaved. For a local index, the
Please file a JIRA for the ability to use multiple tables for an OR query
(but that's a pretty big effort). In the meantime, you may be able to work
around the lack of support for UNION by doing a merge sort yourself on the
client as an efficient way to dedup. For example, if you have a table like
On 10/3/17 3:00 AM, Andrzej wrote:
W dniu 03.10.2017 o 01:35, Josh Elser pisze:
Apache Phoenix does not provide/ship an ODBC driver.
One is provided by Hortonworks, but it is not open source. Would
recommend you use their forums if you need more information than is
included in the below
W dniu 03.10.2017 o 01:35, Josh Elser pisze:
Apache Phoenix does not provide/ship an ODBC driver.
One is provided by Hortonworks, but it is not open source. Would
recommend you use their forums if you need more information than is
included in the below tutorial.
