Hi Igniters, I had a look into IgniteDataStreamer. As far as I understand, currently it just works incorrectly for MVCC tables. It appears as a blocker for releasing MVCC. The simplest thing is to refuse creating streamer for MVCC tables.
Next step could be hair splitting of related use cases. For me, initial load and continuous streaming look quite different cases and it is better to keep them separate at least at API level. Perhaps, it is better to separate API basing on user experience. For example, DataStreamer could be considered tool without surprises (which means leaving data always consistent, transactions). And let's say BulkLoader is a beast for fastest data loading but full of surprises. Such surprises could be locking tables, rolling back user transactions and so on. So, it is of very limited use (like initial load). Keeping API entities separate looks better for me than introducing multiple modes, because separated entities are easier for understanding and so less prone to user mistakes. -- Best regards, Ivan Pavlukhin
