Hi Luke and other Seniors, I come from Big Data Center of excellence from an Indian IT major.
We have been experimenting with the idea of serving cubes through ElasticSearch REST API. This is not related to Kylin. This is our own internal development. But, I would like to hear some feedback from the designers, architects and developers in this forum. Thanks in advance for your time. The motivation for this is --- Once the cube is built, it needs to be served. The query looks somewhat like this: "Given ProductID=*, Year=2015, Fetch All Quantities Sold" "Given ProductID=XX, Fetch how much it has sold every Month" Find all entries that match K1=V1, K2=V2 This relieves us from lot of things - storage, REST API etc. and makes the cubes easily searchable. However, we don't do SQL/MDX on top of it. Tableau 9.1Beta is experimenting with Web-Data-Connector which we believe can be used for Visualization... Apart from that, we experimented with a few auto-generated Kibana dashboards which were just okay. But Kibana was not designed for Cubes and so it has its own limitations. I would love to hear some feedback from the architects regarding the Pros/Cons of this approach. Thanks, Best, Sarnath
