Interesting update. I was able to create the index when I changed the columns in the INCLUDE section. The column that causes the NPE is defined as a BIGINT. Creating the index using a column that is a VARCHAR and one that is a DECIMAL works just fine.
On Thu, Feb 13, 2014 at 1:13 PM, Justin Workman <[email protected]>wrote: > --silent is already set to false and --verbose is set to true. > > > On Thu, Feb 13, 2014 at 1:03 PM, James Taylor <[email protected]>wrote: > >> Modify the sqlline.sh by passing through the --verbose option and you >> should see the full stack trace. >> >> >> >> >> On Thu, Feb 13, 2014 at 11:48 AM, Justin Workman < >> [email protected]> wrote: >> >>> The missing double quote was a typo. This is the only error I get in the >>> sqlline shell. I'll check the region server logs again. >>> >>> Sent from my iPhone >>> >>> On Feb 13, 2014, at 12:46 PM, James Taylor <[email protected]> >>> wrote: >>> >>> Can you include the stack trace please? Also, your CREATE INDEX >>> statement is missing a double quote after >>> relatedKeywordRank. >>> >>> Does the existing HBase table use the expected serialization format for >>> Phoenix? If everything is strings and you don't have a composite row key, >>> then it should be ok. >>> >>> Thanks >>> >>> >>> On Thu, Feb 13, 2014 at 10:59 AM, Justin Workman < >>> [email protected]> wrote: >>> >>>> I am testing 2.2.3 and I get and ArrayIndexOutOfBoundsException when >>>> creating an index with more than 1 column in the INCLUDE statement. >>>> >>>> CREATE INDEX KWD_IDX ON "keywordideas" ("jobName","parentKeyword") >>>> INCLUDE ("keywordText","relatedKeywordRank); >>>> >>>> Error: java.lang.ArrayIndexOutOfBoundsException (state=08000,code=101) >>>> >>>> Is this a bug, or has something changed with 2.2.3? The table was >>>> created on top of an existing HBase table. >>>> >>>> Thanks >>>> Justin >>>> >>> >>> >> >
