So James' ticket seems to indicate this is intended behavior, have you resolved that?  It seems like an index on arbitrarily fixed-with bytes aren't a bad thing.

On Wed, Mar 26, 2014 at 3:49 PM, Samarth Jain <> wrote:
Hi Dan,

Thanks for reporting. 

I am working on a fix for this. Please see:


On Wed, Mar 26, 2014 at 3:42 PM, Dan Di Spaltro <> wrote:
I have a table with two indexes

create table auth.account_users 
    ordered_id BINARY(16) not null PRIMARY KEY, 
    account_id BINARY(16) not null, 
    user_id BINARY(16) not null, 
    default BOOLEAN, 
    created_at TIMESTAMP 

CREATE INDEX auth_account_users_user_idx ON auth.account_users(user_id) 

CREATE INDEX auth_account_users_account_idx ON auth.account_users(account_id)

The creation works fine on this but during insert I get the following message, I am wondering is this intended?  Judging by the code it should work... I am using the 4.0 RC btw.

java.lang.IllegalArgumentException: Unsupported non nullable index type BINARY
at org.apache.phoenix.util.IndexUtil.getIndexColumnDataType(
at org.apache.phoenix.index.IndexMaintainer.buildRowKey(
at org.apache.phoenix.index.IndexMaintainer.buildUpdateMutation(
at org.apache.phoenix.util.IndexUtil.generateIndexData(
at org.apache.phoenix.execute.MutationState$
at org.apache.phoenix.execute.MutationState$
at org.apache.phoenix.execute.MutationState.commit(
at org.apache.phoenix.jdbc.PhoenixConnection.commit(
at org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(
at org.apache.phoenix.jdbc.PhoenixStatement.execute(
at org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(
at org.apache.phoenix.jdbc.PhoenixPreparedStatement.execute(

Dan Di Spaltro

Dan Di Spaltro