No, that's currently not possible. You'd may be able to leverage one of the following to help you, though: - parallel arrays as you've mentioned - different tables with an FK (and likely an index) between them - dynamic columns (http://phoenix.apache.org/dynamic_columns.html) - on-the-fly updatable VIEW creation, where the VIEW represents the set of tuples (http://phoenix.apache.org/views.html)
The implementation of a STRUCT data type (PHOENIX-477) or support for JSON (PHOENIX-628) may help you as well. Would it be possible to share more details about your use case? On Tue, Dec 23, 2014 at 2:07 PM, Alex Kamil <[email protected]> wrote: > is there a way to represent Map.Entry<K,V>[] as a column value in phoenix, > i.e. store an array of tuples <K,V> instead of creating two arrays: K > VARCHAR ARRAY[] and V VARCHAR ARRAY[]
