; > actions to do. I haven't found such a decomposition on IEP-37 page. Do
> > we have one? What the implementation phases will be? What components
> > will be changed? What a new API would be and would it be? What
> > problems we are expecting e.g performance degradation o
Roman.
> Nikolay, Maxim, I understand that our arguments may not be as obvious
> for you as it obvious for SQL team. So, please arrange your questions in
> a more constructive way.
What is SQL team?
I only know Ignite community :)
Please, share you knowledge in IEP.
I want to join to the proce
ra/browse/IGNITE-3911
>
>
> On Fri, Sep 27, 2019 at 4:34 PM Nikolay Izhikov wrote:
>
> > Roman.
> >
> > > Nikolay, Maxim, I understand that our arguments may not be as obvious
> > > for you as it obvious for SQL team. So, please arrange your question
big deal, I think anybody understands it there.
> That's why our proposal to reuse others experience is obvious.
>
> If you have an alternative - you're welcome, I'll gratefully listen to you.
>
> The main question isn't "WHAT" but "HOW" - th
hosen by several other projects, there is experience,
> > there is a list of known issues (like using indexes) so, almost everything
> > is already done for us.
> >
> > Implementing a planner is a big deal, I think anybody understands it
> > there. That's why
the fact it’s the best option.
> It’s possible to develop it as an experimental extension at first (not a
> replacement) until we make sure that it works as expected. This way there are
> no risks for anybody who uses Ignite on production environment.
>
> Regards,
> Igor
&g
at the same time.
>
> > Let's start with the IEP clarification and replace the SQL engine with the
> > best one for Ignite good.
>
> Of course, but anyway it’s good to make familiar with a couple of examples it
> already describes and clarify some additional questi
Hello, Denis.
Thanks for the clarifications.
Sounds good for me.
All I try to say in this thread:
Guys, please, let's take a step back and write down requirements(what we want
to get with SQL engine).
Which features and use-cases are primary for us.
I'm sure you have done it, already during yo
Hello, Ivan.
I had a talk about internals of Spark integration in Ignite.
It answers on question why we should use Spark internals.
You can take a look at my meetup talk(in Russian) [1] or read an article if you
prefer text [2].
[1] https://www.youtube.com/watch?v=CzbAweNKEVY
[2] https://habr.
Yes, I can :)
В Пн, 30/09/2019 в 11:40 -0700, Denis Magda пишет:
> Nikolay,
>
> Would you be able to review the changes? I'm not sure there is a better
> candidate for now.
>
> -
> Denis
>
>
> On Mon, Sep 30, 2019 at 11:01 AM Nikolay Izhikov wrote:
>
e. And I am proud of it!
> >
> > As I understood, nobody is strictly against the proposed initiative.
> > And I am glad that we can move forward (with some steps back along the
> > way).
> >
> > пт, 27 сент. 2019 г. в 19:29, Nikolay Izhikov :
> > >
&
Hello, Igniters.
Since the last release `RunningQueryManager` [1] was added.
It used to track a running query.
In IEP-35 [2] SystemView API was added.
SystemView API supposed to be used to track all kinds of internal Ignite
objects.
I think this RunningQueryManager should be replaced [3] with t
GPG and exit?
>
>
> > On 21 Sep 2018, at 19:46, Nikolay Izhikov wrote:
> >
> > Hello, Petr.
> >
> > Seems that rpm build script doesn't work on a lates Ubuntu Linux.
> > I've created a ticket [1] and found a fix for it [2]
> >
> >
Hello, Igniters.
I've created branch for an Apache Ignite 2.7 release [1]
Please, cherry-pick tickets that should be in 2.7 to that branch.
[1]
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=shortlog;h=refs/heads/ignite-2.7
signature.asc
Description: This is a digitally signed message p
Hello, Igniters.
Cos, I have a question regarding Apache Ignite release.
I have committer priveledges in Apache Ignite.
I don't have PMC role.
Since I don't have PMC role, I can't add my GPG key to KEYS [1] file.
Is it OK if someone with PMC role adds my GPG key to KEYS file?
[1] https://dist
Hello, Igniters.
I propose to implement following behaviour:
1. Execute "Run all" suite for specific PR when the author of PR makes a comment
"@mtcga.bot Run Tests!" in GitHub comments.
2. Send a comment with "Run All" results both: to a Jira ticket and GitHub
comment.
3. Label PR based on "Ru
PA state, the bot will check comments list and find possible
> new mentions (made after the previous build complete date). If it finds
> such comments it goes to step 1 (trying to find only new builds available).
>
> What do you think?
>
> Sincerely,
> Dmitriy Pavlov
>
&g
PRs and the bot can
> expect there is only one open PR per ticket.
>
> Sincerely,
> Dmitriy Pavlov
>
> пн, 24 сент. 2018 г. в 23:41, Nikolay Izhikov :
>
> > Hello, Dmitriy.
> >
> > > But it could be a lot of work to handle mentions (probably from the
>
Hello, Vova.
Thank you for clear release status.
I'm +1 for your proposal.
чт, 27 сент. 2018 г., 18:25 Alexey Kuznetsov :
> Vova,
>
> Huge +1 to do a stabilization.
>
>
> --
> Alexey Kuznetsov
>
Hello, Igniters.
I found that this feature can't be disabled from config.
The only way to disable it is from JMX bean.
I think it very dangerous: If we have some corner case or a bug in this Watch
Dog it can make Ignite unusable.
I propose to implement possibility to disable this feature both -
system
> property.
>
> пт, 28 сент. 2018 г. в 11:30, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > I found that this feature can't be disabled from config.
> > The only way to disable it is from JMX bean.
> >
> > I think it very dangerous: If we
gt; > > > > should
> > > > > > > > > be
> > > > > > > > > > moved to future release, instead of shifting release. The
> > >
> > > sole
> > > > > > reason
> > > > > > > > to
> >
nis Magda :
> > > >
> > > > > Nikolay,
> > > > >
> > > > > Thanks for stepping in and giving more context. In general, I'm
> >
> > fully for
> > > > > your proposal below:
> > > > >
> >
Hello, Saikat.
I have no objections to include this integration to 2.7 release.
But, we should ask for a final review from Alex Goncharyuk.
Alex, can you comment on this?
Is this patch ready to be merged?
Do you see any risks to include it to 2.7 release?
В Вс, 30/09/2018 в 19:57 -0500, Saikat
rincipal place
> > > where
> > > discussion runs. I sincerely hope all similar decisions will be building
> > > on
> > > the dev list.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > вс, 30 сент. 2018 г.
gt; example being added to the tests folder. I think it should be either added
> to the examples (not sure about the dependency though), or should not be
> added at all. Also, I see that you added a new suite, has it been added to
> a TC configuration?
>
>
>
> пн, 1
Hello, Andrey.
Yes, I know it.
I've looked at the PR befor mailing :)
Do you think we can include this improvement to the 2.7 release?
Do you have time to assist Saikat with TC setup and other tasks?
В Пн, 01/10/2018 в 19:54 +0300, Andrey Mashenkov пишет:
> Dmitry, Nikolay,
>
> Ignite-3303 is
Dmitriy, thank you.
I also making some notes about release.
Feedback are welcome.
https://cwiki.apache.org/confluence/display/IGNITE/Release+manager+Notes
В Вт, 02/10/2018 в 14:42 +0300, Dmitriy Pavlov пишет:
> Hi Igniters,
>
> We had several hot discussions related to release, and one from rea
ср, 12 сент. 2018 г. в 20:34, Denis Magda :
>
> > Hello Nikolay,
> >
> > Excellent progress, look forward to seeing the TDE released in 2.7!
> >
> > --
> > Denis
> >
> > On Wed, Sep 12, 2018 at 2:47 AM Nikolay Izhikov
> > wrote:
> &
.
> > > > > > > >
> > > > > > > > On Mon, Oct 1, 2018 at 9:50 PM Dmitriy Setrakyan <
> > > > >
> > > > > dsetrak...@apache.org>
> > > > > > > > wrote:
> &
e-2.6
> > > branch and it has passed. So, it's not an legacy bug, we've brought it
> >
> > with
> > > some change of 2.7 scope. Is it still ok to ignore the bug?
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-9776
> > &
during WAL
> flush), another - by Andrey Kuznetsov (NPE during a concurrent WAL flush).
>
> --AG
>
> ср, 3 окт. 2018 г. в 13:38, Nikolay Izhikov :
> > Hello, Igniters.
> >
> > Release scope is frozen.
> > Please, if you include some new issue
f view this fix is important for release and I want to
> include it to 2.7.
>
> Any objections?
>
> пн, 20 авг. 2018 г. в 21:22, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > I'm release manager of Apache Ignite 2.7.
> >
> > It's t
Helo, Dmitriy.
I looked at patch.
Seems it local for a ML module.
Is it's true I'm +1 to include it to 2.7.
В Чт, 04/10/2018 в 08:33 -0500, dmitrievanthony пишет:
> Hi, Yury, Nikolay.
>
> This issue reproduces in "TensorFlow on Apache Ignite" use cases. When user
> prepares training script (li
ey Kuznetsov :
> >
> > > Ignite committers,
> > >
> > > I have prepared a PR for 2.7 blocker [1]. Could anybody merge it to 2.7
> > > and master?
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-9737
> > >
Hello, Igniters.
I merged to master TDE.Phase 1 that has been actively discussed on dev-list.
I want to thank all guys that helped me with the implementation:
1. Dmitriy Ryabov - initial design.
2. Anton Vinogradov - an initial review. wisdom sharing.
3. Vladimir Ozerov - final review. pricel
%20Closed)%20and%20(component%20is%20null%20or%20component%20not%20in%20(documentation)))%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20
В Ср, 03/10/2018 в 14:02 +0300, Nikolay Izhikov пишет:
> Alexey.
>
> Sorry, I lost link to IGNITE-9760 in this thread :)
>
>
Hello, Igniters.
I list all contributors that assigned to the 2.7 tickets.
If you can help them to finish that tickets - please, do.
Assigners, if you need any help - please, respond to this thread.
NOTE: We have 6 Unassigned tickets for 2.7. Let's start work on it!
Peter Ivanov - IGNITE-9
> >
> > Can you help with the unassigned MVCC tickets?
> >
> > D.
> >
> > On Wed, Oct 10, 2018 at 3:32 AM Nikolay Izhikov
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > I list all contributors that assigned to the
ase is rare,
> but it is quite an unpleasant UX. Should we include it to 2.7 as well?
>
> чт, 11 окт. 2018 г. в 11:22, Nikolay Izhikov :
>
> > Hello, Igniters.
> >
> > We made a good progress yesterday.
> >
> > Here is the list of remaining tickets(17)
- IGNITE-8670
Roman Kondakov - IGNITE-7953
Igor Sapego- IGNITE-9620
Alexey Stelmak - IGNITE-9776
Unassigned:
IGNITE-9663 - MVCC: Data node failure can cause TX hanging.
В Чт, 11/10/2018 в 13:50 +0300, Nikolay Izhikov пишет:
> Alexey, we all agreed to merge in 2.7 blockers only.
Hello, Igniters.
There is no progress till Friday.
We have 14 tickets mapped to 2.7.
В Пт, 12/10/2018 в 08:29 +0300, Nikolay Izhikov пишет:
> Hello, Igniters.
>
> We made some progress yesterday.
>
> Please, note, we have 1 new ticket mapped to 2.7 "IGNITE-9852: Create
gt;
> >
> > On Mon, Oct 15, 2018 at 11:33 AM Vladimir Ozerov
> > wrote:
> >
> > > Nikolay,
> > >
> > > AI 2.7 will include Python thin client. TC suite is crucial part of this
> > > feature, so we should keep the ticket i
Вт, 16/10/2018 в 16:20 +0300, Andrey Gura пишет:
> Hi,
>
> I've found that IGNITE-9723 was resolved but didn't cherry picked to
> ignite-2.7 branch. So I'll do it.
> On Tue, Oct 16, 2018 at 2:30 PM Nikolay Izhikov wrote:
> >
> > Hello, Igniters.
> >
хин Иван wrote:
>
> > Hi NIkolay,
> >
> > Thank you for keeping everybody focused! Regarding to my ticket
> > IGNITE-5935.
> > It is in final stage now. Tests look good. I believe that it will be merged
> > in couple of days (at most).
> >
> > ср,
Pavel.
Ok, I agree to include this ticket into 2.7
Let's do it.
В Ср, 17/10/2018 в 13:20 +0300, Pavel Tupitsyn пишет:
> Nikolay,
>
> It completely breaks a major feature under certain conditions. I would
> consider it a blocker.
>
> On Wed, Oct 17, 2018 at 1:00 PM
at 5:41 PM Pavel Tupitsyn
> > > wrote:
> > > >
> > > > Thank you. Fix has been merged to master and cherry-picked to
> >
> > ignite-2.7.
> > > >
> > > > On Wed, Oct 17, 2018 at 1:26 PM Nikolay Izhikov
> > >
> >
; > quite
> > > > important.
> > > >
> > > > ср, 17 окт. 2018 г. в 17:49, Andrey Gura :
> > > >
> > > > > JFYI
> > > > >
> > > > > IGNITE-9737 and IGNITE-9710 are merged to release branch.
> &
Hello, Igniters.
Currently, Spark Data Frame integration implemented via client node connection.
Whenever we need to retrieve some data into Spark worker(or master) from Ignite
we start a client node.
It has several major disadvantages:
1. We should copy whole Ignite distribution on to
client can connect to any node directly while presently all
> > the communication goes through a proxy (a node the client is connected to).
> > All of that is bad for performance.
> >
> >
> > Vladimir, how hard would it be to support the partition-awareness for Java
ишет:
> Nikolay,
>
> Where do you track those 8 blockers? Can't find them on this wiki page:
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7
>
> --
> Denis
>
> On Sat, Oct 20, 2018 at 11:31 AM Nikolay Izhikov
> wrote:
>
> > Hello, De
re other use cases.
>
> Regards,
> Stephen
>
> > On 21 Oct 2018, at 09:08, Nikolay Izhikov wrote:
> >
> > Valentin.
> >
> > Seems, You made several suggestions, which is not always true, from my
> > point of view:
> >
> > 1. "We
Hello, Igniters.
As you may know, we successfully implement TDE. Phase-1 feature. [1]
This improvement allows users to use an encrypted cache.
To make TDE production ready I propose to extend it with two things:
* Master key rotation.
* Cache key rotation.
Such features required
- IGNITE-9953 - Dropping hadoop accelerator downloads
В Вс, 21/10/2018 в 11:23 +0300, Nikolay Izhikov пишет:
> Hell, Denis.
>
> I just filter all 2.7 tickets without documentation.
>
>
> https://issues.apache.org/jira/browse/IGNITE-9932?jql=(project%20%3D%20%27Ignite%27%
we can go ahead with vote.
> >
> > Thoughts?
> >
> > On Tue, Oct 23, 2018 at 10:41 AM Nikolay Izhikov
> > wrote:
> >
> > > Hello, Igniters.
> > >
> > > We have 7 tickets mapped to 2.7 to
Hello, Maxim.
+1 from me.
I vote to enable static inspections for the Ignite codebase.
Thank you for that contributions!
В Вт, 23/10/2018 в 19:09 +0300, Maxim Muzafarov пишет:
> Igniters,
>
> I've fixed some issues according to the inspections.xml configuration:
> - `Missorted modifiers`;
> -
ling, we have to re-encrypt keys and to set new
> master key id.
>
> 3) We should provide recovery mode for nodes unexpectedly leaved cluster
> during "Master Key rotation" process.
> We have to have a special "node start" command allows to change node's
&g
+0300, Nikolay Izhikov пишет:
> Hello, Dmitriy.
>
> I'm OK with including this patch to 2.7.
>
> Can you ensure it completely fix the issue?
> I left comment in ticket.
>
> https://issues.apache.org/jira/browse/IGNITE-9854?f
try to fix them without getting rid of thick client.
>
> -Val
>
> On Sun, Oct 21, 2018 at 1:08 AM Nikolay Izhikov wrote:
>
> > Valentin.
> >
> > Seems, You made several suggestions, which is not always true, from my
> > point of view:
> >
>
Hello.
Deisgn updated [1]
Please, share your feedback
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381
В Вт, 23/10/2018 в 21:49 +0300, Nikolay Izhikov пишет:
> Hello, Anton.
>
> Thank you for your very usefull feedback!
>
> I accept your propos
a8=pull%2F5059%2Fhead&tab=buildTypeStatusDiv
> [3]
> https://issues.apache.org/jira/browse/IGNITE-9983?focusedCommentId=16662323&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16662323
>
> On Tue, 23 Oct 2018 at 19:16 Nikolay Izhikov wr
igned Parse error leads to leave the
transaction
В Ср, 24/10/2018 в 12:30 +0300, Nikolay Izhikov пишет:
> Hello, Igniters.
>
> We have 3 ticket mapped to 2.7 today:
>
> Igor Seliverstov - IGNITE-9892 - MVCC: Exchange hangs on mvcc coordinator fail
> Roman Kondakov
y ticket.
>
> On Fri, Oct 26, 2018 at 9:57 AM Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
> > We have *9* tickets mapped to 2.7 today
> >
> > Vladimir, do you think 1 week delay will be enough to resolve all this
> > tickets?
> >
&
, Nikolay Izhikov пишет:
> Hello.
>
> Deisgn updated [1]
>
> Please, share your feedback
>
> [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381
>
>
> В Вт, 23/10/2018 в 21:49 +0300, Nikolay Izhikov пишет:
> > Hello, Anton.
>
Hello, Pavel.
What jdk version do you use?
В Пн, 29/10/2018 в 15:30 +0300, Pavel Kovalenko пишет:
> Hello Igniters,
>
> I have a problem with running TDE tests on my local machine.
>
> When I start e.g. EncryptedCacheDestroyTest I get following exception:
>
> > javax.cache.CacheException: clas
>
> JDK 1.8.0_151-b12
>
> пн, 29 окт. 2018 г. в 15:31, Nikolay Izhikov :
>
> > Hello, Pavel.
> >
> > What jdk version do you use?
> >
> > В Пн, 29/10/2018 в 15:30 +0300, Pavel Kovalenko пишет:
> > > Hello Igniters,
> > >
&g
Hello, Guys.
Good news! We have 2 final tickets for 2.7.
So release date is very near!
Let's collect new features and improvements of Ignite 2.7 and includes it to
release notes and other documents.
Can you answer and describe your contributions?
signature.asc
Description: This is a digitally
Databind updated to 2.9.6
> * Jackson 1 usages replaced with Jackson 2
> * JCraft updated to 0.1.54
> * H2 version updated to 1.4.197
> * Log4j 2.x updated to 2.11.0
> * Netty updated to 4.1.27.Final
> * RocketMQ updated to 4.3.0
> * Scala 2.10.x was updated to 2.10.7
>
t; to 'ignite-2.7')
> > > -
> > >
> > >
> https://github.com/apache/ignite/commit/6e0ff06f8e309657a16c94da605348d9c3b804ad
> > >
> > > The most important part is the change introduced into
> GridDhtAtomicCache,
> > > the fix pre
ct 31, 2018 at 5:04 PM Vyacheslav Daradur <
> daradu...@gmail.com>
> > > wrote:
> > > >
> > > > Hi, Igniters! Good news!
> > > >
> > > > Service Grid Redesign Phase 1 - is in Patch Available now.
> > > >
> > > >
Gura Critical worker liveness check configuration
is non-trivial and inconsistent
IGNITE-9996 Nikolay Izhikov Investigate possible performance drop in FSYNC
mode for ignite-2.7 compared to ignite-2.6
В Чт, 08/11/2018 в 14:25 +0300, Nikolay Izhikov пишет:
> I'm OK with this.
&g
gt; >
> > > > > > ср, 7 нояб. 2018 г., 14:39 Vyacheslav Daradur > >
> > > :
> > > > > >
> > > > > > > I prepared a description of the implemented solution and attached
> > >
> > > it
> > > >
Hello,Peter.
Welcome to Ignite community!
First of all, please, subscribe to dev-list.
Processes of code and doc contribution are described on wiki
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
> which repo should I clone? It looks like there are two.
https://github.com/a
Congratulations, Alexey!
сб, 17 нояб. 2018 г., 12:07 Dmitriy Pavlov dpav...@apache.org:
> The Apache Ignite Project Management Committee (PMC) has invited Alexey
> Plehanov to become a new committer and are happy to announce that he has
> accepted.
>
>
>
> Being a committer enables you to more ea
you take a look at
> > the issue?
> >
> > I think this regression essentially makes our logs unreadable in some cases
> > and I would like to get it fixed in ignite-2.7 or revert both commits from
> > the release.
> >
> > [1] https://issues.apache.org/
Yes, I think so.
вс, 18 нояб. 2018 г., 20:34 Denis Magda dma...@apache.org:
> Sounds good to me. Are we starting the vote then?
>
> Denis
>
>
>
> On Sun, Nov 18, 2018 at 8:25 AM Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
> > This iss
IGNITE-10325 created.
ср, 7 нояб. 2018 г., 11:42 Ray ray...@cisco.com:
> From my past experience with Spark Data Frame API, the thick client
> approach
> leads to many usability problems.
>
> Ex.
>
> http://apache-ignite-users.70518.x6.nabble.com/Local-node-SEGMENTED-error-causing-node-goes-down-
gridgain.com:
>
> > +1 for revert.
> >
> > On Sun, Nov 18, 2018 at 11:31 PM Dmitriy Pavlov
> > wrote:
> >
> > > I personally don't mind.
> > >
> > > But I would like Dmitry Ryabov and Alexey Goncharuck share their
> >
> > o
Hello, Vyacheslav.
Yes, we have.
Maxim Muzafarov, can you fix it, please?
вт, 20 нояб. 2018 г., 13:10 Vyacheslav Daradur daradu...@gmail.com:
> Guys, why we have 2 different inspection files in the repo?
> idea\ignite_inspections.xml
> idea\ignite_inspections_teamcity.xml
>
> AFAIK TeamCity is
for continuing work we need to overcome this first phase.
> > >
> > > On Tue, Nov 13, 2018 at 1:09 PM Vyacheslav Daradur <
> daradu...@gmail.com>
> > > wrote:
> > > >
> > > > Denis, Yakov, feel free to contact me directly i
> > > end-users.
> > > >
> > > > But for continuing work we need to overcome this first phase.
> > > >
> > > > On Tue, Nov 13, 2018 at 1:09 PM Vyacheslav Daradur <
> > daradu...@gmail.com>
> > > > wro
Ryabov пишет:
> Yes, revert both.
>
> вт, 20 нояб. 2018 г., 11:52 Vladimir Ozerov voze...@gridgain.com:
>
> > +1 for reverting both.
> >
> > On Tue, Nov 20, 2018 at 9:43 AM Nikolay Izhikov
> > wrote:
> >
> > > Hello, Dmitrii
Hello, Denis.
Nothing blocks now.
I preparing vote artifacts right now.
There are some issues with TC tasks.
I think I resolve them in a couple of hours.
чт, 29 нояб. 2018 г., 19:30 Denis Magda dma...@apache.org:
> I think that it's not a blocker since MVCC is in the beta state and some of
> the
Igniters,
We've uploaded a 2.7.0 release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.7.0-rc1/
Git tag name is 2.7.0-rc1
This release includes the following changes:
Apache Ignite In-Memory Database and Caching Platform 2.7
--
Ivan. Please, provide a link for a ticket with NPE stack trace attached.
I've looked at IGNITE-10376 and can't see any attachments.
пт, 30 нояб. 2018 г., 10:14 Ivan Fedotov ivanan...@gmail.com:
> Igor,
> NPE is available in a full log, now I also attached it in the ticket.
>
> IGNITE-7953
> <
>
t; > (GridCacheProcessor.java:1372)
> >
> > That's why at the time GridCacheMapEntry#touch
> (GridCacheMapEntry.java:5063)
> > invoked there is no eviction manager.
> >
> > This is a result of "normal" flow because message processing doesn't
ompactedDao.java:140)
> > at
> >
> >
> org.apache.ignite.ci.teamcity.ignited.runhist.RunHistSync.saveInvocationList(RunHistSync.java:239)
> > at
> >
> >
> org.apache.ignite.ci.teamcity.ignited.runhist.RunHistSync.lambda$saveInvocationsMap$4(RunHistSync.java:
gt;
> > > >
> >
> > org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:833)
> > > > at
> > > >
> > > >
> >
> > org.apache.ignite.internal.processors.
Igniters,
We've uploaded a 2.7.0 release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.7.0-rc2/
Git tag name is 2.7.0-rc2
This release includes the following changes:
Apache Ignite In-Memory Database and Caching Platform 2.7
--
syn :
>
> > +1
> >
> > Downloaded sources, build Java and .NET parts, ran examples.
> > There is a minor issue with .NET Core examples, compiler warning is
> > displayed (certainly not a blocker) [1]
> >
> > [1] https://issues.apache.o
> I couldn't quickly find the root cause of this problem because I'm not
> >> an expert in the binary metadata flow. I think community should decide
> >> whether this is a release blocker or not.
> >>
> >>
> >> --
> >> Kind Regards
>
Igniters,
Apache Ignite 2.7.0 release (RC2) has been accepted.
3 "+1" binding votes received:
- Pavel Tupitsyn
- Dmitriy Pavlov
- Nikolay Izhikov
Vote thread:
http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html
signature.asc
Descrip
Sorry, Alex.
I miss your +1.
Thank you, very much for checking RC artifacts.
вт, 4 дек. 2018 г., 7:10 Alexey Kuznetsov akuznet...@apache.org:
> Nikolay,
>
> Actually 4 "+1" binding.
>
> You did not count my "+1".
>
> :)
>
>
> On Tu
Hello, Igniters.
I'm agree with Anton Vinogradov.
I think we should avoid commits like [1]
Copy paste coding style is well known anti pattern.
Don't we have another option to do same fix with better styling?
Accepting such patches leads to the further tickets to cleanup mess that
patches brings
Tests in these classes check fail cases when we expect critical
> failure
> > like node stop or exception thrown
> >
> > So, this copy-n-paste-style change is caused by the imperfect logic of
> > existing tests, that should be reworked in more robust way, e.g. usi
release?
> Once the binaries are available on the website we need to release the docs.
>
>
> I'm ready to prepare a blog post for blogs.apache.org.
>
> --
> Denis
>
> On Mon, Dec 3, 2018 at 11:14 PM Nikolay Izhikov
> wrote:
>
> > Sorry, Alex.
> >
&g
Result:
> some of us knew it only now.
>
> Do you need to make Ignite quite toxic place to have an absolutely perfect
> code with just a few of arguing-resistant contributors? I believe not, and
> you don't need to be reminded 'community first principle'.
>
>
> ср,
don't understand what is unmuted by discussed commit.
ср, 5 дек. 2018 г. в 20:40, Nikolay Izhikov :
> > Thanks, as an improvement to the code, this may be better.
>
> I can prepare a full patch for NoOp handler.
> What do you think?
>
> Anton Vinogradov, do you agree with
on "Revert the patch and then do it
> better" but I does not see anything (anyone) what can guarantee it.
> So, I personally prefer an option 1 against 2 because I believe that
> it is good if the system "can make a progress".
>
> [1] https://github.com/apache/ignite/pul
release introduce several major features and fixes some critical issues
https://ignite.apache.org/releases/2.7.0/release_notes.html
Download the latest Ignite version from here:
https://ignite.apache.org/download.cgi
Please let us know [2] if you encounter any problems.
Regards,
Nikolay Izhikov on
601 - 700 of 1145 matches
Mail list logo
