Re: monitoring status of CREATE INDEX operation

Thanks James, all CAPS did the trick! Yes, the event table is already IMMUTABLE_ROWS=true. Thanks again, Nathan On Fri, Aug 12, 2016 at 10:59 AM, James Taylor wrote: > In your IndexTool invocation, try use all caps for your table and index > name. Phoenix normalizes

Re: monitoring status of CREATE INDEX operation

In your IndexTool invocation, try use all caps for your table and index name. Phoenix normalizes names by upper casing them (unless they're in double quotes). One other unrelated question: did you declare your event table with IMMUTABLE_ROWS=true (assuming it's a write-once table)? If not, you

Re: monitoring status of CREATE INDEX operation

Thanks for the detailed info. I took the advice of using the ASYNC method. The CREATE statement executes fine and I end up with an index table showing in state BUILDING. When I kick off the MR job with `hbase org.apache.phoenix.mapreduce.index.IndexTool --schema trans --data-table event

Re: monitoring status of CREATE INDEX operation

Hi Nathan, If your table is large, I'd recommend creating your index asynchronously. To do that, you'd add the ASYNC keyword to the end of your CREATE INDEX call. In this case, the index will be built through Map Reduce in a more resilient manner (i.e. the client going up or down won't impact it

monitoring status of CREATE INDEX operation

Hi All, I executed a CREATE INDEX against a fairly large table. And I received a timeout error after a minute or two, which I understand is expected. `!tables` in sqlline shows the index is still in BUILDING state after 2 hours, which may be accurate since it is a pretty large table and my cluster