There is no dirty read issue. If the new data(actually the new segment) is not cube ready, user could not query that data. It's transparent to client query. The query will not wait for the building/refreshing cube. The incremental build is to build new segment.
2017-05-12 2:18 GMT+08:00 Nirav Patel <[email protected]>: > Hi, > > I understand currently kylin does't support partial changes to existing > cube data. In which case entire cube has to be rebuild. WHat is the impact > of it on clients/query interface? Do they have to wait when cube is getting > refreshed? > Also what happens during incremental refresh? If some client query for new > data which are being built would kylin allow dirty read on cube that is > being built? > > Thanks, > Nirav > > > > [image: What's New with Xactly] <http://www.xactlycorp.com/email-click/> > > <https://www.nyse.com/quote/XNYS:XTLY> [image: LinkedIn] > <https://www.linkedin.com/company/xactly-corporation> [image: Twitter] > <https://twitter.com/Xactly> [image: Facebook] > <https://www.facebook.com/XactlyCorp> [image: YouTube] > <http://www.youtube.com/xactlycorporation>
