Hi Kunal, IndexServer is quiet an efficient method to solve the problem of index cache and it's great that someone finally tries to implement this. However after I went through your design document, I get some questions for this and I'll explain those as following:
1. For the 'backgroud' chapter, I think actually it is the type of pruning (distribute-pruning or not) that matters, not the type of datamaps (default or bloomfilter). 2. Extensibility of the IndexServer 2.1 In the design document, why do you finally choose 'one more spark cluster' as the IndexServer? 2.2 Have you considered other types of IndexServer such as a DB, another in-memory storage engine or even treat the current implementation as an embedded IndexServer? If yes, Will the base IndexServer be enough extensible to support other them during your implementation and design? 2.3 What are the interfaces that the IndexServer will expose to offer service? I also didn't get this info. 3. For the IndexServer, will multiple tenants also be OK? 4. During coding, will IndexServer be in a separate module? -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
