On Fri, Jul 15, 2016 at 12:26 AM, AndreyVel <andrey4...@gmail.com> wrote:
> Good feature may be Aggregated cache - analog materialized view in DBMS > Aggregated cache is great for performance (KPI, analytecal reports). > Do you mean a copy of the aggregated data in another cache? What happens when the data in the original caches is updated? > > Recently I learned network traffic between nodes when node restart/startup > and do no found any compressing for transferred data. > Agree, we should allow users compress the data. I am not an expert on Ignite messaging, but would be nice if some of the committers could comment on this. > > I know there is IgniteDataStreamer for writing cache, but how about > reading cache as stream for iterate all elements with scan performane 1-3M > tuple/sec? > We already have Scan queries which allow for paginated iteration with filters. Are you suggesting something beyond this? > > > 14.07.2016 4:43, Alexey Goncharuk пишет: > > So, no excitement about Ignite 2.0? :) >> >> I went ahead and created a 2.0 version in Ignite Jira, and included the >> following tickets so far based on the chance that this ticket will require >> breaking changes in APIs/Configuration >> - IGNITE-3469 - Get rid of deprecated APIs and code >> - IGNTIE-3477 - Rework offheap storage >> - IGNITE-3478 - Transactional SQL >> - IGNITE-1605 - Provide stronger data loss check >> - IGNITE-3306 - Extend IgniteCluster interface with the methods to send >> and receive custom discovery events >> >> I believe that there are many more changes that we wanted to make but >> delayed because they would break binary compatibility, so if you have >> something in mind - it's time to create a ticket or assign it to 2.0 if it >> exists. It's good to know the scope of work. >> >> Also, it would be great if you review/comment the above-mentioned tickets. >> >> Thanks, >> AG >> >> >
