Zhenya, Dmitriy,
hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from
2.7.6, i
have no clue - why,
The reason here is a lack of time to ensure that everything is fine
there. The patch is valuable but not so trivial. Honestly, I find it wrong
to merge a changes I am not sure with (yet). Especially in a hurry.
Sent from my iPhone
On 17 Aug 2019, at 13:13, Zhenya Stanilovsky
<arzamas...@mail.ru.INVALID> wrote:
I hope there is no data loss here, but index tree corruption can be
easily obtained.
Impact: someone believe that inline_size has been changed due to index
recreation but that`s not so.
Hi Evgeniy,
I can't review this change. We need approve of a committer, who is
SQL
expert, here.
What would be an impact on users if we don' include it into 2.7.6?
Is it a critical/data loss issue? If not, I agree it can wait for 2.8
release.
Sincerely,
Dmitriy Pavlov
сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky <arzamas...@mail.ru>:
hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from
2.7.6, i
have no clue - why, but seems i can`t merge it without his visa.
thanks.
Hi Igniters,
I also suggest adding newly created critical bug into scope
https://issues.apache.org/jira/browse/IGNITE-12081 (already
assigned
since
it was discussed before in private communication).
It is not a regression but can cause data corruption, so I'd
rather wait
for the fix.
Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the
first RC
during the weekend, so I would be grateful if fixes can be
cherry-piked
to
the branch today. Also, since narrow time limit, please trigger
Run All
after each commit in 2.7.6. This will allow to immediately locate
which
commit caused test failure.
Sincerely,
Dmitriy Pavlov
пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov <dpav...@apache.org>:
Hi Ivan,
yes, sure.
If it is cherry-picked without conflicts, just push it.
If it contains conflicts it is better to push to 2.7.6-based
branch and
start additional run-all, example
https://github.com/apache/ignite/pull/6781 -it is PR for
ignite-9562,
base: 2.7.6
Sincerely,
Dmitriy Pavlov
пт, 16 авг. 2019 г. в 12:28, Павлухин Иван <vololo...@gmail.com>:
Dmitriy,
We accomplished with
https://issues.apache.org/jira/browse/IGNITE-12068
Should I cherry-pick it to release branch?
пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov <dpav...@apache.org
:
Hi Igniters,
Yesterday was a planned date of code freeze.
So the scope (related both to features and to bugs) is final,
we're
entering to stabilization phase. Nothing can be included into
scope
besides
blockers approved by the release manager.
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
<
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process>
Unresolved tickets are:
IGNITE-12071 Eduard Shangareev
IGNITE-12068 Ivan Pavlukhin
IGNITE-9562 Eduard Shangareev
IGNITE-12057 Anton Kalashnikov
IGNITE-12061 Stanilovsky Evgeny
Sincerely,
Dmitriy Pavlov
чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky <
arzamas...@mail.ru
:
Dmitriy, review passed, plz proceed.
thanks !
I removed
https://issues.apache.org/jira/browse/IGNITE-12032
until
nobody
volunteer to complete the task.
Evgeniy, please keep me updated about IGNITE-12061.
чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
<arzamas...@mail.ru.invalid
:
yep, i`l try to call someone who probably familiar with
this
problem.
Ok, I've removed Spark from the scope.
What about the unassigned issue related to ODBC? It is
not
looking like
somebody will fix it before release.
Evgeniy Stanilovsky, what about
https://issues.apache.org/jira/browse/IGNITE-12061
<
https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro
do you have someone to review the fix?
чт, 15 авг. 2019 г. в 16:05, Denis Magda <
dma...@apache.org
:
Dmitry,
It would be better for us to put off the Spark upgrade
until
2.8 as
Nikolay
suggested. Let's release 2.7.6 as quickly as possible
to let
roll out
fixes
for the critical issues from the scope.
-
Denis
On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
dpav...@apache.org
wrote:
Nikolay, how long does it take to update? I will be
traveling
from
28
Aug
till 16 Sept. We can select new dates for release if
the
majority
of
fixes
can be done by 16 Sept, but can't be by 20 Aug.
Denis,
please
share
your
vision about selecting new dates.
*Voting Date: *Sept 18, 2019
*Release Date: *Sept 23, 2019
Issue
https://issues.apache.org/jira/browse/IGNITE-12032
<
https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
is
still
unassigned: Server node prints exception when ODBC
driver
disconnects
Igniters, who would like to pick up it? By default,
I'm
going
to
remove
it
from release
чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov <
nizhi...@apache.org
:
Hello, Igniters.
I try to upgrade Spark version but failed.
Seems, internal Spark API(External Catalog, SQL
planner)
that
we
use
changed a lot.
So it will take some time to upgrade version.
For now, I work hard to complete the second phase
of
IEP-35
so I
postpone
upgrade Spark version to Ignite 2.8.
В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov
пишет:
Hi Denis,
Sure, since code freeze is planned for today, I
don't
mind to
include
this
bug.
Ivan, could you complete this issue by 20 August?
BTW #1, Dmitriy Govoruchnin, please reply about
commit
for
https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
BTW #2, FYI, release page is now available here
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
BTW #3, FYI, release related test PR is here
https://github.com/apache/ignite/pull/6775 and
it's
TC
Bot
report is
here:
https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=ignite-2.7.6&action=Latest&baseBranchForTc=ignite-2.7.6
чт, 15 авг. 2019 г. в 13:55, Denis Magda <
dma...@apache.org
:
An Ignite user just reported a silly issue
that needs
to be
fixed
in
2.7.6:
https://issues.apache.org/jira/browse/IGNITE-12068
More details and context:
https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
Ivan, please help us to make it to the release.
-
Denis
On Tue, Aug 13, 2019 at 6:47 AM Denis Magda <
dma...@apache.org
wrote:
IGNITE-12507 (Persistence files are stored
to temp
dir) has
definitely be
added the scope and treated one of the main
release
drivers.
Dmitry, please let us know once the release
wiki
page
is
ready so
that we
can finalize the timelines based on chosen
scope.
-
Denis
On Mon, Aug 12, 2019 at 7:12 PM Dmitriy
Pavlov <
dpav...@apache.org
wrote:
Hi,
Thanks to everyone, who participated in the
discussion.
I would like to wait also fix for
https://issues.apache.org/jira/browse/IGNITE-12057
and discussion results for that issue:
https://lists.apache.org/thread.html/498a14b3971950a45ef57f45cc23d2438ce1afba000b586e230927bf@%3Cdev.ignite.apache.org%3E
Since some issues are still open, we'll
probably
move
some
dates
forward,
but it seems we managed to discuss scope
before
scope
freeze.
I consider now the scope is frozen - no new
feature
can
be
added
to the
scope of 2.7.6. We're entering the rampdown
phase.
Sincerely,
Dmitriy Pavlov
See
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
for
more details.
пн, 12 авг. 2019 г. в 16:37, Zhenya
Stanilovsky
< arzamas...@mail.ru.invalid
:
Hi al,, i also suggest to append [1],
cause it
could
produce
CorruptedTreeException in some scenario.
[1]
https://issues.apache.org/jira/browse/IGNITE-12061
Hi all,
Can we include
https://issues.apache.org/jira/browse/IGNITE-12060 ?
This is
a
https://issues.apache.org/jira/browse/IGNITE-11953
On Fri, Aug 9, 2019 at 10:04 AM Nikolay
Izhikov
<
nizhi...@apache.org
wrote:
Hello, Deni.
Nickolay, could you check if
that's a
quick
upgrade?
Yes, I will take a look.
В Чт, 08/08/2019 в 11:08 -0700,
Denis Magda
пишет:
Dmitry,
Please add this BTree corruption
fix to
the
scope:
https://issues.apache.org/jira/browse/IGNITE-11953
Plus, I would upgrade our Spark
integration
to
version
2.4
as
long
as
2.3
goes with limitations reported by
our
users:
https://issues.apache.org/jira/browse/IGNITE-12054
Nickolay, could you check if
that's a
quick
upgrade?
-
Denis
On Thu, Aug 8, 2019 at 10:40 AM
Dmitriy
Pavlov <
dpav...@apache.org >
wrote:
Hi Ivan, Ilya, Igniters,
I would like this release would
be as
minimal
as
possible.
According to dates proposed we
could
freeze
scope
at
12.08, 4
days
is
more
than enough to stand up and say,
‘Hey,
I
have
an
urgent
fix’.
But
it is
also ok for me if we decide to
have
more
relaxed
dates.
For now, I suppose the following
fixed
should
be
cherry-picked:
https://issues.apache.org/jira/browse/IGNITE-11767
(Blocker)
GridDhtPartitionsFullMessage
retains
huge
maps
on
heap
in
exchange
history
https://issues.apache.org/jira/browse/IGNITE-10451
(Major
Bug)
.NET:
Persistence does not work with
custom
affinity
function
https://issues.apache.org/jira/browse/IGNITE-9562
(Critical
Bug)
Destroyed
cache that resurrected on an old
offline
node
breaks
PME
But I will continue to research
JIRA.
Sincerely,
Dmitriy Pavlov
чт, 8 авг. 2019 г. в 17:30,
Павлухин
Иван
<
vololo...@gmail.com
:
What's the scope for this
release?
Same question.
On the other hand an idea of
2.7.6
release
attracts
me
because
having
a practice of doing frequent
minor
releases
can
help
us to
build
reliable and predictable
release
rails.
чт, 8 авг. 2019 г. в 15:09,
Ilya
Kasnacheev <
ilya.kasnach...@gmail.com >:
Hello!
What's the scope for this
release?
Regards,
--
Ilya Kasnacheev
чт, 8 авг. 2019 г. в 15:07,
Dmitriy
Pavlov
<
dpav...@apache.org
:
Hi Apache Ignite
Developers,
We seem to be on the same
page
about 2.8
release,
but
we’ve
started
new
practice - minor releases,
the
first
release
was
2.7.5.
Unfortunately,
there is a couple of
issues still
not
fixed
in
that
release,
so I
would
like to propose to prepare
one
more
minor
release
for
Apache
Ignite.
I propose my candidacy to
be
release
manager
once
again.
I could (of course with
help from
Peter
Ivanov)
do
some
additional
efforts
to complete and improve
process
doc
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
I propose (most
optimistic) dates
for
release
stages:
Scope Freeze: August 12,
2019
Code Freeze: August 15,
2019
Voting Date: August 22,
2019
Release Date: August 27,
2019
WDYT?
If nobody minds, I will
create
branch
2.7.6
based
on
2.7.5
and
set up
in
the TC Bot during the
weekend.
Sincerely,
Dmitriy Pavlov
--
Best regards,
Ivan Pavlukhin
--
Zhenya Stanilovsky
--
Zhenya Stanilovsky
--
Best regards,
Ivan Pavlukhin
