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
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
wrote:
> Hi Tim,
>
> thanks for the update! I left you a comment on Jira.
>
> Best regards,
> Vladis
Hi Tim,
thanks for the update! I left you a comment on Jira.
Best regards,
Vladisav
On Mon, Jan 22, 2018 at 6:17 PM, Tim Onyschak wrote:
> Hey Vladisav,
>
> I implemented your requests. Take a look, specifically, i created an
> interface to encapsulate the NodeUpdates a
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
wrote:
> Hi Tim,
>
> thank you for the contribution!
> I'll do the review soon and let you know.
>
>
>
> On Wed, J
Hi Tim,
thank you for the contribution!
I'll do the review soon and let you know.
On Wed, Jan 17, 2018 at 8:56 AM, Yakov Zhdanov wrote:
> Thanks Tim! I hope Vlad can review your patch. If this does not happen in
> 2-3 days I will take a look. Can you please let me know on weekend if I
> need
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] https
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
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:
> Sounds lik
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
;;
> tab=buildResultsDiv&buildTypeId=IgniteTests_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.
>
> T
g/viewLog.html?buildId=544238&;
> tab=buildResultsDiv&buildTypeId=IgniteTests_IgniteBinaryObjectsDataStrucut
> ures
>
> Thanks!
>
> -Dmitry.
>
> 13.04.2017 16:15, Dmitry Karachentsev пишет:
>
> Thanks a lot!
>
> 12.04.2017 16:35, Vladisav Jelisavcic пишет:
>
Hi Dmitry,
sure, I made a fix, take a look at the PR and the comments in the ticket.
Best regards,
Vladisav
On Tue, Apr 11, 2017 at 3:00 PM, Dmitry Karachentsev <
dkarachent...@gridgain.com> wrote:
> Hi Vladislav,
>
> Thanks for your contribution! But it seems doesn't fix
GitHub user vladisav opened a pull request:
https://github.com/apache/ignite/pull/1780
IGNITE-4173
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladisav/ignite ignite-4173
Alternatively you can review and apply these
GitHub user vladisav opened a pull request:
https://github.com/apache/ignite/pull/1751
IGNITE-1977 Fixes IgniteSemaphore failover deadlock/fail bug
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladisav/ignite ignite-1977
Hey Dmitry,
sorry for the late reply, I'll try to bake a pr later during the day.
Best regards,
Vladisav
On Tue, Apr 4, 2017 at 11:05 AM, Dmitry Karachentsev <
dkarachent...@gridgain.com> wrote:
> Hi Vladislav,
>
> I see you're developing [1] for a while, did you ha
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
+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, Denis Magda
> > wrote:
> > +1 (binding)
> >
> > —
> > De
+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 official code review
> > tool.
> >
> > [ ]
Hi Sergey,
thanks for finding and submitting this bug!
Best regards,
Vladisav
On Thu, Nov 10, 2016 at 1:46 PM, Sergey Chugunov
wrote:
> Hello Vladisav,
>
> Thanks for confirmation!
>
> I created a JIRA <https://issues.apache.org/jira/browse/IGNITE-4209> to
> track
nodes,
this really is a bug.
Thanks!
Vladisav
On Wed, Nov 9, 2016 at 11:23 AM, Sergey Chugunov
wrote:
> Hello Vladisav,
>
> I found this behavior in a very simple environment: I had two nodes on my
> local machine started by *ExampleNodeStartup* class and another node
&g
this is not the case (test was executed normally) then please submit a
ticket describing more your setup,
how many nodes, how many backups configured, etc..
Thanks!
Vladisav
On Tue, Nov 8, 2016 at 10:37 AM, Sergey Chugunov
wrote:
> Hello folks,
>
> I found a reason why *IgniteSemapho
similar to:
https://issues.apache.org/jira/browse/IGNITE-3386).
This should be fixed (semaphore should be recreated when create==true, as
suggested by Denis in the ticket).
It should be a minor fix, will be ready for 1.8.
Best regards,
Vladisav
On Tue, Nov 1, 2016 at 5:41 PM, Andrey Gura
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,
,
Vladisav
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 incorrect.
>
> On Mon,
Hi,
I just recently started working on this,
you can track progress here [1] and of course here [2],
we also started a separate thread here [3].
Best regards,
Vladisav
[1] https://issues.apache.org/jira/browse/IGNITE-3131
[2] https://issues.apache.org/jira/browse/APEXMALHAR-2091
[3]
https
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
Github user vladisav closed the pull request at:
https://github.com/apache/ignite/pull/519
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
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
wrote:
> Yakov,
>
> I've finished the initialization tests for ignite-642 (and moved
> serialization test from GridCacheLo
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
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
wrote:
> Sure, I'll look into it later today, or tomorrow at th
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
> comments?
>
> --Yakov
>
> 201
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
wrote:
> Yakov, I've seen your comments, can you please check the jira again?
>
>
> On Wed, Mar 23
Yakov, I've seen your comments, can you please check the jira again?
On Wed, Mar 23, 2016 at 4:46 PM, Yakov Zhdanov wrote:
> Vlad, can you please check my comments again?
>
> --Yakov
>
> 2016-03-18 17:57 GMT+03:00 Vladisav Jelisavcic :
>
> > Hi Yakov,
> >
Hi Yakov,
yes, thanks for the comments, I think everything should be ok now,
please review the PR and tell me if you think anything else is needed.
Once ignite-642 is merged into master,
I'll submit a PR for IgniteReadWriteLock (hopefully on time for 1.6.
release).
Best regrads,
Vladisav
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
This sounds excellent, I'll get right to it.
Best regards,
Vladisav
On Fri, Mar 4, 2016 at 2:48 AM, Dmitriy Setrakyan
wrote:
> Vladislav,
>
> This would be a great contribution. For a feature like this, I would pick 1
> ML library and propose the design first. Once the commun
Igniters,
is IGNITE-1251 still a thing?
If so, I would really like to start working on this one.
Best regards,
Vladisav
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
GitHub user vladisav opened a pull request:
https://github.com/apache/ignite/pull/525
IGNITE-2735: Fixes distributed semaphore local node stopping issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladisav/ignite 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
Hi,
i recently implemented distributed ReentrantLock - IGNITE-642,
i made a pull request, so hopefully this could be added to the next release.
Best regards,
Vladisav
On Thu, Feb 18, 2016 at 10:49 AM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Folks,
>
> The current
GitHub user vladisav opened a pull request:
https://github.com/apache/ignite/pull/519
IGNITE-642: Implements cache distributed reentrant lock
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vladisav/ignite ignite-642
sense?
>
>
> --Yakov
>
> 2016-01-18 0:39 GMT+03:00 Andrey Kornev :
>
> > Just to clarify, 7.4 below refers to GridGain 7.4, which is Ignite 1.4.
> > _
> > From: Andrey Kornev
> > Sent: Sunday, January 17, 2016 10:27 AM
>
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
It does sounds like a useful addition,
and I believe it could be implemented easily.
I can do it if the community agrees on changing the API of the Semaphore.
Best regards,
VJ
On Sun, Jan 17, 2016 at 5:53 AM, Andrey Kornev
wrote:
> Dmitriy,I don't believe it makes sense to have the action execu
+1
On Wed, Dec 2, 2015 at 1:25 PM, Nikolay Tikhonov
wrote:
> +1
>
> On Wed, Dec 2, 2015 at 3:21 PM, Anton Vinogradov >
> wrote:
>
> > +1
> >
> > On Wed, Dec 2, 2015 at 3:16 PM, Yakov Zhdanov
> wrote:
> >
> > > Dear Sirs!
> > >
> > > We have uploaded release candidate to
> > > https://dist.apac
self.
In a realworld node failure scenario, all those threads would fail at the
same time
(none of them would influence the rest of the grid anymore);
I think fixing the issue Denis is working on can fix this (IGNITE-801 and
IGNITE-803)
Am i right? Does it makes sense?
Best regards,
Vladisav
On T
TOP_CHANGE_THEAD_CNT = 1
everything is running ok;
@Yakov
I made a new commit to my IGNITE-638 branch,
can you please take a look?
Best regards,
Vladisav
> On Wed, Nov 11, 2015 at 3:48 PM, Denis Magda wrote:
>
> > Hi Vladislav,
> >
> > Please see below..
> >
ngs.
I am still using partitioned cache, does it make sense to use replicated
cache instead?
Other than that, I'm done with everything else.
Thanks,
Vladisav
On Tue, Nov 10, 2015 at 7:19 PM, Raul Kripalani wrote:
> Sorry I haven't made an appearance in this thread ye
Assigned IGNITE-642 and IGNITE-637 to me,
and unassigned IGNITE-640.
If nobody picks it up in the near future,
I will do it (after I'm done with IGNITE-642 and IGNITE-637).
Best regards,
VJ
On Thu, Nov 5, 2015 at 1:48 AM, Dmitriy Setrakyan
wrote:
> On Tue, Nov 3, 2015 at 5:46 AM,
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 really great addition to
>10. I would also like to include distributed Semaphore. Vladislav, any
>chance you can finish with it this week?
>https://issues.apache.org/jira/browse/IGNITE-
><https://issues.apache.org/jira/browse/IGNITE-426>638
I will have it done by thursday.
Best regards,
Vladisav
On M
Github user vladisav closed the pull request at:
https://github.com/apache/ignite/pull/120
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user vladisav reopened a pull request:
https://github.com/apache/ignite/pull/120
IGNITE-638: Implements cache distributed semaphore
This interface provides a rich API for working with distributed semaphore.
Distributed semaphore provides functionality similar to
GitHub user vladisav opened a pull request:
https://github.com/apache/ignite/pull/120
Implements distributed semaphore ignite-638
This interface provides a rich API for working with distributed semaphore.
Distributed semaphore provides functionality similar to
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
57 matches
Mail list logo
