Added C++ section. Best Regards, Igor
On Tue, May 2, 2017 at 1:06 AM, Rishi Yagnik <[email protected]> wrote: > OK good to know ..Thanks.. > > On Mon, May 1, 2017 at 5:03 PM, Denis Magda <[email protected]> wrote: > > > Yes, this affected the XML part either. Honestly, I don’t think we should > > say about the XML explicitly because there we define and instantiate the > > same Java beans. It’s just one more way how you can create your object > like > > IgniteConfiguration. > > > > — > > Denis > > > > > On May 1, 2017, at 2:56 PM, Rishi Yagnik <[email protected]> > wrote: > > > > > > Denis, > > > > > > IgniteConfiguration's `getGridName/setGridName` methods are deprecated > > and > > > will be removed in later releases. Use IgniteConfiguration's > > > `getIgniteInstanceName/setIgniteInstanceName` instead. > > > > > > For example, > > > > > > <bean id="ignite.cfg" > > > class="org.apache.ignite.configuration.IgniteConfiguration"> > > > > > > <property name="gridName" value="WebGrid"/> > > > .... > > > </bean> > > > > > > Does it mean that xml configuration would also be no longer supported ? > > if > > > yes, shall we add one liner in the document related to xml > configuration > > ? > > > > > > Thanks, > > > > > > > > > On Mon, May 1, 2017 at 4:47 PM, Denis Magda <[email protected]> wrote: > > > > > >> Folks, > > >> > > >> I’ve walked through the changes that broke compatibility with Ignite > 1.x > > >> and polished the migration guide: > > >> https://cwiki.apache.org/confluence/display/IGNITE/ > > >> Apache+Ignite+2.0+Migration+Guide > > >> > > >> * Vovan, Sergi, please introduce and fill in SQL part. > > >> * Vovan, please review and extend “Binary Marshalling” section if > > needed. > > >> * Igor Sapego, do we need to mention any C++ changes there? > > >> > > >> > > >> — > > >> Denis > > >> > > >>> On Jan 11, 2017, at 8:47 PM, Denis Magda <[email protected]> > wrote: > > >>> > > >>> Dmitriy, > > >>> > > >>> Few number of people contribute to readme.io documentation and I > don’t > > >> want to create an account only if someone needs to put a row in the > > >> migration guide. On the other hand, everyone can have an access to the > > wiki > > >> and update page there directly. I’ll create a page on readme.io with > > >> content from the wiki page once 2.0 gets released. That was the plan. > > >>> > > >>> — > > >>> Denis > > >>> > > >>>> On Jan 11, 2017, at 6:34 PM, Dmitriy Setrakyan < > [email protected] > > > > > >> wrote: > > >>>> > > >>>> Denis, > > >>>> > > >>>> I would rather have these changes tracked on a hidden readme.io > page. > > >> This > > >>>> way we can publish it whenever 2.0 is released. You can have the URL > > to > > >>>> that page on Ignite wiki. > > >>>> > > >>>> D. > > >>>> > > >>>> On Wed, Jan 11, 2017 at 2:18 PM, Denis Magda <[email protected]> > > wrote: > > >>>> > > >>>>> Igniters, > > >>>>> > > >>>>> There will be many changes in 2.0. Some API can be deprecated while > > the > > >>>>> other removed completely. Let’s track all this kind of changes in > 2.0 > > >>>>> migration guide making a life for our users easier when they will > be > > >>>>> switching from 1.x to 2.0 version. Add this page to your bookmarks > > and > > >>>>> don’t forget to update whenever is needed: > > >>>>> https://cwiki.apache.org/confluence/display/IGNITE/ > > >>>>> Apache+Ignite+2.0+Migration+Guide <https://cwiki.apache.org/ > > >>>>> confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide> > > >>>>> > > >>>>> — > > >>>>> Denis > > >>> > > >> > > >> > > > > > > > > > -- > > > Rishi Yagnik > > > > > > > -- > Rishi Yagnik >
