ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Pavlov <dpavlov....@gmail.com>
Subject Re: Apache Ignite 2.7 release
Date Fri, 24 Aug 2018 21:50:20 GMT
Hi Dmitriy, I suppose it highly depends on how fast community will come to
a consensus about design. So it is up to us to make this happen

сб, 25 авг. 2018 г. в 0:05, Dmitriy Setrakyan <dsetrakyan@apache.org>:

> Nikolai,
>
> To my knowledge, some significant changes to the service grid
> implementation were going to make it into 2.7. However, I am right now
> seeing other threads about the service grid in which the new design is just
> being discussed. This shows that service grid is not release ready.
>
> Do you know whether it is ready or not? Can we get a list of tickets on the
> service grid that we should be monitoring?
>
> D.
>
>
> On Fri, Aug 24, 2018 at 5:01 AM, Nikolay Izhikov <nizhikov@apache.org>
> wrote:
>
> > Hello, Yakov.
> >
> > Blocker Tickets.
> >
> > Open:
> >
> > IGNITE-9184     Mikhail Cherkasov       Cluster hangs during concurrent
> > node restart and continues query registration
> > IGNITE-8552     Vladimir                Ozerov  Unable to use date as
> > primary key
> > IGNITE-6980     Aleksey Plekhanov       Automatic cancelling of hanging
> > Ignite operations
> > IGNITE-8671     Peter Ivanov            Provide instructions on running
> > Apache Ignite on Windows 10 WSL Environment
> > IGNITE-7009     Vladimir Ozerov         NPE when Ignite persistence is
> > enabled for Hadoop accelerator
> > IGNITE-8803     Alexey Goncharuk        Need to fix Ignite QUIET log
> output
> > IGNITE-8802     Alexey Goncharuk        Need to fix Ignite INFO output
> > IGNITE-5618     Dmitriy Pavlov          .NET: Ignite fails with OOM on
> > startup under x86 (32 bit) with default configuration
> > IGNITE-9352     Unassigned              Web Console: Investigate how
> > correctly use package-lock.json
> > IGNITE-9347     Unassigned              Attempt to start a dynamic cache
> > with invalid configuration leads to exchange worker death
> > IGNITE-9202     Unassigned              .NET `TestRemoteNodes` fails with
> > "Failed to map SQL query to topology"
> > IGNITE-7793     Unassigned              SQL does not work if value has
> > index filed which name equals to affinity key name
> > IGNITE-8890     Unassigned              Ignite YARN Kerberos - Delegation
> > Token renewal
> > IGNITE-8771     Unassigned              OutOfMemory in Cache2 suite in
> > master branch on TC
> > IGNITE-8770     Unassigned              OutOfMemory in Queries1 suite in
> > master branch on TC
> > IGNITE-8767     Unassigned              JavaClient test suite times out
> in
> > master branch
> > IGNITE-5302     Unassigned              Empty LOST partition may be used
> > as OWNING after resetting lost partitions
> > IGNITE-7813     Unassigned              Method org/apache/ignite/cache/
> > hibernate/HibernateRegionFactory.start(Lorg/hibernate/boot/spi/
> > SessionFactoryOptions;Ljava/util/Properties;)V is abstract
> > IGNITE-8523     Unassigned              Java and Scala spark examples are
> > mixed
> > IGNITE-8772     Unassigned              WebSessionFilter does not work
> > with jetty 9.4 anymore
> > IGNITE-6064     Unassigned              Rework control.sh script
> > IGNITE-8454     Unassigned              Hadoop module compilation failure
> > under JDK9
> > IGNITE-7620     Unassigned              Not able to run query in Ignite
> > YARN
> >
> > In Progress:
> >
> >
> > IGNITE-9305     Pavel Pereslegin        Wrong off-heap size is reported
> > for a node
> > IGNITE-7728     Artem Budnikov          Put together a doc that shows how
> > to blend SQL with k/v APIs
> > IGNITE-7721     ruchir choudhry         Apache Ignite web session
> > clustering stack after login success
> >
> > Patch Available:
> >
> > IGNITE-9068     Ilya Lantukh            Node fails to stop when
> > CacheObjectBinaryProcessor.addMeta() is executed inside guard()/unguard()
> > IGNITE-7251     Anton Vinogradov        Remove term "fabric" from Ignite
> > deliverables
> > IGNITE-9030     Peter Ivanov            Apache Ignite 2.7 Linux packages
> > version update
> >
> > В Пт, 24/08/2018 в 14:47 +0300, Yakov Zhdanov пишет:
> > > Igniters,
> > >
> > > We should definitely expand the list of important tickets adding
> tickets
> > > related to (1) Partition Map Exchange speed up and (2) SQL memory
> > > optimization tickets. Alex Goncharuk, Vladimir, can you please add
> labels
> > > to corresponding tickets.
> > >
> > > Also we have several blocker tickets (mostly related to failing tests)
> > not
> > > yet assigned to anyone. Nikolay, can you please list those tickets and
> > ask
> > > community to pick them up?
> > >
> > > We have 556 open tickets now according to [1]. This seems a bit to
> much.
> > > Can I ask everyone to review tickets assigned to yourselves and move
> > those
> > > that will not be fixed. Then Nikolay will process the ones that are not
> > > assigned yet. Nikolay, can you take a look please?
> > >
> > > --Yakov
> > >
> > > 2018-08-24 12:58 GMT+03:00 Nikolay Izhikov <nizhikov@apache.org>:
> > >
> > > > Hello, Dmitriy.
> > > >
> > > > Release page - [1]
> > > >
> > > > > I think it is important to include the links to all important Jira
> > > >
> > > > tickets> in this thread
> > > >
> > > > Open:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-6980 - Automatic
> > cancelling
> > > > of hanging Ignite operations
> > > > https://issues.apache.org/jira/browse/IGNITE-5473 - Create ignite
> > > > troubleshooting logger
> > > > https://issues.apache.org/jira/browse/IGNITE-6903 - Implement new
> JMX
> > > > metrics for Indexing
> > > > https://issues.apache.org/jira/browse/IGNITE-6507 - Commit can be
> > lost in
> > > > network split scenario
> > > >
> > > > In Progress:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-9349
> > > >
> > > > Patch Available:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-7251 - Remove term
> > "fabric"
> > > > from Ignite deliverables
> > > >
> > > >
> > > > Resolved:
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-8780 - File I/O
> > operations
> > > > must be retried if buffer hasn't read/written completely
> > > > https://issues.apache.org/jira/browse/IGNITE-5059 - Implement
> logistic
> > > > regression
> > > > https://issues.apache.org/jira/browse/IGNITE-3478 - Multi-version
> > > > concurrency control
> > > > https://issues.apache.org/jira/browse/IGNITE-9340 - Update jetty
> > version
> > > > in Apache Ignite (ignite-rest-http)
> > > >
> > > >
> > > >
> > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > Apache+Ignite+2.7
> > > >
> > > > В Пт, 24/08/2018 в 10:47 +0300, Nikolay Izhikov пишет:
> > > > > Hello, Pavel.
> > > > >
> > > > > Please, be aware of IGNITE-6055 [1]
> > > > >
> > > > > I'm edit thin protocol in that ticket.
> > > > > I can't support changes in Python and PHP clients, because, they
> are
> > not
> > > >
> > > > merged in master, yet.
> > > > > Write me, If you have any questions about new fields.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-6055
> > > > >
> > > > > В Чт, 23/08/2018 в 18:02 -0700, Pavel Petroshenko пишет:
> > > > > > Hi Nikolay,
> > > > > >
> > > > > > Python [1], PHP [2], and Node.js [3] thin clients will get into
> the
> > > >
> > > > release.
> > > > > >
> > > > > > Thanks,
> > > > > > p.
> > > > > >
> > > > > > [1] https://jira.apache.org/jira/browse/IGNITE-7782
> > > > > > [2] https://jira.apache.org/jira/browse/IGNITE-7783
> > > > > > [3] https://jira.apache.org/jira/browse/IGNITE-7777
> > > > > >
> > > > > >
> > > > > > On Tue, Aug 21, 2018 at 12:20 PM, Dmitriy Setrakyan <
> > > >
> > > > dsetrakyan@apache.org> wrote:
> > > > > > > Thanks, Nikolay!
> > > > > > >
> > > > > > > I think it is important to include the links to all important
> > Jira
> > > >
> > > > tickets
> > > > > > > in this thread, so that the community can track them.
> > > > > > >
> > > > > > > D.
> > > > > > >
> > > > > > > On Tue, Aug 21, 2018 at 12:06 AM, Nikolay Izhikov <
> > > >
> > > > nizhikov@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello, Dmitriy.
> > > > > > > >
> > > > > > > > I think Transparent Data Encryption will be available
in 2.7
> > > > > > > >
> > > > > > > > В Пн, 20/08/2018 в 13:20 -0700, Dmitriy Setrakyan
пишет:
> > > > > > > > > Hi Nikolay,
> > > > > > > > >
> > > > > > > > > Thanks for being the release manager!
> > > > > > > > >
> > > > > > > > > I am getting a bit lost in all these tickets.
Can we
> specify
> > some
> > > > > > > > > high-level tickets, that are not plain bug fixes,
which
> will
> > be
> > > > > > > >
> > > > > > > > interesting
> > > > > > > > > for the community to notice?
> > > > > > > > >
> > > > > > > > > For example, here are some significant tasks
that the
> > community
> > > >
> > > > is either
> > > > > > > > > working on or has been working on:
> > > > > > > > >
> > > > > > > > > - Node.JS client
> > > > > > > > > - Python client
> > > > > > > > > - Transactional SQL (MVCC)
> > > > > > > > > - service grid stabilization
> > > > > > > > > - SQL memory utilization improvements
> > > > > > > > > - more?
> > > > > > > > >
> > > > > > > > > Can you please solicit status from the community
for these
> > tasks?
> > > > > > > > >
> > > > > > > > > D.
> > > > > > > > >
> > > > > > > > > On Mon, Aug 20, 2018 at 11:22 AM, Nikolay Izhikov
<
> > > >
> > > > nizhikov@apache.org>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hello, Igniters.
> > > > > > > > > >
> > > > > > > > > > I'm release manager of Apache Ignite 2.7.
> > > > > > > > > >
> > > > > > > > > > It's time to start discussion of release.
[1]
> > > > > > > > > >
> > > > > > > > > > Current code freeze date is September, 30.
> > > > > > > > > > If you have any objections - please, responsd
to this
> > thread.
> > > > > > > > > >
> > > > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/
> > > > > > > >
> > > > > > > > Apache+Ignite+2.7
> > > > > > > >
> >
>

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