Hi, But after seeing your explanation below I understand that option 2 above is > not really the way Ignite is supposed to be used - even if it is on top of > hadoop. Did I get that right?
In this configuration, Ignite will not be on top of Hadoop, it will be close to it - deployed as separate storage for faster performance. Synchronization is possible if needed. As for the other details, let's connect privately, more details are needed to give useful suggestions. -- Denis Magda On Wed, May 15, 2019 at 4:15 AM m4mmr <rmam...@gmail.com> wrote: > Hi Denis, > > Thank you very much for a good response. Definitely helps. Hope I can ask > one follow-up question which I feel I did not make so clear from the > beginning: > > The business has a very strong (non-negotiable) requirement on that the > data > warehouse should be modeled with high normalisation. These model > requirements prevents us from building the data warehouse on hadoop(hive). > We won't get rid of hadoop though - it is still used for offloading the > operational source systems. > > Therefore we need to: > 1. Either build a data warehouse on a RDBMS on top of the hadoop - to meet > the business requirements. > 2. Or build the relational data warehouse directly on Ignite with > Persistence Store - on top of hadoop. > > But after seeing your explanation below I understand that option 2 above is > not really the way Ignite is supposed to be used - even if it is on top of > hadoop. Did I get that right? > > We can of course use Ignite with the RDBMS from option 1 as persistence > store for making the DWH offloading more effective later on. Will look into > that. > > Again - thank you very much for you pedagogical response Denis. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
