+1
Thanks,
S.
вт, 16 июл. 2024 г. в 09:46, Maksim Timonin :
> Hi Igniters,
>
> I'd like to start a voting process about moving Ignite 2.x sources to
> JDK11. Discussion of the proposal is here [1].
>
> The plan is as follows:
> 1. Upgrade all TeamCity jobs from jdk1.8 to jdk11.
> 2. Review and
Hello Igniters,
+1 (binding)
Thanks,
S.
вт, 18 июн. 2024 г. в 07:44, Andrey Novikov :
> Dear Community,
> The release candidates are ready. See the links below.
>
>
> == Ignite Spring Data Extension Module 3.0.0 ==
>
> The release candidate is uploaded to:
>
>
Congratulations, keep it going!
Thanks,
S.
ср, 8 мая 2024 г. в 07:27, Pavel Tupitsyn :
> Dear Igniters,
>
> The Project Management Committee (PMC) for Apache Ignite
> has invited Mikhail Pochatkin to become a committer and we are pleased
> to announce that they have accepted.
>
> Being a
Congrats, Roman! Well deserved!
Thanks,
S.
ср, 8 мая 2024 г. в 07:28, Pavel Tupitsyn :
> Dear Igniters,
>
> The Project Management Committee (PMC) for Apache Ignite
> has invited Roman Puchkovskiy to become a committer and we are pleased
> to announce that they have accepted.
>
> Being a
Hi Nikita,
Is it possible to add the following ticket to the scope of the release as
well?
https://issues.apache.org/jira/browse/IGNITE-21032
GitHub issue: https://github.com/apache/ignite/issues/11045
Thanks,
S.
пн, 4 дек. 2023 г. в 21:13, Nikita Amelchev :
> Hello, Igniters.
>
> I had a
Congratulations, Nikita!
Thanks,
S.
ср, 22 нояб. 2023 г. в 18:55, Ivan Daschinsky :
> Congratulations, you deserve it
>
> On Wed, Nov 22, 2023, 18:10 Nikita Amelchev wrote:
>
> > Thank you everyone, I'm very pleased!
> >
> > ср, 22 нояб. 2023 г. в 15:46, Ilya Shishkov :
> > >
> > >
Well deserved! Three cheers for you, Stephen!
Thanks,
S.
пн, 4 сент. 2023 г. в 12:38, Wei Cheng <29608336...@gmail.com>:
>
> Congratulations
>
> Thanks
> Wei Cheng
>
> > 在 2023年9月4日，17:28，ZhangJian He 写道：
> >
> > Configurations!
> >
> > Thanks
> > ZhangJian He
> >
> >
> >> On Mon, 4 Sept 2023
; Great idea.
> Could I ask you to do this?
>
> On Wed, Aug 23, 2023 at 6:16 PM Вячеслав Коптилин <
> slava.kopti...@gmail.com>
> wrote:
>
> > Hi Anton,
> >
> > +1 for removal MVCC
> >
> > I think it would be nice to close (with "will not fix"
tes removal PR was merged.
>
> Slava,
> > I think it would be nice to close (with "will not fix" status) all open
> > tickets related to MVCC
>
> Great idea.
> Could I ask you to do this?
>
> On Wed, Aug 23, 2023 at 6:16 PM Вячеслав Коптилин <
&g
Hi Anton,
+1 for removal MVCC
I think it would be nice to close (with "will not fix" status) all open
tickets related to MVCC:
Congratulations, Alexander! Keep it up!
Thanks,
S.
пн, 21 авг. 2023 г. в 09:14, Roman Puchkovskiy :
> Congratulations!
>
> пн, 21 авг. 2023 г. в 09:29, Pavel Tupitsyn :
> >
> > Congratulations, Aleksandr! Well deserved!
> >
> > On Mon, Aug 21, 2023 at 8:01 AM Kseniya Romanova
> > wrote:
> >
>
Hello,
I don't have any objections. Let's clean up the code.
Thanks,
Slava.
вт, 4 июл. 2023 г. в 19:47, Николай Ижиков :
> Hello, Igniters.
>
> IgniteCacheSnapshotManager is internal component that was deprecated more
> then 3 years for now.
> I have plans to remove it from codebase.
> Is
+1
ср, 29 мар. 2023 г. в 21:57, Alex Plehanov :
> Dear Ignite Community!
>
> I suggest starting Apache Ignite 2.15 release activities.
>
> We've accumulated more than two hundred resolved issues [1] with new
> features and bug fixes which are waiting for release.
> The major changes related to
+1
ср, 15 февр. 2023 г. в 10:21, Ivan Daschinsky :
> Dear Igniters!
>
> This is a patch release that contains an important fix for users of
> pyignite
>
> https://issues.apache.org/jira/browse/IGNITE-18788
>
>
> Release candidate binaries for subj are uploaded and ready for vote
> You can find
+1
пн, 12 дек. 2022 г. в 14:35, Pavel Tupitsyn :
> +1 (binding)
>
> On Mon, Dec 12, 2022 at 2:34 PM Maxim Muzafarov wrote:
>
> > +1
> >
> > On Mon, 12 Dec 2022 at 09:59, Andrey Gura wrote:
> > >
> > > +1
> > >
> > > On Fri, Dec 9, 2022 at 10:36 AM Nikita Amelchev
> > wrote:
> > > >
> > > >
Hi Aleksandr,
This suggestion seems useful to me.
As Aleksandr pointed out, this is a compile-time dependency, so it doesn't
look risky.
+1
Thanks,
Slava.
ср, 7 дек. 2022 г. в 10:20, Aleksandr Polovtsev :
> Dear Igniters! In Ignite 3, we have a bunch of classes that utilize the
> Java SPI
Hi Igniters,
I fully support the idea to stop supporting Visor and removing its
implementation.
However, do we have a list of useful features that do not exist in our
control utility?
Perhaps, it makes sense to reimplement such functionality and provide it
based on control.sh script.
Thanks,
Dear Igniters,
I'm happy to announce that the 1st beta version of Ignite 3 is out!
On top of the functionality that was previously released, Beta 5 adds the
following major features:
- RPM and DEB packages: simplified installation and node management with
system services.
- Client's Partition
Dear Igniters,
Apache Ignite 3.0.0-beta1 RC2 has been accepted.
8 "+1" votes received:
- Pavel Tupitsyn (binding)
- Alexander Lapin
- Denis Chudov
- Vladislav Pyatkov
- Yuriy Gerzhedovich
- Igor Sapego (binding)
- Mirza Aliev
- Igor Gusev
No "0" or "-1" votes.
Dear Community,
Ignite 3 is moving forward and I think we're in a good spot to release the
first beta version. In the last few months the following major features
have been added:
- RPM and DEB packages: simplified installation and node management with
system services.
- Client's Partition
ne?
> Isn't
> >>> nuget package enough for .NET ecosystem?
> >>>
> >>> Thanks,
> >>> Stan
> >>>
> >>>> On 9 Nov 2022, at 19:55, Pavel Tupitsyn wrote:
> >>>>
> >>>> Also:
> >>>>
Dear Community,
Ignite 3 is moving forward and I think we're in a good spot to release the
first beta version. In the last few months the following major features
have been added:
- RPM and DEB packages: simplified installation and node management with
system services.
- Client's Partition
Hello Igniters,
I would like to inform you that a code freeze started.
Only blockers are accepted to be included to the scope.
Thanks,
Slava.
reeze according to the ticket
> >> estimates instead of just setting it to the end of next week. I'll work
> >> with each ticket owner to determine the critical path.
> >>
> >> I also saw an Open ticket that was added to the scope outside of the
>
.apache.org/jira/browse/IGNITE-17773>
>
> These tickets are the last tickets in the packaging scope for beta1.
>
> --
> Best regards,
> Aleksandr
>
> > On 19 Oct 2022, at 21:48, Вячеслав Коптилин
> wrote:
> >
> > Hi Yuriy,
> >
> > Let's add them. I hope t
E-17907
> https://issues.apache.org/jira/browse/IGNITE-17671
> https://issues.apache.org/jira/browse/IGNITE-17816
>
> So, I propose adding them into the release scope.
>
> ср, 19 окт. 2022 г. в 15:53, Вячеслав Коптилин :
>
> > Hi Yuriy,
> >
> > I agree, let's add th
support RO
> transaction
> by SQL
> https://issues.apache.org/jira/browse/IGNITE-17859 - index filling
> https://issues.apache.org/jira/browse/IGNITE-17813 - related to support
> indexes by SQL
> https://issues.apache.org/jira/browse/IGNITE-17655 - related to support
> indexes by
Hello Alexander,
Thank you for pointing this out. I fully support including RO transactions
into the scope of Ignite 3.0.0-beta1 release.
Thanks,
S.
ср, 19 окт. 2022 г. в 11:42, Alexander Lapin :
> Igniters,
>
> I would like to add following tickets to ignite-3.0.0-beta1
>
Hi Stan,
> I’ll need help from a PMC to do the steps requiring PMC permissions but I
can do most of the work.
I'm ready to assist you with this.
Thanks,
Slava.
чт, 13 окт. 2022 г. в 15:08, :
> Hi,
>
> I’ll be happy to do this.
>
> I’ll need help from a PMC to do the steps requiring PMC
Hi,
Congratulations Ivan! Well-deserved!
Thanks,
Slava.
вс, 18 сент. 2022 г. в 12:10, Zhenya Stanilovsky :
>
> Join the congratulations !
>
>
>
>
> >Hi Igniters!
> >
> >The Project Management Committee (PMC) for Apache Ignite has invited
> >Ivan Daschinsky to become a member of the PMC and we
+1
пт, 26 авг. 2022 г. в 18:07, Mikhail Pochatkin :
> Hi! No, this doesn't affect Ignite 2.x. This IEP is applicable only for
> Apache Ignite 3.
>
> On Fri, Aug 26, 2022 at 5:47 PM Ilya Kasnacheev >
> wrote:
>
> > Hello!
> >
> > Please clarify whether this is Apache Ignite 3 only and that it
Congratulations, Taras, very well deserved!
Thanks,
S.
вс, 21 авг. 2022 г. в 19:26, Ilya Shishkov :
> Congratulations, Taras!
>
> вс, 21 авг. 2022 г. в 09:52, Pavel Tupitsyn :
>
> > Congrats!
> >
> > Pavel
> >
> > On Sun, Aug 21, 2022 at 9:07 AM Ivan Pavlukhin
> > wrote:
> >
> > >
Hi Igniters,
Many thanks to all of you! I really appreciate this.
Thanks,
S.
чт, 18 авг. 2022 г. в 17:17, Andrey Mashenkov :
> Congratulations, Slava!
>
> On Wed, Aug 17, 2022 at 5:35 PM Kseniya Romanova
> wrote:
>
> > Hi Igniters!
> >
> > The Project Management Committee (PMC) for Apache
Hello,
I will take a look.
Thanks,
Slava.
чт, 18 авг. 2022 г. в 16:54, liyuj :
> Hello,
>
> Is there anyone willing to help merge the following PR?
>
> https://github.com/apache/ignite/pull/10203
>
> At 2022-08-18 21:11:00, "YuJue Li (Jira)" wrote:
> >YuJue Li created IGNITE-17556:
>
Hello Andrey,
Data rebalancing (https://issues.apache.org/jira/browse/IGNITE-14209) is
already done and merged to main & ignite-3.0.0-alpha5 branches.
Thanks,
S.
пн, 6 июн. 2022 г. в 22:52, Andrey Gura :
> Igniters,
>
> ignite-3.0.0-alpha5 release branch has been created. But the following
>
+1
Thanks,
S.
ср, 1 июн. 2022 г. в 12:56, Ilya Korol :
> +1
>
> 01.06.2022 19:14, ткаленко кирилл пишет:
> > + 1
>
Hi,
Congratulations, Alexander!
Thanks,
S.
ср, 9 мар. 2022 г. в 18:57, Ivan Pavlukhin :
> Alex, congratulations, well deserved!
>
> 2022-03-09 18:18 GMT+03:00, Petr Ivanov :
> > Congratulations!
> >
> >> On 9 Mar 2022, at 17:46, Kseniya Romanova
> wrote:
> >>
> >> Igniters! The Apache Ignite
Hello Anton,
This IEP is already placed under Proposals for Ignite 3.0 section
https://cwiki.apache.org/confluence/display/IGNITE/Proposals+for+Ignite+3.0
Perhaps, we need to move all that stuff to
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3
Thanks,
S.
пн, 21 февр. 2022
/jira/browse/IGNITE-12464
> >
> >
> > On Wed, Jan 19, 2022 at 1:22 AM Valentin Kulichenko <
> > valentin.kuliche...@gmail.com> wrote:
> >
> > > What are the metrics that are being affected by this?
> > >
> > > -Val
> > &g
Hello Igniters,
IMHO, this is not a good idea to change the behavior of serviceProxy()
depending on statistics (enabled/disabled). It seems counterintuitive to me.
Perhaps, we need to introduce a new method that should always return a
proxy to the user service.
Thanks,
Slava.
вт, 28 дек. 2021
Hi,
Congratulations, Vlad!
Thanks,
S.
чт, 23 дек. 2021 г. в 11:59, Anton Vinogradov :
> Welcome aboard!
>
> On Thu, Dec 23, 2021 at 10:24 AM Ivan Pavlukhin
> wrote:
>
> > Congrats, Vlad!
> >
> > 2021-12-22 20:48 GMT+03:00, Ivan Daschinsky :
> > > Vlad, congrats! You have definitely deserved
Hello,
+1
Thanks,
S.
пн, 20 дек. 2021 г. в 16:26, Nikolay Izhikov :
> +1 (binding)
>
> > 20 дек. 2021 г., в 16:20, Ivan Daschinsky
> написал(а):
> >
> > +1 from me
> > Checked ODBC drivers (32-bit and 64-bit) installers on Windows with
> running
> > locally Ignite with
> > pyodbc and python
1 г. в 16:28, Вячеслав Коптилин :
>
> > Hello Maxim,
> >
> > Honestly, I don't quite understand why ODBC improvement is included in
> the
> > release.
> > It seems to me, we have an agreement that the scope of the 2.11.1 release
> > will be limited by log4j
Hello Maxim,
Honestly, I don't quite understand why ODBC improvement is included in the
release.
It seems to me, we have an agreement that the scope of the 2.11.1 release
will be limited by log4j issues.
Thanks,
S.
пт, 17 дек. 2021 г. в 15:20, Maxim Muzafarov :
> The release candidate for the
Hi Nikita,
The proposed timeline looks great. Thank you!
Slava.
пт, 17 дек. 2021 г. в 15:32, Nikita Amelchev :
> Hello, Slava.
>
> I am planning the following timeline:
>
> Voting Date: December 20, 2021
> Release Date: December 27, 2021
>
> чт, 16 дек. 2021 г. в
ed to do a stabilization release we
> > should unbound it from this urgent fix.
> >
> > I wonder why 2.12 is not with us already, given that it was scheduled to
> go
> > out in August.
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
Hello,
> Given that 2.12 is so close, my preference would be to limit the scope of
2.11.1 to just the log4j update.
I agree with Stephen. Apache Ignite 2.11.1 is an emergency release. Using
log4j 2.16 instead of 2.14 is a quite small change that only requires a
"sanity" check and can be quickly
Hi folks,
IMHO, we should do our best to fix all these places and should avoid using
the default charset. In my understanding, this is only
> The main question is - should we restrict the join of nodes with
different encodings or just fix all places where implicit default encoding
is used and
issue [1] to the 2.12. It updates the log4j
> version to 2.16.
>
> Slava, thank you.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-16127
>
> ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин :
> >
> > Hello,
> >
> > Nikita, it seems that we have to add
Hello,
Nikita, it seems that we have to add the following ticket
https://issues.apache.org/jira/browse/IGNITE-16127 to Apache Ignite 2.12
release.
Thanks,
S.
вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev :
> +1 to move these auth issues to the next release. I will prepare RC at
> the nearest
tandable that a method signature can be updated, or another
> similar
> > > change can be made in internal APIs. However, changes like system cache
> > > removal are much more critical, because a plugin might rely on it.
> It's our
> > > responsibility as a good fri
> Plugins have access to different internal Ignite components, such as
> security processor and others, and can extend the programmatic API of
> Ignite.
>
> Where docs say that we, as a community, take responsibility to keep
> internals in the way plugin expect?
>
> >
be respectful
> to
> > those users, provide a reasonable documented alternative and give time.
> >
> > -Val
> >
> > On Fri, Dec 3, 2021 at 8:18 AM Nikolay Izhikov
> wrote:
> >
> >> I don’t understand how it possible.
> >>
> >> Are you talking
e the ability to atomically
> >>>> change several properties at the same time (there are no transactions
> >> on
> >>>> this API).
> >>>>
> >>>> Can you share an example of what kind of properties we intend to
> >>>&g
gt; > > >
> > > > Agree with Slava. Two months is not enough time, especially
> considering
> > > > that the system cache is not functionally equivalent to the
> metastorage.
> > > I
> > > > suggest we do the following:
> > > >
> > > >
Hi Maxim,
> On the other hand, I don't see any valuable reason why the change can't
be done and we should wait for the future that never comes.
Maxim, the community must provide a reasonable time interval in order to
notify all contributors and wait for updating all 3-rd party plugins.
Honestly,
Hi,
Congrats, Maxim!
Thanks,
S.
вт, 30 нояб. 2021 г. в 20:13, Maksim Timonin :
> Hi, guys!
>
> Thanks everyone :)
>
> On Tue, Nov 30, 2021 at 1:16 PM Petr Ivanov wrote:
>
> > Great news! Congratulations, Maksim!
> >
> >
> > > On 29 Nov 2021, at 19:13, Kseniya Romanova
> > wrote:
> > >
> > >
Hooray!
Congrats! May the Force be with you!
Thanks,
S.
ср, 1 дек. 2021 г. в 12:02, Petr Ivanov :
> Congratulations!
>
>
> > On 1 Dec 2021, at 01:48, Andrey Gura wrote:
> >
> > Igniters,
> >
> > The Apache Ignite Project Management Committee (PMC) has invited
> > Semyon Danilov to become a
Hello,
Yep, absolutely the same.
Thanks,
S.
пт, 12 нояб. 2021 г. в 11:12, Ivan Pavlukhin :
> A last one I received was IGNITE-15872 as well.
>
> 2021-11-11 22:43 GMT+03:00, Ilya Kasnacheev :
> > Hello!
> >
> > For some reason, looks like it has stopped working. I did not get any
> >
Hello Pavel,
It seems that your commit https://issues.apache.org/jira/browse/IGNITE-15801
broke the javadoc suite.
Team City:
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Javadoc?branch=%3Cdefault%3E=builds#6261281
Could you please take a look?
Thanks,
S.
-1
I am leaning toward -1 because of vulnerability issues (that is a possible
case in general).
Thanks,
S.
ср, 8 сент. 2021 г. в 12:13, Andrey Mashenkov :
> -1
> Supporting few copy-pasted methods is much easier than support dependencies
> compatibility.
>
> On Tue, Sep 7, 2021 at 7:42 PM
Hooray!
Congrats! May the Force be with you!
Thanks,
S.
пт, 30 июл. 2021 г. в 11:17, Anton Vinogradov :
> Congrats!
>
> On Fri, Jul 30, 2021 at 10:19 AM ткаленко кирилл
> wrote:
>
> > Zhenya, congratulations!
> >
> > Пересылаемое сообщение
> > 30.07.2021, 09:50, "Ivan
By the way, we already fixed the issue
https://issues.apache.org/jira/browse/IGNITE-14248 that looks very close to
what we are discussing now.
Thanks,
S.
чт, 15 июл. 2021 г. в 11:17, Вячеслав Коптилин :
> Hi Pavel,
>
> >As for handling the exception in this case, from my p
e
> (these are not caching operations, detection, etc.), but perhaps I am
> wrong here. Also, in this particular case, only one checked exception
> is possible - if re-encryption is started when the node is stopped (I
> think handling it with a failure handler is redundant).
>
> вт, 13
Hello Pavel,
Could you please assist me in understanding the fix that was implemented
under https://issues.apache.org/jira/browse/IGNITE-14424
In particular, it seems odd to me, just logging an exception in case
starting re-encryption failed with an error/exception.
Please take a look at
s absolutely insane,
> normal users pass passwords using environment variables.
>
> At least, we could just hide params that match specific pattern
>
> Ilya, go ahead, file ticket and prepare a PR.
>
> чт, 1 июл. 2021 г., 16:45 Вячеслав Коптилин :
>
> > Hello,
> >
>
Hello,
Unfortunately, the user can pass its own system properties via JVM options
as follows: -DMY_SECRET_PASSWORD=123
It does not seem, this approach is the best one. However, the user should
have a "kostyl" in order to hide these properties and values in the log
file, IMHO.
Thanks,
S.
ср, 30
+1
Thanks,
S.
пн, 28 июн. 2021 г. в 18:09, Igor Sapego :
> +1
>
> Best Regards,
> Igor
>
>
> On Sat, Jun 26, 2021 at 1:41 AM Nikita Ivanov wrote:
>
> > +1
> >
> > --
> > Nikita Ivanov
> >
> >
> >
> > On Fri, Jun 25, 2021 at 3:31 PM Valentin Kulichenko <
> > valentin.kuliche...@gmail.com>
Hello Ilya,
Could you please add me to the "Contributors 1" role?
Thanks,
S.
пн, 26 апр. 2021 г. в 12:29, Ilya Kasnacheev :
> Hello!
>
> I have added you to "Contributors 1" role. Everybody in this role will
> still get those "issue created" e-mail.
>
> Feel free in asking me to enlist.
>
>
Hello Alexei,
It would be nice to add something like as follows:
boolean isInfoEnabled();
boolean isDebugEnabled();
or
boolean isLoggable(Level) - the same way which System.Logger suggests
Thanks,
S.
пт, 26 мар. 2021 г. в 17:41, Alexei Scherbakov :
> Andrey,
>
> I've introduced a
method like putAsync.
>
>
> So I propose to have a safe default.
> Then document the performance tuning opportunity on [1].
>
> Think about how many users abandon a product because it mysteriously
> crashes and hangs.
>
> [1]
>
> https://ignite.apache.org/docs/latest/p
ase.
>
>
> On Wed, Mar 17, 2021 at 3:34 PM Вячеслав Коптилин <
> slava.kopti...@gmail.com>
> wrote:
>
> > Well, the specified method already exists :)
> >
> > /**
> > * Registers listener closure to be asynchronously notified whene
exec Executor to run listener. Cannot be {@code null}.
*/
public void listenAsync(IgniteInClosure> lsnr,
Executor exec);
Thanks,
S.
ср, 17 мар. 2021 г. в 15:25, Вячеслав Коптилин :
> Hello Pavel,
>
> I took a look at your IEP and pool request. I have the following concerns.
&g
Hello Pavel,
I took a look at your IEP and pool request. I have the following concerns.
First of all, this change breaks the contract of IgniteFuture#listen(lsnr)
/**
* Registers listener closure to be asynchronously notified whenever
future completes.
* Closure will be processed
Hello,
My congratulations, Ivan! May the Force be with you!
Thanks,
S.
вт, 12 янв. 2021 г. в 14:27, Ivan Pavlukhin :
> Ivan, congratulations!
>
> 2021-01-12 13:36 GMT+03:00, Kseniya Romanova :
> > Ivan, my congratulations!
> >
> > вт, 12 янв. 2021 г. в 13:32, Andrey Gura :
> >
> >> Igniters,
>
gt;
> [1] https://issues.apache.org/jira/browse/IGNITE-13871
>
> On Thu, 17 Dec 2020 at 12:23, Вячеслав Коптилин
> wrote:
> >
> > The vote is closed now.
> >
> > Vote result: Vote passed with 13 "+1" votes, no "0" and no "-1" votes.
>
The vote is closed now.
Vote result: Vote passed with 13 "+1" votes, no "0" and no "-1" votes.
+1 Votes:
Valentin Kulichenko
Nikolay Izhikov
Andrey Gura
Igor Seliverstov
Andrey Mashenkov
Kirill Tkalenko
Nikita Amelchev
Petr Ivanov
Alexei Scherbakov
Maxim Muzafarov
Yuriy Gerzhedowich
Konstantin
art the vote and
> see what happens.
>
> On Wed, 2 Dec 2020 at 16:39, Вячеслав Коптилин
> wrote:
> >
> > > It will be even worse if our users will face NPE or things like that
> in
> > the basic MVCC scenarios just because we don’t tests it.
> > The feature is no
kolay Izhikov :
> > I think test suites can be disabled even today
>
> I’m -1 to disable tests without complete removal.
> It will be even worse if our users will face NPE or things like that in
> the basic MVCC scenarios just because we don’t tests it.
>
>
> >
. I just want to save the time required for getting TCBot's visa and TC
> resources.
>
> Why do we need feature in the project that not even tested regularly?
>
> > 2 дек. 2020 г., в 15:36, Вячеслав Коптилин
> написал(а):
> >
> > Hello Nikolay,
> >
> >> +1
llo Slava,
> >
> > I think we should vote for MVCC termination of support. If the vote
> > will be successful than remove it from the source code and disable
> > MVCC suites.
> >
> > Only disabling tests from MVCC sounds not good.
> >
> &g
; I think we should vote for MVCC termination of support. If the vote
> will be successful than remove it from the source code and disable
> MVCC suites.
>
> Only disabling tests from MVCC sounds not good.
>
> On Wed, 2 Dec 2020 at 12:32, Вячеслав Коптилин
> wrote:
> >
&g
Hello Igniters,
It looks like there is no activity related to maintaining or developing the
MVCC feature.
So, I see no reason to waste TeamCity resources. I propose to disable the
corresponding test suites.
This has already been discussed here as well [1].
[1]
Hooray!
Congratulations, Alex! Well deserved achievement!
Thanks,
S.
ср, 18 нояб. 2020 г. в 03:26, Denis Magda :
> Igniters,
>
> The Project Management Committee (PMC) for Apache Ignite
> has invited Alex to become a PMC member and we are pleased to announce that
> he has accepted.
>
> Alex
Hello Kirill,
Thanks a lot for driving this activity. If I am not mistaken, this
discussion relates to IEP-40.
> I suggest adding a warmup phase after recovery here [1] after [2], before
discovery.
This means that the user's thread, which starts Ignite via
Ignition.start(), will wait for ana
Hi,
Well deserved! Keep it up, Sergey!
Thanks,
S.
пт, 17 июл. 2020 г. в 14:36, Ivan Pavlukhin :
> Sergey, congratulations!
>
> 2020-07-17 14:25 GMT+03:00, Petr Ivanov :
> > Congratulations!
> >
> >
> >> On 17 Jul 2020, at 14:14, Roman Kondakov
> >> wrote:
> >>
> >> Sergey, congratulations!
>
Hello Artem,
Congratulations! You definitely deserve it.
Thanks,
S.
чт, 16 июл. 2020 г. в 15:26, Ivan Pavlukhin :
> Artem, my congratulations!
>
> 2020-07-16 15:10 GMT+03:00, Roman Kondakov :
> > Congrats, Artem!
> >
> > --
> > Roman Kondakov
> >
> > On 16.07.2020 14:19, Ilya Kasnacheev wrote:
definitely should be checked as early as
> possible and by default should fail Ignite build.
> But for exceptional cases (which was mentioned by Slava), can we add some
> "Run custom build" parameter on TC to be able to exclude "checkstyle"
> profile from "~Build Apache Ig
/github.com/apache/ignite/commit/2a85925f1705fbad36b5421c0ca5cf9de9a29658
>
> https://github.com/apache/ignite/commit/d63f4d3569dcb387394d367a7f00aaf35f1b288e
>
>
>
> > 7 июля 2020 г., в 12:52, Вячеслав Коптилин
> написал(а):
> >
> > Hi Maxim,
> >
> &g
0 г. в 12:21, Maxim Muzafarov :
> Slava,
>
> Why the auto-formatting procedure cannot be used for any PR you'd like
> to run on TC? Even more, you can remove all the rules from checkstyle
> XML config and do all you want in the PR branch.
>
> On Tue, 7 Jul 2020 at 12:17,
s the issue here.
>
> If we don’t want to follow the code style or considered it as a «waste of
> the time» we should change it.
> As simple as that.
>
> But, we should force the code style as early as we can.
> I think we should fail maven local build on code style violati
can help a newcomer with the code style -
> GitHub interface has the edit button even for someone else’s PR’s
>
>
> > 7 июля 2020 г., в 11:01, Вячеслав Коптилин
> написал(а):
> >
> > Hello Nikolay,
> >
> >> Because any code style violations sho
running heavy suites when code style is violated is a
> waste of the resources.
>
> Why do you want to violate code style rules in your PR?
>
> I think instead of hiding style errors we should make our code style
> comfortable for everyone.
> Can you, please, write - what part o
Hello Maxim,
> Why do you think that splitting the checkstyle build is better option
than fixing code style issues reporting by the checkstyle plugin?
Why do you think that Ilya talks that code style errors should not be fixed?
It looks weird to me that we do not even start the tests if check
+1
Thanks,
S.
ср, 13 мая 2020 г. в 08:48, Nikolay Izhikov :
> +1
>
> ср, 13 мая 2020 г., 07:35 Alexey Zinoviev :
>
> > +1
> >
> > ср, 13 мая 2020 г., 5:52 Saikat Maitra :
> >
> > > +1
> > >
> > > Regards
> > > Saikat
> > >
> > > On Tue, 12 May 2020 at 7:03 PM, Denis Magda wrote:
> > >
> > > >
Hooray!
Congratulations, Taras! Well deserved, keep going!
Thanks,
S.
вт, 12 мая 2020 г. в 19:09, Dmitriy Pavlov :
> Hello Ignite Community,
>
>
>
> The Project Management Committee (PMC) for Apache Ignite has invited Taras
> Ledkov to become a committer and we are pleased to announce that he
Hi Maxim,
My congratulations!
Thanks,
S.
сб, 9 мая 2020 г. в 07:12, Denis Magda :
> Congrats, Maxim. Well deserved!
>
> -
> Denis
>
>
> On Thu, May 7, 2020 at 4:47 AM Dmitriy Pavlov wrote:
>
> > The Project Management Committee (PMC) for Apache Ignite
> >
> > has invited Maxim Muzafarov to
Hello Semyon,
This is a good and long-awaited improvement! Thank you for your efforts!
Thanks,
S.
вт, 12 мая 2020 г. в 15:11, Данилов Семён :
> Hello!
>
> I would like to propose moving /binary_meta and /marshaller folders to the
> PDS folder.
>
> Motivation: data, directly related to the
Hello,
+1 to remove this component or move it to a separate repository if someone
wants to maintain it.
In case the web console provides useful features, we should consider how to
add them to our command-line utilities, if possible.
Thanks,
Slava.
ср, 6 мая 2020 г. в 16:10, Nikolay Izhikov :
>
>:
> >>>
> >>> Hello!
> >>>
> >>> I suggest that it's one of the places where it could be put instead of
> >>> adding a new tool.
> >>>
> >>> Regards,
> >>> --
> >>> Ilya Kasnacheev
>
1 - 100 of 170 matches
Mail list logo
