Hi, please use 'user list' to ask the questions.
But in this case, I can recomend you to check GC logs. It seems, for some
reason, you have huge GC pauses.
On Sat, Mar 9, 2024 at 12:08 PM Kalwakuntla, Srinivas
wrote:
> Dear Ignite Team,
>
> Hope this email finds your well !
>
> Reaching out to
Mikhail, as we discussed earlier, Ignite-3 should use it's own counters
since it's a different project.
Better case for me is to use I3EP-XX naming.
Nikolay, +1 to your proposal.
On Thu, Feb 8, 2024 at 6:57 PM Mikhail Pochatkin
wrote:
> Hello, Nikolay.
>
> Thanks for your IEP. I would say that
+1, LGTM
On Tue, Jan 30, 2024 at 11:36 PM Nikita Amelchev
wrote:
> Hello, Vladimir.
>
> Thanks for the IEP. I have reviewed the proposal, good plan. Let's
> implement this.
>
> ср, 17 янв. 2024 г. в 18:48, Vladimir Steshin :
> >
> > Hi, Igniters! I'd like to propose a new feature - Custom
Great job, Ivan!
On Mon, Jan 29, 2024 at 12:02 PM Ivan Daschinsky
wrote:
> All parsers also have been uploaded to maven central:
>
> https://central.sonatype.com/artifact/org.apache.ignite/ignite-ml-ext/dependents
>
> пн, 29 янв. 2024 г. в 12:00, Ivan Daschinsky :
>
> > The Apache Ignite
+1
Вс, 24 дек. 2023 г. в 15:19, Николай Ижиков :
> +1 (binding)
>
> Отправлено с iPhone
>
> > 24 дек. 2023 г., в 00:13, Ivan Daschinsky
> написал(а):
> >
> > +1 from me (binding)
> >
> > 1. Checked checksums
> > 2. Checked C++/ODBC driver: built from source and ran examples on Ubuntu
> >
Welcome aboard :)
On Wed, Nov 22, 2023 at 2:11 PM Maxim Muzafarov wrote:
> My congratulations, Nikita!
>
> On Tue, 21 Nov 2023 at 15:20, Dmitriy Pavlov wrote:
> >
> > Hello Igniters,
> >
> > The Project Management Committee (PMC) for Apache Ignite
> > has invited Nikita Amelchev to become a
. Drop old physical logging implementation if (1) has no critical
> issues after some time.
> 3. Or implement logical and physical records split, if critical issues
> found in (1).
> In this case, we proceed to the alternative approach only if the main
> approach fails.
>
> чт, 9
opinion, it's better to keep both
> approaches and allow users to configure it. We should keep both
> approaches at least for a one release after the new approach will be
> enabled by default. In case of a critical problem users can raise the
> issue and switch to the old approach.
>
Sounds good to me, except the compatibility proposal.
No need to keep the old behaviour. Noone will update the node after the
crash.
Update must happen only after the plain node stop, let's just check this
instead of groving the code complexity.
On Thu, Nov 2, 2023 at 4:55 PM Alex Plehanov
25 авг. 2023 г. в 12:13, Ivan Daschinsky :
> > >
> > > > +1. It's time to do it at last.
> > > >
> > > > пт, 25 авг. 2023 г. в 12:06, Peter Ivanov :
> > > >
> > > > > Mostly, yes.
> > > > >
> > > > > In othe
+1
On Sun, Oct 22, 2023 at 12:29 PM Nikita Amelchev
wrote:
> Dear Ignite Community!
>
> I suggest starting Apache Ignite 2.16 release activities.
>
> We've accumulated a hundred resolved [1] issues with new features and
> bug fixes which are waiting for their release date. For example:
>
>
ted
>
>
> чт, 28 сент. 2023 г. в 14:12, Ivan Daschinsky :
>
> > No, I just think that we should remove 1 yaml file unless the sonar check
> > is not properly configured.
> >
> > чт, 28 сент. 2023 г. в 14:09, Anton Vinogradov :
> >
> >> Ivan,
&
at 1:57 PM Anton Vinogradov wrote:
> > Sonar shows lots of false positives.
> Thats not a true.
> We have a *bad* code, unfortunatelly, and that's the *reason* of such
> hints.
> Could you please show "a lot" of false positives?
> The url you provided contains a lot of
to ignoring of all checks. Simply nobody pay
> attention to them. It is not acceptable and contradicts to
> the idea of running these checks.
>
> чт, 28 сент. 2023 г. в 13:43, Anton Vinogradov :
>
> > Removing a quality tool it not a good idea.
> > AFAIU, we have two issue
Removing a quality tool it not a good idea.
AFAIU, we have two issues here:
1) Sonar always failed at PR because ot token issues
Error: Failed to execute goal
org.sonarsource.scanner.maven:sonar-maven-plugin:3.9.1.2184:sonar
(default-cli) on project apache-ignite: Project not found. Please check
a/browse/IGNITE-13871 which is assigned to
> you. Is it required to delegate?
>
> Best regards,
> S.
>
> ср, 23 авг. 2023 г. в 19:05, Anton Vinogradov :
>
> > MVCC test/suites removal PR was merged.
> >
> > Slava,
> > > I think it would be nice to cl
I looks like you're proposing not migration to 2.11 (because it is already
supported), but Java 8-9 support dropping.
On Fri, Aug 25, 2023 at 11:54 AM Peter Ivanov wrote:
> Hi, Igniters!
>
>
> I would like to propose the next, if you don't mind me saying,
> revolutionary step forward in our
RDER%20BY%20%20priority%20DESC%2C%20updated%20DESC
>
> WDYT?
>
> Thanks,
> Slava.
>
> вт, 22 авг. 2023 г. в 22:03, Anton Vinogradov :
>
> > Going to merge on green visa obtaining if there are no objections.
> >
> > On Tue, Aug 22, 2023 at 6:47 PM Anto
Going to merge on green visa obtaining if there are no objections.
On Tue, Aug 22, 2023 at 6:47 PM Anton Vinogradov wrote:
> MVCC test/suites removal PR [1] is almost ready, fixing final failures.
>
> Does anybody ready to review the PR?
>
> I've rechecked each modified line
MVCC test/suites removal PR [1] is almost ready, fixing final failures.
Does anybody ready to review the PR?
I've rechecked each modified line before pushing the commit button, is this
enough?
[1] https://github.com/apache/ignite/pull/10900
On Thu, Aug 17, 2023 at 1:18 PM Anton Vinogradov
Great, starting the removal.
On Wed, Aug 16, 2023 at 5:35 PM Ivan Daschinsky wrote:
> The plan looks good to me. Some of the tests are in the ODBC test suite, so
> i can help if needed.
>
> ср, 16 авг. 2023 г. в 16:32, Anton Vinogradov :
>
> > Igniters,
> >
> >
Igniters,
I started the TX code cleanup [1] last month and almost finished with the
obvious garbage.
Now, started the code deduplication, I was faced with code overcomplexity
because of unfinished MVCC.
The community agreed to remove MVCC, but the initial attempt [2] was not
successful because
+1 to relocation
On Wed, Aug 9, 2023 at 3:09 PM Alex Plehanov
wrote:
> Pavel, do you know anyone who uses it?
>
> Looks like it isn't used at all (no questions on mail lists, no
> tickets), but we spend developers time to build module with every
> Ignite rebuild, we spend users traffic to
ucer for thread unsafe behavior, which causes data
> inconsistency ?
> AFAIK all required parts of txn processing are already properly linearized,
> and other parts are ready to be processed in parallel (like txn recovery)
>
> пн, 19 июн. 2023 г. в 22:25, Anton Vinogradov :
>
&
24, 2023 at 4:11 PM Anton Vinogradov wrote:
> >> could you please point to this at code, it may be not needed after the
> fix and can bring the performance growth.
> BTW, found the trick.
> Still necessary to keep copying.
>
> On Wed, May 24, 2023 at 2:44 PM Anton Vinogr
>> could you please point to this at code, it may be not needed after the
fix and can bring the performance growth.
BTW, found the trick.
Still necessary to keep copying.
On Wed, May 24, 2023 at 2:44 PM Anton Vinogradov wrote:
> Andrey,
>
> Thanks for the tip.
> Of cour
> Tx processing is supposed to be thread bound by hashing the version to
> a
> > > partition, see methods like [1]
> > > If for some cases this invariant is broken, this should be fixed.
> > >
> > > [1]
> > >
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDh
)
at
org.apache.ignite.internal.processors.cache.transactions.TxMultiCacheAsyncOpsTest.testCommitAfterAsyncGet(TxMultiCacheAsyncOpsTest.java:121)
Such code generates/fills non-threadsafe collections which will be used at
the striped pool later.
Should we always create/modify transactions at the striped pool threads?
On Fri, May 19, 2023 at 8:29 PM Anton Vinogradov wrote
; Tx processing is supposed to be thread bound by hashing the version to a
> > partition, see methods like [1]
> > If for some cases this invariant is broken, this should be fixed.
> >
> > [1]
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareReque
Igniters,
My team was faced with node failure [1] because of non-threadsafe
collections usage.
IgniteTxStateImpl's fields
- activeCacheIds
- txMap
are not thread safe, but are widely used from different threads without the
proper sync.
The main question is ... why?
According to the research,
Igniters,
GridSslContextFactory is deprecated since 2015, and it's time to get rid of
it (including Public API).
I've prepared the patch [1] and going to merge it on wednesday.
Any objections?
[1] https://issues.apache.org/jira/browse/IGNITE-19339
Done
On Wed, Mar 15, 2023 at 4:07 PM Виталий Виноградов
wrote:
> Hi,
>
> I'm Vitaliy Vinogradov, a technical writer. I want to update documentation
> for Ignite on regular basis. Therefore I need to create tickets in Jira.
>
> Please grant me permission for this.
>
> My login at ASF: vitavin
>
Hi,
Not sure if we released 1.8.3 or 1.9.3 ever, but you may find older
releases at https://archive.apache.org/dist/ignite/
On Tue, Mar 7, 2023 at 2:55 PM Orishkevich
wrote:
> Good evening!
> I really need to find apache-ignite-fabric-1.8.3-bin.zip and
> apache-ignite-fabric-1.9.3-bin.zip.
> I
+1
On Tue, Nov 15, 2022 at 11:25 AM Ilya Shishkov
wrote:
> Hi,
>
> +1 from me.
>
> Checked out pyignite-0.6.0.zip with
> pyignite-0.6.0-cp310-cp310-win_amd64.whl:
> 1. Whl package installed via pip.
> 2. All examples tested (with supplied docker-compose.yml).
> 3. SHA512 hashes checked for both
Great news!
Welcome aboard
On Fri, Nov 11, 2022 at 12:03 PM Nikita Amelchev
wrote:
> My congratulations, Mikhail!
>
> пт, 11 нояб. 2022 г. в 11:55, Maksim Timonin :
> >
> > Hi Mikhail! Congratulations!
> >
> > On Fri, Nov 11, 2022 at 11:30 AM Vladimir Steshin
> > wrote:
> >
> > > Mikhail,
think marking the issue as 'important' and filling out the release
> >>> notes field is enough to get the attention of a release manager.
> >>>
> >>> вт, 18 окт. 2022 г. в 20:26, Maksim Timonin :
> >>>>
> >>>> Hi guys,
> >>
Ok, let's do this.
And schedule the fix to the 2.16.
On Mon, Oct 17, 2022 at 7:42 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> By placing the @Deprecated annotation on the property.
>
> пн, 17 окт. 2022 г. в 19:07, Anton Vinogradov :
>
> &
t looks fine to me.
>
> пн, 17 окт. 2022 г. в 15:50, Anton Vinogradov :
>
> > We MUST break this, of course!
> > Atomic operations inside the transaction is a wrong and unexpected
> > behaviour and MUST be restricted for every user.
> >
> > On Mon, Oct 17, 202
We MUST break this, of course!
Atomic operations inside the transaction is a wrong and unexpected
behaviour and MUST be restricted for every user.
On Mon, Oct 17, 2022 at 3:05 PM Julia Bakulina
wrote:
> Hi Team,
>
> I have found this ticket https://issues.apache.org/jira/browse/IGNITE-8801 -
>
Welcome aboard!
On Sat, Sep 17, 2022 at 11:14 PM Pavel Pereslegin wrote:
> Great news!
> Congratulations, Ivan!
>
> сб, 17 сент. 2022 г. в 16:33, Dmitriy Pavlov :
> >
> > Hi Igniters!
> >
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Ivan Daschinsky to become a
Hi,
Is it possible to share old/new hardware specs, or at least the difference?
Will it become faster?
On Wed, Sep 14, 2022 at 4:14 PM Petr Ivanov wrote:
> Dear community,
>
>
> TeamCity 1 (ci.ignite.apache.org) is moving to the new hardware.
> Effective immediately the queue will be paused,
Looks great!
On Wed, Sep 7, 2022 at 2:57 PM Nikita Amelchev wrote:
> Pavel, Looks cool.
>
> +1 to add to the default log config.
>
> вт, 6 сент. 2022 г. в 13:20, Pavel Tupitsyn :
> >
> > Thanks for the explanation.
> >
> > Yes, I think we can apply the same color scheme everywhere, but let's
>
It looks like we need to mention that we are talking about Ignite *3* only.
Same mention is required at IEP header.
On Mon, Aug 22, 2022 at 4:07 PM Mikhail Pochatkin
wrote:
> Hi Igniters,
>
> I want to start a voting process about several points from IEP-93 [1].
>
> 1. Switch Apache Ignite
> - Do we know the way how orphaned pages sneaks into index.bin?
Could this be because of nodes crashes and restarts?
Looks like we have no failovers to restore indices after the crash.
On Mon, Jun 20, 2022 at 10:47 PM Николай Ижиков wrote:
> Hello Igniters.
>
> We have very useful
+1
On Fri, May 13, 2022 at 12:59 PM Николай Ижиков wrote:
> +1
>
> > 13 мая 2022 г., в 12:53, Maxim Muzafarov написал(а):
> >
> > Dear Community,
> >
> >
> > The release candidates are ready.
> >
> > The ignite-zookeeper-ip-finder and ignite-spring-session haven't been
> > changed since the
+1
On Fri, Apr 29, 2022 at 5:28 PM Maxim Muzafarov wrote:
> Dear Community,
>
>
> The release candidates are ready. See the links below.
>
>
> == Ignite Spring Data Extension Module 2.2.0 ==
>
> The release candidate is uploaded to:
>
>
+1
On Fri, Apr 29, 2022 at 3:48 PM Maxim Muzafarov wrote:
> Dear Community,
>
>
> The release candidates are ready. See the links below.
>
>
> == Ignite AWS Extension Module 1.0.0 ==
>
> The release candidate is uploaded to:
>
>
+1
On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков wrote:
> +1
>
> > 26 апр. 2022 г., в 16:24, Maxim Muzafarov
> написал(а):
> >
> > Hello Igniters,
> >
> >
> > Currently we have a batch of ignite-hibernate modules which provide
> > Hibernate second-level cache (L2 cache) implementation based
>
> > > I've prepared the pull request [1] and have plans to merge it to the
> > > master branch in about two weeks, if there is no objection.
> > >
> > > [1]: https://github.com/apache/ignite/pull/9855
> > >
> > > чт, 30 дек. 2021 г. в 13:43, A
According to Infra [1], issue is solved.
Please check.
[1] https://issues.apache.org/jira/browse/INFRA-22827
On Wed, Feb 9, 2022 at 3:27 PM Anton Vinogradov wrote:
> Created the issue [1] to solve the problem of broken checks we already
> have because of non-guaranted checks by
ee.
> We should update or workaround known security issues ASAP.
>
>
> > Not every deployment requires to use of log4j.
>
>
>
> Agree, but we shouldn’t provide or support modules with known security
> issues.
>
>
> > 28 февр. 2022 г., в 18:41, Anton Vinogradov
Your deployment has vulnerabilities only in case you configured log4j as a
logger.
Not every deployment require to be secured.
Not every deployment requires to use of log4j.
We must change the default logging library if the current is log4j and
provide the ability to use log4j as before (where it
ced 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 фев
ame ok?
>
> On Mon, Feb 21, 2022 at 12:29 PM Anton Vinogradov wrote:
>
> > Alexander,
> >
> > Could you please specify (at IEP's name) this IEP is related to the
> Ignite
> > 3 (only)?
> >
> > On Tue, Feb 15, 2022 at 3:28 PM Alexander Polovtcev <
&
Andrey,
Could we create a separate and explicit IGNITE-3 project at confluence for
Ignite 3 wikis?
On Mon, Feb 14, 2022 at 9:21 AM Andrey Gura wrote:
> Igniters,
>
> The new wiki section for Apache Ignite 3 contributors is created. This
> page [1] is the main entry point for new and existing
Alexander,
Could you please specify (at IEP's name) this IEP is related to the Ignite
3 (only)?
On Tue, Feb 15, 2022 at 3:28 PM Alexander Polovtcev
wrote:
> Hello, dear Igniters!
>
> We've prepared an IEP
> <
>
> I «vote» for more frequent releases.
+1
Hotfixes, eg. 2.12.1, should be released asap (no need to wait for 2.13).
And it's ok to release 2.13 without fixes planned for 2.12.1 since not all
users are affected but some wait for features like "Consistency check &
repair".
On Thu, Feb 10, 2022
Created the issue [1] to solve the problem of broken checks we already have
because of non-guaranted checks by Travis.
https://issues.apache.org/jira/browse/IGNITE-16508
Folks,
Let's vote for the issue [1], I wish this may help to solve the problem
faster.
[1] https://issues.apache.org/jira/browse/INFRA-22827
On Fri, Feb 4, 2022 at 2:31 PM Anton Vinogradov wrote:
> >> Should I add this info for the INFRA ticket?
> Please do
>
> On Fri, Feb
/builds/245860409
>
>
>
> On Wed, Feb 2, 2022 at 5:42 PM Anton Vinogradov wrote:
>
> > Asked the INFRA [1]
> >
> > [1] https://issues.apache.org/jira/browse/INFRA-22827
> >
> > On Wed, Feb 2, 2022 at 5:29 PM Anton Vinogradov wrote:
> >
>
Asked the INFRA [1]
[1] https://issues.apache.org/jira/browse/INFRA-22827
On Wed, Feb 2, 2022 at 5:29 PM Anton Vinogradov wrote:
> Igniters,
>
> Seems the Travis service is not working properly.
> For example, it never checked my PR [1], any ideas why?
>
> Who knows how
Igniters,
Seems the Travis service is not working properly.
For example, it never checked my PR [1], any ideas why?
Who knows how to fix it?
[1] https://github.com/apache/ignite/pull/9661
+1 to option 4
On Thu, Jan 13, 2022 at 5:15 PM Pavel Tupitsyn wrote:
> +1 to option 2
>
> On Thu, Jan 13, 2022 at 3:52 PM Roman Puchkovskiy <
> roman.puchkovs...@gmail.com> wrote:
>
> > +1 to option 2
> >
> > чт, 13 янв. 2022 г. в 15:58, Sergey :
> > >
> > > +1 for option2 (only @Nullable)
> >
+1
On Tue, Jan 11, 2022 at 11:35 AM Maxim Muzafarov wrote:
> +1
>
> On Tue, 11 Jan 2022 at 11:31, Nikolay Izhikov wrote:
> >
> > +1
> >
> > > 11 янв. 2022 г., в 02:38, Vladimir Steshin
> написал(а):
> > >
> > > +1
> > >
> > > 10.01.2022 15:52, Nikita Amelchev пишет:
> > >> Dear Community,
> >
> it would be great to release a new SQL engine in 2.13 as an
experimental feature.
++1
On Thu, Dec 30, 2021 at 12:55 PM Alex Plehanov
wrote:
> Andrey,
>
> > Is this [1] a full scope of the tickets that MUST be resolved before the
> engine could be merged?
> Yes, we must resolve at least these
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 it!
> >
> > ср, 22 дек. 2021 г. в 20:40, Andrey Mashenkov <
> andrey.mashen...@gmail.com>:
> >
> >>
Sergei,
Please make sure this will not break the Ducktests.
AFAIK, we have zookeeper tests there.
On Wed, Dec 22, 2021 at 12:09 PM Sergei Ryzhov
wrote:
> Hi, igniters,
>
> I've created an issue [1] to move the zookeeper IP-finder to the
> ignite-extensions. The motivation is the same as with
ous vulnerability and it is
> recommended to update log4j asap.
>
> пн, 20 дек. 2021 г. в 14:00, Anton Vinogradov :
>
> > Maxim,
> > Look like an issue is not related to security problems we fix.
> > Any reason to cancel the vote (delay release) to include this bugfix?
Maxim,
Look like an issue is not related to security problems we fix.
Any reason to cancel the vote (delay release) to include this bugfix?
On Mon, Dec 20, 2021 at 1:28 PM Maxim Muzafarov wrote:
> Cancelling the vote.
>
> I'll cherry-pick the following [1] to the release branch and prepare a
>
of single project.
>
>
> > On 17 Dec 2021, at 15:14, Anton Vinogradov wrote:
> >
> > Petr,
> >
> >> I strongly suggest avoiding a separate repository for project settings.
> >> Let's store them in https://github.com/apache/ignite
> >
> > Sou
Petr,
> I strongly suggest avoiding a separate repository for project settings.
> Let's store them in https://github.com/apache/ignite
Sounds good, but we must avoid dozens of additional commits in this case.
Each commit should be properly formalized and related to the issue.
We may create a
Thanks for the update!
On Thu, Dec 16, 2021 at 9:07 PM Виталий Осилов
wrote:
> Hi!
> TeamCity server https://ci2.ignite.apache.org/ will be unavailable on
> Friday 17.12 from 22:00 MSK to 00:00 MSK
> Works will be done to synchronize the TeamCity configuration
> https://ci2.ignite.apache.org/
Folks,
My 200 rubles here,
> I want to include it to the 2.12 scope.
Why not 2.11.1 as well?
We should provide a fixed version for current customers asap.
2.12 require migration, while 2.11.1 can be applied as-is.
On Mon, Dec 13, 2021 at 12:18 PM Stephen Darlington <
Anton, I disagree.
> >
> >1. This should be released with main distro.
> >2. This should not be abandoned.
> >3. There is not any release process in ignite-extensions.
> >4. Everything is working now and working good.
> >
> >
> >So lets
Let's move all GCC-related parts to ignite-extensions, release, and use
them as a maven dependency.
On Fri, Dec 3, 2021 at 1:08 PM Ivan Daschinsky wrote:
> Ok, TC suite is ready [1].
> If there is no objections, I will merge it soon.
>
> Possible concerns -- now it is required to install
> What is the issue if third-party plugins will create «ignite-sys-cache»
from the code?
Great idea!
On Fri, Dec 3, 2021 at 2:15 PM Nikolay Izhikov wrote:
> Vyacheslav, Val, can you please clarify - What is the issue if third-party
> plugins will create «ignite-sys-cache» from the code?
>
>
Welcome aboard!
On Wed, Dec 1, 2021 at 12:30 PM Вячеслав Коптилин
wrote:
> 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!
Folks,
Could we have a kick-off call to determine the roadmap?
On Thu, Oct 21, 2021 at 6:52 PM Denis Magda wrote:
> Folks, you don't need me on that call. I'm of a little value/help here.
>
> -
> Denis
>
>
> On Thu, Oct 21, 2021 at 9:51 AM Nikolay Izhikov
> wrote:
>
> > Hello, Igniters.
> >
>
My -0 here, since the is no automated RC preparation and testing at Apache
TeamCity again.
Next time, I will vote with -1 if a new vote is not covered by public
automated preparation/testing as the AI release does.
On Wed, Oct 27, 2021 at 11:48 AM Nikita Amelchev
wrote:
> Dear Ignite Community,
+1
On Fri, Oct 15, 2021 at 3:41 PM Nikita Amelchev
wrote:
> +1 for deprecation in the 2.12 release
>
> пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov :
> >
> > Hello, Igniters.
> >
> > I’ve prepared IEP-80 [1] to track breaking changes that should be done
> in Ignite 2.x.
> >
> > We agreed on the
> 1. What is expected behaviour if an old thin client requests creation of
> LOCAL cache on the newest ignite cluster?
Unsupported operation exception.
> 2. Should we completely remove LOCAL caches support in thin clients (i.e.
pyignite) before 2.13 release?
Removal should happen at 2.13.
On
My regards!
On Thu, Aug 19, 2021 at 1:11 PM andrei wrote:
> Congrats, Petr!
>
> 8/19/2021 1:00 PM, Andrey Mashenkov пишет:
> > Congrats, Petr!
> >
> > On Thu, Aug 19, 2021 at 12:58 PM Dmitry Pavlov
> wrote:
> >
> >> Hello Ignite community,
> >>
> >> The Project Management Committee (PMC) for
> I think TC config should be stored in the same repo as the corresponding
> code (2.x config in 2.x repo, 3.x in 3.x, etc).
This will kill repo history.
You'll see dozens of TC config updates vs a single Ignite fix
> it would be great to be able to test them by simply creating a new branch
> in
+1 to keeping the dev list clean.
On Mon, Aug 9, 2021 at 11:00 AM Pavel Tupitsyn wrote:
> I agree, let's keep the dev list clean.
> Automated notifications of any kind should not be sent to dev@i.a.o.
>
> PS Ivan, links 2 and 3 are the same.
>
> On Mon, Aug 9, 2021 at 8:54 AM Ivan Pavlukhin
Great news!
Wish you good luck with this undertaking!
P.s. ci2.i.a.o sounds good to me.
On Tue, Aug 3, 2021 at 7:36 PM Petr Ivanov wrote:
> Seems that preserving and syncing users will be difficult to achieve —
> that info is stored in DB, and partial DB replication is tricky.
>
> Also
Congrats!
On Fri, Jul 30, 2021 at 10:19 AM ткаленко кирилл
wrote:
> Zhenya, congratulations!
>
> Пересылаемое сообщение
> 30.07.2021, 09:50, "Ivan Daschinsky" :
>
>
> Zhenya, congrats, well deserved!
>
> пт, 30 июл. 2021 г. в 00:44, Andrey Mashenkov >:
>
> > Congratulations
Folks, seems we MUST automate such a check, as well as the whole
extension release process before the next release attempt?
We may (must?) use AI release automation as a booster.
Please let me know if any help required.
On Tue, Jun 29, 2021 at 11:59 AM Ilya Kasnacheev
wrote:
> Hello!
>
> -1
-authored-by: Dmitriy Sorokin
Co-authored-by: emvdovets
On Mon, Jun 28, 2021 at 6:01 PM Anton Vinogradov wrote:
> Seems, we have a silent agreement here :)
> We also discussed the proposal with the Ignite QA Meetup participants and
> found this contribution useful.
>
> Going to
Seems, we have a silent agreement here :)
We also discussed the proposal with the Ignite QA Meetup participants and
found this contribution useful.
Going to merge tomorrow, if there are no objections.
On Mon, Jun 28, 2021 at 3:21 PM Anton Vinogradov wrote:
> With regard to the request of I
Folks, we already have Ignite release semi-automated at TeamCity.
We able to assembly, publish as RC and check published.
Seems, we must do the same at extensions.
This way we'll check issues like this even before starting the vote.
On Mon, Jun 28, 2021 at 2:14 PM Ilya Kasnacheev
wrote:
>
> --
> > Denis
> >
> > -
> > Denis
> >
> > On Thu, Jun 24, 2021 at 3:43 AM Anton Vinogradov wrote:
> >
> >> Denis,
> >>
> >> Unfortunately, we had some issues with this recording (low slides
> recording
> >> reso
Summit and wonder if you should share that recording with an
> English-speaking part of the community?
>
> -
> Denis
>
> On Wed, Jun 23, 2021 at 7:37 AM Anton Vinogradov wrote:
>
> > Folks,
> >
> > Here's the video [1] that explains the proposal in detail.
> >
Folks,
Here's the video [1] that explains the proposal in detail.
Feel free to ask questions here.
[1] https://www.youtube.com/watch?v=f-i9COU5uAQ (in Russian)
On Tue, Jun 8, 2021 at 2:51 PM Anton Vinogradov wrote:
> Igniters,
> Let me present a framework, we developed, that allows auto
;>> Konstantin, thanks for chiming in.
> >>>>>>>>
> >>>>>>>> That's exactly my concern. Overformalization is generally not a
> good
> >>>>>>>> thing.
> >>>>>>>> Someone used "mes
Igniters,
Let me present a framework, we developed, that allows automating Apache
Ignite testing on a real cluster.
The framework was initially presented at Ignite Summit.
In brief,
The framework allows automating operations with any applications on a real
cluster using ssh in a form of a python
-1 here.
We can fix the code and set up the rule.
This will help to prevent having a weird abbreviation like "mess" (from
"message") or "ign" (from "Ignite").
Also, the abbreviations list (hardcoded at IDEA plugin) allows to have same
names across the whole code, this should simplify the reading.
Anton Vinogradov created IGNITE-14622:
-
Summary: Snapshot test simplification
Key: IGNITE-14622
URL: https://issues.apache.org/jira/browse/IGNITE-14622
Project: Ignite
Issue Type: Sub
Anton Vinogradov created IGNITE-14618:
-
Summary: Increase stop timeout to 60 seconds
Key: IGNITE-14618
URL: https://issues.apache.org/jira/browse/IGNITE-14618
Project: Ignite
Issue Type
Anton Vinogradov created IGNITE-14601:
-
Summary: Specs should use service's params instead of copying.
Key: IGNITE-14601
URL: https://issues.apache.org/jira/browse/IGNITE-14601
Project: Ignite
Also checked the hashcode generation
>> from pyignite import _cutils
>> print(_cutils.hashcode('test'))
>> 3556498
On Mon, Apr 19, 2021 at 11:01 AM Anton Vinogradov wrote:
> Checked the installation from sources.
> +1
>
> On Sat, Apr 17, 2021 at 7:47 PM Ivan Das
1 - 100 of 874 matches
Mail list logo
