ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Вадим Опольский <vaopols...@gmail.com>
Subject Re: Apache Ignite 2.0 Release
Date Thu, 06 Apr 2017 09:58:32 GMT
Hello community!

Denis,  issue IGNITE-1794
<https://issues.apache.org/jira/browse/IGNITE-1794> - Hibernate 5 Support
has been ready for review from 24 March.

The tests in Team City executed successfully.

Vadim Opolski

2017-04-06 5:04 GMT+03:00 Denis Magda <dmagda@apache.org>:

> *Denis Magda:*
> IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> - Provide
> integration with Spring Data
>
>
> Will be finished and merged by the code freeze date. I’m on a business
> trip now and don’t have extra time to complete the feature.
>
> Plus, following your template these are additional tickets:
>
> *Alexey Kuznetsov*
> IGNITE-4349 <https://issues.apache.org/jira/browse/IGNITE-4349> - Discontinue
> the schema-import utility
>
> *Sergey Chugunov*
> IGNITE-4536 <https://issues.apache.org/jira/browse/IGNITE-4536> - Update
> metrics for new offheap storage
>
> *Nikita Ivanov*
> IGNITE-4572 <https://issues.apache.org/jira/browse/IGNITE-4572> - Machine
> Learning: Develop distributed algebra support for dense and sparse data
> sets.
>
> *Roman Shtykh*
> IGNITE-4539 <https://issues.apache.org/jira/browse/IGNITE-4539> -
> RocketMQ Data Streamer
>
> *Vadim Opolski*
> IGNITE-1794 <https://issues.apache.org/jira/browse/IGNITE-1794> -
> Hibernate 5 Support
>
> —
> Denis
>
> On Apr 5, 2017, at 9:39 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
>
> Guys,
>
> Please provide a status underneath every ticket listed below, so we can get
> a full picture in one email thread:
>
> *Alexey Goncharuk:*
> IGNITE-3477 <https://issues.apache.org/jira/browse/IGNITE-3477> - Rework
> offheap storage
> IGNITE-4337 <https://issues.apache.org/jira/browse/IGNITE-4337> -
> Introduce
> persistence interface to allow build reliable persistence plugins
>
> *Alexander Menshikov:*
> IGNITE-4699 <https://issues.apache.org/jira/browse/IGNITE-4699> -
> Introduce
> custom configurable executors.
>
> *Denis Magda:*
> IGNITE-1192 <https://issues.apache.org/jira/browse/IGNITE-1192> - Provide
> integration with Spring Data
>
> *Dmitriy Karachentsev:*
> IGNITE-4477 <https://issues.apache.org/jira/browse/IGNITE-4477> - Fix
> IgniteFuture.listen() and IgniteFuture.chain() semantics
>
> *Ilya Lantukh:*
> IGNITE-4535 <https://issues.apache.org/jira/browse/IGNITE-4535>
> <https://issues.apache.org/jira/browse/IGNITE-4535>- Add option to store
> deserialized values on-heap
>
> *Ivan Rakov:*
> IGNITE-4534 <https://issues.apache.org/jira/browse/IGNITE-4534> -
> Implement
> offheap eviction policies based on page memory
>
> *Sergey Kalashnikov:*
> IGNITE-3595 <https://issues.apache.org/jira/browse/IGNITE-3595> - Improve
> Enum fields handling in SQL.
>
> *Sergi Vladykin:*
> IGNITE-3869 <https://issues.apache.org/jira/browse/IGNITE-3869> - Reduce
> number of temporary objects produced by H2
>
> *Taras Ledkov:*
> IGNITE-3469 <https://issues.apache.org/jira/browse/IGNITE-3469> - Get rid
> of deprecated APIs and entities
>
> *Vladimir Ozerov:*
> IGNITE-4565 <https://issues.apache.org/jira/browse/IGNITE-4565> - Support
> CREATE INDEX DDL statements
>
> *Yakov Zdanov:*
> IGNITE-4799 <https://issues.apache.org/jira/browse/IGNITE-4799> - Remove
> TcpDiscoverySpi.heartbeatsFrequency parameter
>
>
> *Denis*, we still have 5 issues that are *unassigned*. Are they supposed to
> be getting into release?
>
> IGNITE-3488 <https://issues.apache.org/jira/browse/IGNITE-3488> - Prohibit
> null as name in all the components (cache name first of all).
> IGNITE-3596 <https://issues.apache.org/jira/browse/IGNITE-3596> - Hadoop
> edition can't be compiled against spark 2.0.0
> IGNITE-4794 <https://issues.apache.org/jira/browse/IGNITE-4794> -
> Reconsider
> CachePeekMode.ONHEAP
> IGNITE-2202 <https://issues.apache.org/jira/browse/IGNITE-2202> - Local
> server query result doesn't include versions in entries
> IGNITE-2398 <https://issues.apache.org/jira/browse/IGNITE-2398> - .NET:
> Change default mapper behavior
>
>
> D.
>
> On Wed, Apr 5, 2017 at 6:07 PM, Denis Magda <dmagda@apache.org> wrote:
>
> Dmitriy,
>
> You can find all the required tickets with contributors assigned here:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#
> ApacheIgnite2.0-Requiredtickets <https://cwiki.apache.org/
> confluence/display/IGNITE/Apache+Ignite+2.0#ApacheIgnite2.0-
> Requiredtickets>
>
> In short, Alex G., Sergi, Vovan, Taras, Yakov, Sam, etc. (almost all the
> community) please share your readiness with the rest of the community.
>
> —
> Denis
>
> On Apr 5, 2017, at 9:03 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>
>
> wrote:
>
>
> Denis,
>
> I think it will be worth while to list all the tickets by status together
> with a name of the engineer assigned to it. This way most folks involved
> would provide a response sooner.
>
> What do you think?
>
> D.
>
> On Wed, Apr 5, 2017 at 1:27 PM, Denis Magda <dmagda@apache.org> wrote:
>
> Igniters,
>
> What’s the overall status of 2.0 release? I see that many tickets
>
> related
>
> to the page memory [1] are still in the open state and, looks like, this
> new memory architecture has not been fully merged yet. In addition, a
>
> new
>
> version of H2 has to be released prior to 2.0.
>
> All this threatens the release schedule we agreed on. According to the
> plan the next week is a week of code freeze:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0#
> ApacheIgnite2.0-Releasephases <https://cwiki.apache.org/
> confluence/display/IGNITE/Apache+Ignite+2.0#
>
> ApacheIgnite2.0-Releasephases>
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-3477 <
> https://issues.apache.org/jira/browse/IGNITE-3477>
>
> —
> Denis
>
> On Mar 31, 2017, at 4:02 AM, Vladimir Ozerov <vozerov@gridgain.com>
>
> wrote:
>
>
> Another big merge - now almost all our setters on public configuration
> return "this" instance to allow for convenient chaining [1]. Big
> thanks to *Andrew
> Mashenkov* for making this happen.
> Ideally I would also try to replace "set(Collection<Something>)" with "
> set(Something...)". This should make configuration even more easier.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4564
>
> On Fri, Mar 31, 2017 at 2:18 AM, Denis Magda <dmagda@apache.org>
>
> wrote:
>
>
> Vovan,
>
> I expect to finalize and merge Spring Data Integration by the code
>
> freeze
>
> time (April 14th):
> IGNITE-1192Provide integration with Spring Data <
> https://issues.apache.org/jira/browse/IGNITE-1192>
>
> —
> Denis
>
> On Mar 30, 2017, at 3:10 PM, Vladimir Ozerov <vozerov@gridgain.com>
>
> wrote:
>
>
> Igniters,
>
> We are getting closer to proposed code freeze date. Could you please
>
> go
>
> through the list of required [1] tickets and provide brief update on
>
> where
>
> we are?
>
> As per myself, I am curerntly working on CREATE/DROP index feature
> stabilization and expect it to be ready for review on the next week.
>
> Vladimir.
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/
>
> Apache+Ignite+2.0
>
>
> On Tue, Mar 28, 2017 at 9:11 PM, nivanov <nivanov30@gmail.com>
>
> wrote:
>
>
> I think we can make it on time to add IgniteML (a.k.a. distributed
>
> math) to
>
> 2.0 release pipeline.
>
>
>
> --
> View this message in context: http://apache-ignite-
> developers.2346864.n4.nabble.com/Apache-Ignite-2-0-Release-
> tp15690p15857.html
> Sent from the Apache Ignite Developers mailing list archive at
>
> Nabble.com.
>
>
>
>
>
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message