v 3, 2015 at 5:46 AM, Vladisav Jelisavcic <vladis...@gmail.com>
> wrote:
>
> > Dear Dmitriy,
> >
> > it sounds excellent, I would like to do it,
> > but I would like to implement ReentrantLock first:
> > https://issues.apache.org/jira/browse/IGNITE-642
>
Dear Dmitriy,
it sounds excellent, I would like to do it,
but I would like to implement ReentrantLock first:
https://issues.apache.org/jira/browse/IGNITE-642
What do you think?
On Tue, Nov 3, 2015 at 3:37 AM, Dmitriy Setrakyan
wrote:
> Igniters,
>
> MultiMap should be
gt;
> > Please see below..
> >
> >
> > On 11/11/2015 12:33 PM, Vladisav Jelisavcic wrote:
> >
> >> Yakov,
> >>
> >> sorry for running a bit late.
> >>
> >> Vladislav, do you have any updates for
> >>> https://issues.apache.o
Hi everyone,
my name is VJ, i would like to implement IgniteSemaphore datastructure (
IGNITE-638).
My Jira ID is vladisav, can someone please assign it to me?
Thanks,
VJ
Not working for me also,
but only 1.6.0 (latest) and 1.5.0.final, the rest is working fine.
On Mon, Jun 20, 2016 at 8:02 AM, Sergey Kozlov wrote:
> Hi
>
> It's a known issue: apache site puts links to a nearest site for user (I
> suppose it based on IP address) and does it
I created a ticket from this discussion:
https://issues.apache.org/jira/browse/IGNITE-2399
Can someone please review it (and edit if needed)?
Best regrads,
VJ
On Mon, Jan 18, 2016 at 12:28 PM, Yakov Zhdanov wrote:
> I like the idea. Couple of comments though.
>
> I would
Sure, no problem.
I created a ticket:
https://issues.apache.org/jira/browse/IGNITE-2735
and a PR to resolve this problem.
I think this should also fix: IGNITE-1977
but the non-failover test scenario is not good anymore;
Best regards,
Vladisav
On Mon, Feb 29, 2016 at 2:32 PM, Vladimir
gt; >
> > --Yakov
> >
> > 2016-02-29 16:00 GMT+06:00 Yakov Zhdanov <yzhda...@apache.org>:
> >
> >> Vlad, that's great! I will take a look this week. Reassigning ticket to
> >> myself.
> >>
> >> --Yakov
> >>
> >>
Yakov,
sorry for the long delay, I added another commit to the PR,
can you please do the review again?
Thanks!
Vladisav
On Sun, Mar 27, 2016 at 11:30 AM, Vladisav Jelisavcic <vladis...@gmail.com>
wrote:
> Yakov, I've seen your comments, can you please check the jira again?
>
>
&
Yakov, I've seen your comments, can you please check the jira again?
On Wed, Mar 23, 2016 at 4:46 PM, Yakov Zhdanov <yzhda...@apache.org> wrote:
> Vlad, can you please check my comments again?
>
> --Yakov
>
> 2016-03-18 17:57 GMT+03:00 Vladisav Jelisavcic <vladis...@gm
design first. Once the community agrees on the
> design, you can proceed with the implementation.
>
> Does this sound good?
>
> D.
>
> On Thu, Mar 3, 2016 at 11:22 AM, Vladisav Jelisavcic <vladis...@gmail.com>
> wrote:
>
> > Igniters,
> >
> > is IGNIT
Igniters,
is IGNITE-1251 still a thing?
If so, I would really like to start working on this one.
Best regards,
Vladisav
Yakov,
did you had time to do another review round of ignite-642?
Thanks!
On Fri, Apr 15, 2016 at 3:53 PM, Vladisav Jelisavcic <vladis...@gmail.com>
wrote:
> Yakov,
>
> I've finished the initialization tests for ignite-642 (and moved
> serialization test from GridCac
Hi,
it looks really interesting to me,
I'll be glad to pick this one.
Best regards,
Vladisav
On Fri, May 13, 2016 at 7:41 AM, Thomas Weise wrote:
> Dear Ignite community,
>
> Apache Apex is a data in-motion processing platform. It was developed since
> 2012 and recently
Yakov,
I've finished the initialization tests for ignite-642 (and moved
serialization test from GridCacheLockAbstractTest to
IgniteLockAbstractSelfTest).
Please check the commit and let me know if you spot anything else.
Thanks!
On Fri, Apr 15, 2016 at 10:11 AM, Vladisav Jelisavcic <vla
Yakov,
I reviewed the changes in ignite-642 and it looks good to me, but I have
one question.
Can you please look at my comment in ignite-642 ticket?
Thanks!
Vladisav
On Thu, Apr 14, 2016 at 7:51 PM, Vladisav Jelisavcic <vladis...@gmail.com>
wrote:
> Sure, I'll look into it la
Sure, I'll look into it later today, or tomorrow at the latest
On Thu, Apr 14, 2016 at 5:53 PM, Yakov Zhdanov wrote:
> Vlad, please see my changes in ignite-642 and comment in the ticket.
>
> Alex, can you please take a look at my latest commit as well and provide
>
Sure, I'll do the review.
It is lazy initialized, same as latch and other datastructures.
Regards,
Vladisav
On Thu, Jul 21, 2016 at 10:24 AM, Yakov Zhdanov wrote:
> Vladislav, can you please review and merge to master the fix and test case
> suggested by Krome?
>
> Vlad,
Hi everyone,
cross-posting from JIRA:
I recently came across this post:
http://codereview.stackexchange.com/a/31231
Do you think ReadWriteUpdateLock is something we can put to good use here
in Ignite?
This kind of lock should be more efficient for read-before-write patterns.
Best regards,
Hi Sergey,
can you please provide more information?
Have you changed the example (if so, can you provide the changes you made?)
Is the example executed normally (without node failures)?
In the example, semaphore is created in non-failover safe mode,
which means it is not safe to use it once it
nging of new nodes doing so.
>
> Can you reproduce this? If so I will submit a ticket and share with you.
>
> Thank you,
> Sergey.
>
>
> On Wed, Nov 9, 2016 at 10:55 AM, Vladisav Jelisavcic <vladis...@gmail.com>
> wrote:
>
> > Hi Sergey,
> >
> > ca
/IGNITE-4209> to
> track this issue, feel free to edit it if it isn't descriptive enough.
>
> Thank you,
> Sergey.
>
> On Thu, Nov 10, 2016 at 9:44 AM, Vladisav Jelisavcic <vladis...@gmail.com>
> wrote:
>
> > Hi Sergey,
> >
> > you are right - I can r
+1 (non-binding)
On Wed, Nov 16, 2016 at 6:15 PM, Denis Magda wrote:
> +1
>
> —
> Denis
>
> > On Nov 16, 2016, at 2:08 AM, Pavel Tupitsyn
> wrote:
> >
> > Following the discussion on Upsource [1],
> > I would like to call a vote on accepting it as our
Hi,
when failoverSafe == true, semaphore should silently redistribute the
permits acquired on the failing node.
If failoverSafe is set to false, exception is thrown to every node
attempting to acquire.
It seems to me that when the first instance left topology,
no backups were available (this is
+1 (non-binding)
On Tue, Dec 6, 2016 at 9:17 AM, Anton Vinogradov
wrote:
> +1 (binding)
>
> On Tue, Dec 6, 2016 at 3:43 AM, Roman Shtykh
> wrote:
>
> > +1 (binding)
> >
> > -Roman
> >
> >
> >
> >
> > On Tuesday, December 6, 2016 8:14 AM,
Hi everyone,
I agree with Val, he's got a point; recreating the lock doesn't seem
possible
(at least not the with the transactional cache lock/semaphore we have).
Is this re-create behavior really needed?
Best regards,
Vladisav
On Thu, Mar 16, 2017 at 8:34 PM, Valentin Kulichenko <
related tickets, in
> particular [1].
> Could you please take a look?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-4173
>
> Thanks!
>
> 06.04.2017 16:27, Vladisav Jelisavcic пишет:
>
> Hey Dmitry,
>
> sorry for the late reply, I'll try to bake a pr
gt;> nobody else is currently executing the guarded logic before the
>> re-creation. This is exactly the same semantics as with
>> BrokenBarrierException for j.u.c.CyclicBarrier.
>>
>> 2017-03-17 2:39 GMT+03:00 Vladisav Jelisavcic <vladis...@gmail.com>:
>>
>>
wLog.html?buildId=544238;
> tab=buildResultsDiv=IgniteTests_IgniteBinaryObjectsDataStrucut
> ures
>
> Thanks!
>
> -Dmitry.
>
> 13.04.2017 16:15, Dmitry Karachentsev пишет:
>
> Thanks a lot!
>
> 12.04.2017 16:35, Vladisav Jelisavcic пишет:
>
> Hi Dmit
iteTests_IgniteDataStrucutures#
> testNameId-979977708202725050
> [2] https://issues.apache.org/jira/browse/IGNITE-1977
>
> Thanks!
>
> 14.04.2017 15:27, Dmitry Karachentsev пишет:
>
> Vladislav,
>
> Yep, you're right. I'll fix it.
>
> Thanks!
>
> 14.04.2017 15:18, Vla
Hi,
excellent job so far!
What about classification algorithms?
If everyone agrees, let's start by adding logistic regression to the list:
https://issues.apache.org/jira/browse/IGNITE-5059
Best regards,
Vladisav
On Fri, Apr 21, 2017 at 10:00 PM, Nikita Ivanov wrote:
>
Hi Artem,
I agree, it is not supported in many frameworks;
on the other hand, Spark MLlib supports it [1].
I think it is good thing to check with users if there is a need for this,
since we are already on the topic of model importing/exporting.
Best regards,
Vladisav
[1]
Hi Yury,
since we're already on topic for importing/exporting models,
just as a thought: maybe we should add support for PMML [1] [2]?
Best regards,
Vladisav
[1] http://dmg.org/pmml/v4-1/GeneralStructure.html
[2] https://github.com/jpmml/jpmml-model
On Mon, Oct 16, 2017 at 2:20 PM, Yury Babak
Hi Tim,
I reviewed your contribution and left you some comments on the pr.
Thanks!
Vladisav
On Wed, Jan 17, 2018 at 10:14 PM, Vladisav Jelisavcic <vladis...@gmail.com>
wrote:
> Hi Tim,
>
> thank you for the contribution!
> I'll do the review soon and let you know.
>
>
Hi Tim,
thank you for delving deeper into the problem,
I left you a comment/question on the JIRA.
Best regards,
Vladisav
On Tue, Jan 23, 2018 at 3:00 PM, Vladisav Jelisavcic <vladis...@gmail.com>
wrote:
> Hi Tim,
>
> thanks for the update! I left you a comment on Jira.
&
Hi Alexey,
I already reviewed it, but wanted to see the resolution of IGNITE-6454
first before I merge.
Thanks,
Vladisav
On Fri, Feb 16, 2018 at 12:39 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Hi Vladislav,
>
> Can you please finalize the review? I would like to include the
>
>
>
> On Sat, Jan 20, 2018 at 8:10 AM, Vladisav Jelisavcic <vladis...@gmail.com>
> wrote:
>
>> Hi Tim,
>>
>> I reviewed your contribution and left you some comments on the pr.
>> Thanks!
>>
>> Vladisav
>>
>> On Wed,
Vladisav Jelisavcic created IGNITE-2399:
---
Summary: Add asynchronous acquire to IgniteSemaphore
Key: IGNITE-2399
URL: https://issues.apache.org/jira/browse/IGNITE-2399
Project: Ignite
Vladisav Jelisavcic created IGNITE-2735:
---
Summary: Interrupt all acquires on local node after ignite.close
Key: IGNITE-2735
URL: https://issues.apache.org/jira/browse/IGNITE-2735
Project: Ignite
Vladisav Jelisavcic created IGNITE-2768:
---
Summary: Public API for data structures should be guarded from
being invoked after node is stopped
Key: IGNITE-2768
URL: https://issues.apache.org/jira/browse
Vladisav Jelisavcic created IGNITE-5059:
---
Summary: Implement logistic regression
Key: IGNITE-5059
URL: https://issues.apache.org/jira/browse/IGNITE-5059
Project: Ignite
Issue Type
41 matches
Mail list logo