Awesome!
Thanks, Andrey!
> On 9 Jul 2018, at 18:57, Andrey Gura wrote:
>
> POM is updated in master branch.
>
> And no more commits to ignite-2.6 branch.
> On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov wrote:
>>
>> Andrey,
>>
>> Answered at the same [1] issue.
>> Anyway, we have to increm
Thank you!
пн, 9 июл. 2018 г. в 18:57, Andrey Gura :
> POM is updated in master branch.
>
> And no more commits to ignite-2.6 branch.
> On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov wrote:
> >
> > Andrey,
> >
> > Answered at the same [1] issue.
> > Anyway, we have to increment version now. We
POM is updated in master branch.
And no more commits to ignite-2.6 branch.
On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov wrote:
>
> Andrey,
>
> Answered at the same [1] issue.
> Anyway, we have to increment version now. We had to do this at the moment
> we created ignite-2.6 branch.
> In case y
Andrey,
Answered at the same [1] issue.
Anyway, we have to increment version now. We had to do this at the moment
we created ignite-2.6 branch.
In case you have some issues with increment, I can do this by myself.
[1] https://issues.apache.org/jira/browse/IGNITE-7823
пн, 9 июл. 2018 г. в 16:35,
I will side with Anton.
In any case right after branch creation, master version should be incremented.
Or version increase is planned right after 2.6 release?
> On 9 Jul 2018, at 16:32, Andrey Gura wrote:
>
> Anton,
>
> while version number is frequently used in Ignite code base I believe
>
Anton,
while version number is frequently used in Ignite code base I believe
that it's bad approach. See my comment to IGNITE-7823 [1] issue.
[1] https://issues.apache.org/jira/browse/IGNITE-7823
On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov wrote:
>
> Igniters,
>
> Ignite version still 2.6.0-
Igniters,
Ignite version still 2.6.0-SNAPSHOT at master,
It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a special
branch.
Some issues affecting backward compatibility can not be merged while
version not incremented.
ср, 4 июл. 2018 г. в 20:59, Andrey Gura :
> Igniters,
>
> I'v
Igniters,
I've moved IGNITE-8780 [1] issue to the next release. It can't be
merged to AI 2.6 because it has many other dependent commits.
[1] https://issues.apache.org/jira/browse/IGNITE-8780
On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov wrote:
>
> Andrey, thanks!
>
> I've cherry-picked the fixes to
Andrey, thanks!
I've cherry-picked the fixes to ignite-2.6 branch.
Best Regards,
Ivan Rakov
On 04.07.2018 16:26, Andrey Gura wrote:
Ivan,
I agree to include this fixes into AI 2.6 release. Please, feel free to merge.
On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov wrote:
Igniters,
Do we still ha
Ivan,
I agree to include this fixes into AI 2.6 release. Please, feel free to merge.
On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov wrote:
>
> Igniters,
>
> Do we still have chance to extend 2.6 scope?
>
> I propose to include two more tickets into 2.6:
> https://issues.apache.org/jira/browse/IGNITE-8
Igniters,
Do we still have chance to extend 2.6 scope?
I propose to include two more tickets into 2.6:
https://issues.apache.org/jira/browse/IGNITE-8769
https://issues.apache.org/jira/browse/IGNITE-8910
We had data races in our free lists implementation. Fixes prevent
possibility of AssertionE
Nikolay, thank you for such fast reaction. Tests are passing now.
ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov :
> Hello, Dmitriy.
>
> I fixed this issue, already.
> Please, check it.
>
> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> > Hi Denis,
> >
> > currently anyway we have TC issue
Hello, Dmitriy.
I fixed this issue, already.
Please, check it.
В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> Hi Denis,
>
> currently anyway we have TC issue came from spark version migrations.
>
> I also currently experiencing challenges with my local environment setup.
> So I guess we
Hi Denis,
currently anyway we have TC issue came from spark version migrations.
I also currently experiencing challenges with my local environment setup.
So I guess we have day or two to wait this fix.
Sincerely.
Dmitriy Pavlov
ср, 27 июн. 2018 г. в 16:05, Denis Magda :
> May I ask when? The c
May I ask when? The current status of the ticket is not clear.
--
Denis
On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey)
wrote:
> Yes, it will be in the release 2.6
>
> > 27 июня 2018 г., в 14:15, Dmitry Pavlov
> написал(а):
> >
> > Hi Igniters,
> >
> > I've returned https://issues.apache.org/j
Yes, it will be in the release 2.6
> 27 июня 2018 г., в 14:15, Dmitry Pavlov написал(а):
>
> Hi Igniters,
>
> I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
> scope because it was initially discussed to be in this reselase.
>
> Alexey Stelmak, could you please confirm f
Hi Igniters,
I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
scope because it was initially discussed to be in this reselase.
Alexey Stelmak, could you please confirm fix could be ready soon?
Also I've cherry-picked javadoc fix.
Sincerely,
Dmitriy Pavlov
вт, 26 июн. 201
+1 to Dmitriy's stance.
IGNITE-6055 doesn't look like something that needs to halt this release.
Plus, let me remind us that it's an emergency release that has to solve
severe problems at the persistence layer. What planned to be released
within 2 weeks got stuck for almost a month.
Dmitriy, as a
Hi Nikolay,
why this ticket should be included into emergency release?
I agree in case
1) Vladimir has time to review it now,
2) we have clear motivation why it is emergency change.
We are still going to do 2.7 release as normal Ignite release later.
Sincerely,
Dmitriy Pavlov
вт, 26 июн. 2018
Also, Igniters, be aware
https://issues.apache.org/jira/browse/IGNITE-8534 merged to master and cherry
picked to 2.6 branch.
В Вт, 26/06/2018 в 19:29 +0300, Nikolay Izhikov пишет:
> Hello, Igniters.
>
> We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
>
> IGNITE-6055 has to b
Hello, Igniters.
We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
IGNITE-6055 has to be included in 2.6, also.
Final review from Vladimir required to merge this ticket.
Do we have a chance to include this ticket to 2.6?
В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> Hi
Hi Igniters,
I've prepared wiki page
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 and
started to reassign existing issues to 2.7.
Sincerely,
Dmitriy Pavlov
сб, 23 июн. 2018 г. в 2:58, Denis Magda :
> Thanks folks!
>
> Dmitriy P., please proceed with the release finalizat
Thanks folks!
Dmitriy P., please proceed with the release finalization. Don't accept any
other commits to 2.6.
--
Denis
On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
>
> -Val
After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
-Val
On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Guys,
>
> I reviewed changes in IGNITE-8740, but I'm not sure the fix is correct. I
> left a more detailed comment in the ti
Guys,
I reviewed changes in IGNITE-8740, but I'm not sure the fix is correct. I
left a more detailed comment in the ticket. Hopefully, Mair will be able to
respond shortly and clarify.
-Val
On Fri, Jun 22, 2018 at 10:58 AM Denis Magda wrote:
> Dmitriy,
>
> No, that's an honor for us to see you
Dmitriy,
No, that's an honor for us to see you in this role ;) Both Andrey Gura,
Anton Vinogradov are our release-management veterans. Please feel free to
contact them directly.
Could you take over this ticket review and include it in the release:
https://issues.apache.org/jira/browse/IGNITE-8740
Hi Alexey,
Sure, it will be honor for me.
In the same time I relatevely new in this area, so I would highly
appreciate any assistance of experienced community members to make this
happen.
Sincerely,
пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk :
> Denis,
>
> Currently, I am not aware of anybo
Denis,
Currently, I am not aware of anybody who can immediately review and
sign-off the suggested patch. The original scope of tickets have been
resolved, so I suggest to move on with what we have now.
I will not be able to continue with the release process until Thursday next
week.
Dmitriy Pavl
Folks,
This release no longer reminds an emergency one :) Are we done with the
scope, who is a release manager?
>From my side, I'd like us to review and add the fix for broken Spring
integration which is a significant regression:
https://issues.apache.org/jira/browse/IGNITE-8740
--
Denis
On Mon
Hi Petr,
Who will be able to make the review for the suggested patch? I would like
to freeze the branch and start preparing the release.
пт, 15 июн. 2018 г. в 11:45, Petr Ivanov :
> Igniters,
>
>
> I’d like to stage for 2.6 release also this issue [1]. Corresponding PR
> [2] is ready for review
Igniters,
I’d like to stage for 2.6 release also this issue [1]. Corresponding PR [2] is
ready for review and merge.
This is not related to code additional configuration file for enabling support
of Windows 10 WSL Environment.
[1] https://issues.apache.org/jira/browse/IGNITE-8804
[2] https://
Hi,
Fix for IGNITE-8722 (https://issues.apache.org/jira/browse/IGNITE-8722) is
ready.
Diff
https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
TC looks good for me.
https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=bu
Igniters,
Recently we noticed the issue when we don't completely persist some data on
the disk:
https://issues.apache.org/jira/browse/IGNITE-8780 . In some cases it can
lead node to unrecoverable state.
I think this problem should be included to release.
ср, 13 июн. 2018 г. в 14:06, Alexey Kuzne
Hi!
Lets also include fix for https://issues.apache.org/jira/browse/IGNITE-8722
in this release.
This bug was introduced in IGNITE-7803 (Ignite 2.5) for data structures
that has references to self-type.
The fix is simple (remove one "else" key word in
IGNITE_BINARY_OBJECT_SERIALIZER) + add test.
Hello, guys.
I try my best to do review in a next few days.
В Вт, 12/06/2018 в 11:28 -0700, Denis Magda пишет:
> Agree with Ray. The ticket has been already reviewed and requires us to run
> tests for an isolated module - Spark.
>
> Dmitriy Pavlov, Nickolay Izhikov, could you step in as final r
Agree with Ray. The ticket has been already reviewed and requires us to run
tests for an isolated module - Spark.
Dmitriy Pavlov, Nickolay Izhikov, could you step in as final reviewers and
merge the changes?
--
Denis
On Tue, Jun 12, 2018 at 12:01 AM Ray wrote:
> Igniters,
>
> Can you squeeze t
Igniters,
Can you squeeze this ticket into 2.6 scope?
https://issues.apache.org/jira/browse/IGNITE-8534
As ignite-spark module is relatively independent module, and there're
already two users in the user list trying to use spark 2.3 with Ignite last
week only.
http://apache-ignite-users.70518.x6
I agree with Eduard.
вс, 10 июн. 2018 г. в 13:22, Eduard Shangareev :
> Guys,
>
> I have found an issue which could cause JVM Crash.
>
> https://issues.apache.org/jira/browse/IGNITE-8768
> (JVM Crash on node stop or deactivate while async evict in progress).
>
> Another one could hang node or thr
Guys,
I have found an issue which could cause JVM Crash.
https://issues.apache.org/jira/browse/IGNITE-8768
(JVM Crash on node stop or deactivate while async evict in progress).
Another one could hang node or throw AssertionError when we try to recycle
data pages:
https://issues.apache.org/jira/b
Ignite-2.6 branch is created, all mentioned fixes were pushed. I also
included the fix for [1] because the issue could lead to a hanging PME in
some circumstances.
Will trigger TC shortly.
[1] https://issues.apache.org/jira/browse/IGNITE-8530
вт, 5 июн. 2018 г. в 21:18, Ivan Rakov :
> I'd like t
I'd like to add that first issue [1] has a follow-up fix [2]. It should
be backported along with the first fix.
[1] - https://issues.apache.org/jira/browse/IGNITE-8476
[2] - https://issues.apache.org/jira/browse/IGNITE-8682
Best Regards,
Ivan Rakov
On 05.06.2018 20:57, Ivan Rakov wrote:
I agre
I agree in general. First issue is severe usability issue, while second
one may fail crash recovery and cause data loss. This makes AI 2.5 not
recommended for using.
Best Regards,
Ivan Rakov
On 05.06.2018 19:39, Alexey Goncharuk wrote:
Igniters,
Recently we've stumbled across the following t
Igniters,
Recently we've stumbled across the following two tickets [1], [2] which
seem to be very critical from the usability and stability points of view.
The [1] results in clients not being able to update persistence-enabled
clusters unless the client configuration is identical to the server
co
43 matches
Mail list logo
