+1
On Mon, 22 Aug 2022 at 17:07 Mikhail Pochatkin
wrote:
> Hi Igniters,
>
> I want to start a voting process about several points from IEP-93 [1].
>
> 1. Switch Apache Ignite build system to Gradle as default.
> 2. Consequently, after changing the build system to Gradle we need to add
> new thir
+1
ср, 1 июн. 2022 г. в 12:19, Alexander Lapin :
> +1
>
> ср, 1 июн. 2022 г. в 12:14, ткаленко кирилл :
>
> > + 1
> >
>
rgence/release candidate build, please let know.
>
> Sincerely,
> Dmitriy Pavlov
>
> On 2021/05/13 09:45:02, Алексей Гидаспов wrote:
> > Dear Ignite Community!
> >
> > I suggest starting Apache Ignite 2.11 release activities. Also suggest
> > mysel
wrote:
> > My login is: agidaspov
> > E-mail: olive.c...@gmail.com
> >
> > On 2021/06/03 08:17:15, Dmitry Pavlov wrote:
> > > Can you please sign in to cwiki and share your login?
> > >
> > > wiki admins (PMC members) could grant access in tha
My login is: agidaspov
E-mail: olive.c...@gmail.com
On 2021/06/03 08:17:15, Dmitry Pavlov wrote:
> Can you please sign in to cwiki and share your login?
>
> wiki admins (PMC members) could grant access in that case.
>
> On 2021/06/03 07:11:54, Алексей Гидаспов wrote:
&
Hi, Igniters!
As a release manager of 2.11 Apache Ignite release I need edit access to
cwiki.apache.org Apache Ignite space. Please tell me, how can I obtain it?
t; > I guess we can just pick up master current state and release it. But if
> > someone has some ideas if we should wait for particular feature to be
> > completed before branch divergence/release candidate build, please let
> know.
> >
> > Sincerely,
> > D
Dear Ignite Community!
I suggest starting Apache Ignite 2.11 release activities. Also suggest
myself to be a release manager for this release. I plan release at the end
of june 2021.
___
Best Regards,
Alexey Gidaspov
Hello Ignite Community,
My name is Alexey and I'm a Java and Scala developer with a current focus
on Big Data stack like Spark and Hadoop.
I would like to take part in the Apache Ignite project and make a
contribution to it.
I'm thinking to start with some easy fix or bugfix to get more
acquainte
+1 for Dmitry Pavlov
чт, 31 окт. 2019 г. в 01:23, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> +1 Dmitry Pavlov (binding)
>
> On Wed, Oct 30, 2019 at 12:55 PM Alex Plehanov
> wrote:
>
> > + 1 Dmitry Pavlov
> >
> > ср, 30 окт. 2019 г. в 20:50, Pavel Kovalenko :
> >
> > > +1 for Dmitry
ith some
> cache?) on demand.
>
>
> On Tue, Sep 10, 2019 at 2:09 PM Алексей Платонов
> wrote:
> >
> > I mean metrics for model evaluation like Accuracy or Precision/Recall for
> > ML models. It isn't same as system metrics (like throughput). Such
>
stributed metrics in the first place?
> It seems, there are many metric processing system out there: Prometheus,
> Zabbix, Splunk, etc.
>
> Each of then can aggregate metrics in many ways.
>
> I think, we should not use Ignite as an metrics aggregation system.
>
> What do you th
Hi Igniters!
I've been working on a prototype of distributed metrics computation for
ML-models. Unfortunately, we don't have an ability to compute metrics in a
distributed manner, so, it leads to gathering metric statistics to client
node via ScanQuery and all flow of vectors from partitions will b
5 июн. 2019 г. в 17:20, Yuriy Babak :
> Alexey,
>
> This is a cool change, do you create a ticket for it?
>
> If no I can create one.
>
> Best regards,
> Yuriy Babak
>
>
> пт, 31 мая 2019 г. в 14:20, Алексей Платонов :
>
> > Hi, Igniters!
> > Curre
Hello, it would be nice to have a subj in Ignite.
Thx
27;t require to change APIs of
these classes.
Sincerely
Alexey Platonov
пт, 31 мая 2019 г. в 14:51, Alexey Zinoviev :
> It sounds great, could you please explain what are you going to change in
> the main Vectorizer/Preprocessor API to support it?
>
> пт, 31 мая 2019 г. в 14:20, Алексей Пл
Hi, Igniters!
Currently we don't have an ability to deploy automatically user-defined
preprocessors and vectorizers. Client's code should be deployed manually to
Ignite server nodes.
I have an idea how to fix it. If we pass user's classloader and one of
user-defined classes from fit-level to
Compu
Hey, Igniters!
I prepared some PR for Serializable support in our Vectors.
Could you review this: https://github.com/apache/ignite/pull/6378 ?
чт, 28 мар. 2019 г. в 11:47, Алексей Платонов :
> Yep, I definitely agree with you.
>
> Moreover, such improvement should reduce parallel hiera
Yep, I definitely agree with you.
Moreover, such improvement should reduce parallel hierarchies in trainers
and preprocessors, from this point of view preprocessor will be equal to a
trainer. In my opinion, this improvement is very important for ml module
because it can give a flexible hierarchy o
gnite sub-projects as well.
>
> пт, 1 мар. 2019 г. в 19:04, Алексей Платонов :
> >
> > Hello, Igniters!
> > I would like to create several tests for ML algorithms using binary
> builds.
> > These tests should work in this way:
> > 1) Get last master (or user
Hello, Igniters!
I would like to create several tests for ML algorithms using binary builds.
These tests should work in this way:
1) Get last master (or user-defined branch) from git repository;
2) Build Ignite with a release profile and create binary build;
3) Run several Ignite instances from bin
Hello!
I would like to contribute to apache ignite and i am asking for contribution
permission.
I would like to start with ignite-2196 to get familiar with contribution
process. The issue Is still reproducable. I am plannig to remove the link and
wrap it into @code directive as suggested in comm
Hello!
I would like to contribute to apache ignite and i am asking for contribution
permission.
I would like to start with ignite-2196 to get familiar with contribution
process. The issue Is still reproducable (broken link from documentation -
https://ignite.apache.org/releases/latest/javadoc/i
You can compute just TP (true-positive), FP, TN and FN counters and use
them to evaluate Recall, Precision, Accuracy, ect. If you want to specify
class for Pr evaluation, then you can compute Pr for first label as
TP/(TP+FP) and for second label as TN/(TN+FN) for example. After it we can
unite all
Hi
After Alexander create separate tickets for failed tests, everybody is
free to fix them.
So we can proceed faster issue resolving.
Hello, Igniters.
Actually, I don't understand why we should merge in master something broken.
Currently, Ignite is not ready for JCache 1.1.
Only change I see
PR for this issue is ready to be reviewed.
Changes are relatively small.
1. No network messages have been changed.
2. Thread id usage replaced with xid usage when we work with candidates.
3. All current tests are passed [3]
Please, review. [1], [2]
[1] https://issues.apache.org/jira/browse/IGNI
Hello all
Thank you, Alexey!
>Вторник, 27 марта 2018, 21:57 +06:00 от Alexey Goncharuk
>:
>
>Hello Alexey,
>
>Welcome to the Ignite community! I've added you to the contributors list,
>you should be now able to assign the JIRA ticket.
>
>--AG
>
>2018-03-27 18:42 GMT+03:00 Spider (Alexey) < spid
I would like to join apache ignite development.
My JIRA ID is rokhin
Going to start from IGNITE-7281.
BR
I would like to join apache ignite development.
My JIRA ID is r okhin
Going to start from IGNITE-7281.
BR
Dear Ignite community,
Can you please grant me (lexa) contributor access, so that I can
assign Ignite Jira issues to myself ?
Best Regards
Aleksey Chetaev.
30 matches
Mail list logo