Hi, Its not clear why you want to store secondary index in Elastic search. IMO, using Elastic search to store scondary index is a very abnormal choice. Have you run into performance problems? Your app will not be interacting with HDFS directly. HBase/Phoenix interacts with hdfs and it has pretty decent performance. Also, IMO, Elastic search doesnt scales as well as HBase/Phoenix. HBase/Phoenix can easily store PB's of data. Do you have a very specific use case to store secondary index in Elastic search?
~Anil On Thu, Mar 3, 2016 at 2:24 AM, Naveen Nahata ( SC ) < [email protected]> wrote: > Hi, > > > > I am looking possibility to extend phoenix where secondary index could be > stored in elastic search ( instead of HDFS ). Please provide me your > opinion on this. > > > > As per my understanding elastic search is better for retrieving realtime > small to larger data set while HDFS is good for large to very-large data > sizes. > > > > -Naveen Nahata > -- Thanks & Regards, Anil Gupta
