+1
Thanks for taking this, Evgeniy.
> Still not completed wiki page with different issue filters is available
> through [2], plz actualize who considers responsible for this.
Please clarify - do you need help with this?
On Thu, Sep 18, 2025 at 6:44 PM zstan wrote:
>
> Dear Ignite Community!
>
Both issues should be fixed now
[1]
https://github.com/apache/ignite-website/commit/e77011dc6a267c6333562ebf6d4c336f2fc38c57
[2]
https://github.com/apache/ignite-website/commit/076efc077622a4b7b1c9a473b8a9acf8794f965c
On Thu, Aug 28, 2025 at 9:15 AM Pavel Tupitsyn wrote:
>
> Hi
Hi Maksim,
> 2. The "ignite-2" option on the main page leads to a non-existent page
Good catch, we'll fix it
> https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation
If "latest" points to 3.0.0, I'm not sure we can make 2.x links work.
In other words, I expect version-specific
> Little Endian architectures that are NOT
> included in the following list: "i386", "x86", "amd64", and "x86_64"
What are those, can you please provide examples?
On Wed, Jul 23, 2025 at 9:50 PM Aleksandr Polovtsev
wrote:
>
> Thank you, Ivan, for the detailed explanation.
> Do I understand corr
thub.com/dspavlov/ignite-abbrev-plugin
> [3] https://github.com/timoninmaxim/ignite-abbrev-plugin
> [4] https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules
> --
> Regards,
> Aleksandr Chesnokov
>
> пт, 18 июл. 2025 г. в 11:14, Pavel Tupitsyn :
>
> > Hello
Hello,
There is an ASF repo [1], why do we use a personal repo [2] for an ASF release?
[1] https://github.com/apache/ignite-abbrev-plugin
[2] https://github.com/timoninmaxim/ignite-abbrev-plugin
On Fri, Jul 18, 2025 at 10:32 AM Aleksandr Chesnokov
wrote:
>
> We are pleased to announce the relea
Hello Aditya,
I've added you to the Contributors group in JIRA, you should be able
to work on tickets now.
Welcome to the Apache Ignite community!
On Thu, Jul 17, 2025 at 3:22 PM wrote:
>
> Hello, Everyone!
>
> My name is Aditya Mukhopadhyay. I want to contribute to Ignite. I would
> like to st
+1 (binding)
On Mon, Jun 23, 2025 at 8:48 AM Andrey Novikov wrote:
>
> Dear Community,
> The release candidate is ready. See the links below.
>
> The release candidate is uploaded to:
> https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spark-ext-4.0.0-rc1/
>
> The following M
The only workflow with windows-2019 that I found in Ignite repos is [1]
Updated it to windows-2022
[1]
https://github.com/apache/ignite-python-thin-client/blob/master/.github/workflows/build_wheel.yml
On Tue, Jun 17, 2025 at 3:43 PM Andrew Wetmore wrote:
>
> Good day:
>
> Infra received this me
Igniters,
TeamCity server at https://ci.ignite.apache.org will be unavailable
for up to four hours starting at 12:00 UTC today for maintenance.
Hello Michael,
Welcome to the Apache Ignite community!
I've added you to the contributors group in JIRA, you should be able
to work on tickets now.
Pavel
On Thu, May 29, 2025 at 5:24 PM Michael Aglietti
wrote:
>
> Hello, Everyone!
>
> My name is Michael Aglietti. I want to contribute to Ignite
Ok, I've merged it, thank you.
On Mon, Apr 28, 2025 at 1:37 PM Niall Pemberton
wrote:
>
> On Mon, 28 Apr 2025 at 11:29, Pavel Tupitsyn wrote:
>
> > Hi Niall,
> >
> > Can't review 90K files, is it a rebuild or just plain automated removal?
> >
>
>
Hi Niall,
Can't review 90K files, is it a rebuild or just plain automated removal?
On Mon, Apr 28, 2025 at 11:37 AM Niall Pemberton
wrote:
>
> Hi Ignite Devs,
>
> Could someone take a look at the PR #207 to remove Google & Yandex from old
> versions in the "releases" directory:
> https://git
Igniters,
Please have a look at the .NET Platform Compute proposal for Ignite 3
and let me know what you think.
https://cwiki.apache.org/confluence/display/IGNITE/IEP-136+Platform+Compute
Hello Daria, I've added you to the Contributors group in JIRA, you
should be able to work on tickets now.
Welcome to the Apache Ignite community!
On Mon, Feb 24, 2025 at 11:53 AM jinxxxoid wrote:
>
> Hello, team
>
> My name is Daria and I'd like to start contributing to the Apache Ignite
> doc a
Igniters,
The ASF published a press release on Ignite 3.0 today:
https://news.apache.org/foundation/entry/the-apache-software-foundation-announces-apache-ignite-3-0
...and there is a new blog post from Stanislav Lukyanov:
https://ignite.apache.org/blog/whats-new-in-apache-ignite-3-0
P.S. A remin
Igniters,
I invite you to join Ignite Summit 2025 that will take place live, online
next Tuesday, Feb 25, starting at 7am PST / 10am EST / 3pm UTC.
With over 8 hours of speaking sessions from community members, Ignite power
users, and top contributors, you can join for any portion of the event, o
+1 (binding)
Checked node startup, NuGet packages, .NET examples
On Wed, Feb 12, 2025 at 2:51 PM Dmitriy Pavlov wrote:
> +1
>
> Started a server node ver. 2.17.0#20250209-sha1:d53d4540
> Checked license, notes, release notes.
>
>
> Nocite in the root of distribution seems to have outdated year
corresponding resources.
Please let us know if you encounter any problems:
https://ignite.apache.org/our-community.html#faq
Regards,
Pavel Tupitsyn on behalf of the Apache Ignite community.
For now, "latest" [1] points to 2.x (same with Docker latest tag [2]).
For the docs, there is a separate Ignite 2 / Ignite 3 combobox on top to
avoid mixing major versions.
I agree that we need a clear separation. Maybe two dedicated website
sections and an explanation that 2.x and 3.x are both ac
It took some time to finalize things (artifacts, docs, website) - I'll
announce the release on Monday (Feb 10).
On Wed, Feb 5, 2025 at 11:28 AM Pavel Tupitsyn wrote:
> Igniters,
>
> The release of Apache Ignite 3.0.0 rc1 has been accepted.
>
> The vote PASSES with
> 8 +1
;
> > > > > > +1 (binding)
> > > > > >
> > > > > > On Fri, Jan 31, 2025 at 1:02 PM Вячеслав Коптилин
> > > > > > wrote:
> > > > > > >
> > > > > > > +1 (binding)
> > >
Igniters,
The release of Apache Ignite 3.0.0 rc1 has been accepted.
The vote PASSES with
8 +1 votes (4 binding),
no 0 votes,
and no -1 votes.
+1 votes:
Aleksandr Polovtsev
Vyacheslav Koptilin (binding)
Andrey Gura (binding)
Mikhail Pochatkin
Andrey Novikov (binding)
Igor Sapego (binding)
Andrey
Igniters,
3.0.0-rc1 release candidate is ready:
https://dist.apache.org/repos/dist/dev/ignite/3.0.0-rc1/
Maven staging:
https://repository.apache.org/content/repositories/orgapacheignite-1571
Tag 3.0.0-rc1:
https://github.com/apache/ignite-3/releases/tag/3.0.0-rc1
This is the first release of A
We have to cancel the vote. A few critical issues have been identified:
IGNITE-24351 .NET: Apache.Extensions.Caching.Ignite package is missing in
release build artifacts
IGNITE-24352 Packaging: ODBC rpm building is broken
IGNITE-24356 Thin 3.0: Features and extensions handling is inconsistent
IGNI
gt; >
> > > > Best Regards,
> > > > Igor
> > > >
> > > >
> > > > On Tue, Jan 28, 2025 at 7:12 PM Mikhail Pochatkin <
> > > m.a.pochat...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > &g
Igniters,
3.0.0-rc0 release candidate is ready:
https://dist.apache.org/repos/dist/dev/ignite/3.0.0-rc0/
Maven staging:
https://repository.apache.org/content/repositories/orgapacheignite-1570/
Tag 3.0.0-rc0:
https://github.com/apache/ignite-3/releases/tag/3.0.0-rc0
This is the first release of
+1
Started server node, tried .NET examples, checked NuGet packages.
On Fri, Jan 24, 2025 at 3:11 AM Yujue Li <18624049...@163.com> wrote:
> +1
>
> Start an ignite server node with ignite-calcite and ignite-log4j2 and
> ignite-rest-http and ignite-json module enabled on Linux 6.12 and JDK
> 17/2
day.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-24053
>
>
>
> вт, 21 янв. 2025 г. в 20:28, Pavel Tupitsyn :
>
> > Following an in-person discussion with Vladimir Pligin and Alexander
> Lapin,
> > we concluded that Metastorage Compaction can require up to 3 weeks to
&g
Following an in-person discussion with Vladimir Pligin and Alexander Lapin,
we concluded that Metastorage Compaction can require up to 3 weeks to
complete.
As a result, it should be postponed to ensure the release of version 3.0
before the Ignite Summit.
Metastorage Compaction is an important feat
n 3.0, let me know in
this thread.
On Tue, Jan 14, 2025 at 12:12 PM Pavel Tupitsyn
wrote:
> Metastorage compaction takes more time than expected
> (IGNITE-23280, IGNITE-23466), and we have a lot of small fixes coming every
> day.
>
> Proposal:
> - Move code freeze to Jan 20 (ne
I'll post an update
> > tomorrow.
> >
> > On Mon, Jan 13, 2025 at 6:15 PM Mikhail Pochatkin <
> m.a.pochat...@gmail.com
> > >
> > wrote:
> >
> > > Hi, guys. I have fixed a bug in CLI with incorrect SQL exception
> handling
> > > (IGNITE-2417
g in CLI with incorrect SQL exception handling
> (IGNITE-24179). Any objections to merge it before code freeze?
>
> пн, 13 янв. 2025 г. в 08:45, Pavel Tupitsyn :
>
> > > Found a very nasty error IGNITE-24186, I think it's worth adding, since
> > we might not be able to
> Found a very nasty error IGNITE-24186, I think it's worth adding, since
we might not be able to restart the cluster.
Kirill, are you going to work on this? Any ETA?
> worth adding this performance fix into the scope IGNITE-24163
Already done and cherry-picked, nice.
On Sun, Jan 12, 2025 at 1
ols has been
>> found recently:
>>
>> [1] - https://issues.apache.org/jira/browse/IGNITE-24159
>>
>> I'd suggest including it into the release scope.
>>
>> пн, 16 дек. 2024 г. в 11:18, Pavel Tupitsyn :
>>
>> > RO TX timeouts [1] and related tasks
apache.org/jira/browse/IGNITE-24159
>
> I'd suggest including it into the release scope.
>
> пн, 16 дек. 2024 г. в 11:18, Pavel Tupitsyn :
>
> > RO TX timeouts [1] and related tasks are still in the works.
> > Moving the dates again:
> >
> > Scope Freeze:
I think it is a great idea.
We can use Continuous Query to keep the local entries up to date. I've seen
this approach in some real-world Ignite-based applications.
Note that we have .NET Platform Cache [1] which is quite similar, but works
on thick clients and embedded servers only.
[1] https://i
Hello Matthias,
- I've added you to the Contributors group in JIRA, you should be able to
work on tickets now.
- Please note the "ignite-3" label on tickets, those are about
https://github.com/apache/ignite-3 repo.
- Flaky test fixes are always welcome and there are always quite a few of
them.
We
2024 at 3:37 PM Pavel Tupitsyn wrote:
> Mikhail, thank you for taking the initiative.
>
> I agree with the Kotlin DSL direction.
>
> > slowdown in indexing in the developers' projects
>
> IDEA can exclude a folder from indexing [1] - should be an easy workaround.
>
Mikhail, thank you for taking the initiative.
I agree with the Kotlin DSL direction.
> slowdown in indexing in the developers' projects
IDEA can exclude a folder from indexing [1] - should be an easy workaround.
[1] https://www.jetbrains.com/help/idea/indexing.html
On Fri, Dec 20, 2024 at 2:22
Igniters,
Currently, our TeamCity projects [1] are UI-defined and are the same for
all branches.
Which has the following issues:
- Can't test project changes in a branch without risking broken main
- Can't have different settings for different branches (e.g. SDK upgrade in
a new version only)
- Di
Pavel Tupitsyn wrote:
> There are still 5 important unresolved tasks, moving the dates again.
> Considering various holidays across the globe nearing the end of the year:
>
> Scope Freeze: December 16, 2024
> Code Freeze: December 23, 2024
> Voting Date: January 6, 2025
> Rel
; Maksim Myskov
>
> > On 3 Dec 2024, at 17:13, Pavel Tupitsyn wrote:
> >
> >> adding the "ignite.bootstrap.nodeName" property to define the node that
> > performs cluster initialization on startup
> >
> > Why node name and not a boolean flag?
> &g
mode” section, please take a look.
> > In short, I propose adding the "ignite.bootstrap.nodeName" property to
> define the node that performs cluster initialization on startup.
> > I look forward to receiving feedback on this approach.
> >
> > --
> > Maksim Myskov
> &
Hello Maksim,
The proposal looks good in general.
I think we need more details on cluster initialization mechanism - who
calls init and when? What if there are multiple Spring-based embedded nodes?
On Fri, Nov 22, 2024 at 1:36 PM Maksim Myskov wrote:
> Hello Ignite devs,
>
> Please, take a loo
chev 写道:
> > Hello, Igniters.
> >
> > I have created the 2.17 release page [1].
> >
> > As a reminder, on the scope freeze, issues that are not ready for
> > merging will be moved to the next release.
> >
> > Please, feel free to write if some issues are c
I prefer the "same repo" approach - a lot easier to manage.
Let's keep things simple unless there is a very good reason to have a
separate repo.
On Wed, Nov 20, 2024 at 11:51 AM Maksim Myskov wrote:
> Hi Ignite devs,
>
> I’d like to raise a question regarding the location of future Spring Boot
>
mands? How does it work with GridClient? Invoke by class name?
>
> See CommandsProvider. Yes, they are invoked by the class name.
>
> On Mon, Nov 11, 2024 at 8:15 AM Pavel Tupitsyn
> wrote:
> >
> > Nikita,
> >
> > I see two issues:
> > - Changing the default beha
:34 AM Pavel Tupitsyn wrote:
> Metastorage Compaction and some other important tickets [1] are still
> unresolved. Let's postpone the release further.
>
> Proposed dates:
> Scope Freeze: November 11, 2024
> Code Freeze: November 18, 2024
> Voting Date: November 25, 2024
&
+1
2.16 was released almost a year ago, some users are worried about the lack
of updates
On Tue, Nov 12, 2024 at 11:07 PM Maxim Muzafarov wrote:
> +1
>
> On Tue, 12 Nov 2024 at 18:41, Nikita Amelchev
> wrote:
> >
> > Dear Ignite Community!
> >
> > I suggest starting Apache Ignite 2.17 release
ath that inherits from the management task class.
> This is necessary for pluggable commands - in Ignite extensions and
> plugins.
>
> In any case, to avoid security issues it seems the user should
> configure an explicit security plugin - which has the functionality
> needed for this
I agree with the proposal in general, but this part is concerning:
> Change the default parameter -
ThinClientConfiguration#setMaxActiveComputeTasksPerConnection (enable tasks
execution by default)
This might become a security issue.
As a user, I might want to disable thin client compute tasks bu
e.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Themostimportantreleasetasks
On Fri, Oct 4, 2024 at 3:59 PM Pavel Tupitsyn wrote:
> Thanks Vladimir, this ticket is already tracked as a requirement for the
> release [1]
> I'll keep an eye on the progress an
ry YCSB benchmark results added to the release page [1]
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Benchmarks
> >
> > On Fri, Sep 13, 2024 at 10:09 AM Pavel Tupitsyn
> > wrote:
> >
>
Hello Aleksandr, I've added you to the Contributors group in JIRA, you
should be able to work on tickets now.
Welcome to the Apache Ignite community!
On Tue, Oct 1, 2024 at 6:41 PM Александр Чесноков
wrote:
> Hello, Everyone!
> My name is Aleksandr. I want to contribute to Ignite. I would like
Preliminary YCSB benchmark results added to the release page [1]
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=318606750#ApacheIgnite3.0.0-Benchmarks
On Fri, Sep 13, 2024 at 10:09 AM Pavel Tupitsyn
wrote:
> I agree that the tickets listed above are important for
in
> > > 3-4 weeks.
> > >
> > > [1] - https://issues.apache.org/jira/browse/IGNITE-22719
> > > [2] - https://issues.apache.org/jira/browse/IGNITE-22740
> > > [3] - https://issues.apache.org/jira/browse/IGNITE-22744
> > > [4] - https://issues.apache
e.org/jira/issues/?jql=project%3Dignite%20and%20fixVersion%3D3.0.0-beta2%20
On Fri, Aug 30, 2024 at 8:13 PM Maxim Muzafarov wrote:
> +1!
>
> On Fri, 30 Aug 2024 at 18:52, Stephen Darlington
> wrote:
> >
> > +1
> >
> > Fab milestone!
> >
> >
2022 -> 2024, of course :)
On Thu, Aug 29, 2024 at 1:50 PM Pavel Tupitsyn wrote:
> Dear Ignite Community!
>
> I suggest starting Apache Ignite 3.0.0 release activities.
>
> beta1 was released almost 2 years ago, and the product has matured greatly
> since then.
> -
Dear Ignite Community!
I suggest starting Apache Ignite 3.0.0 release activities.
beta1 was released almost 2 years ago, and the product has matured greatly
since then.
- The public API is stable
- Performance is greatly improved [1]
- More than 2000 tickets resolved [2]
I would like to be the r
+1
On Tue, Jul 16, 2024 at 10:14 AM Zhenya Stanilovsky
wrote:
>
> Great !
> +1
>
> >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
Hello Tim,
I've added you to the Contributors group in JIRA, you should be able to
work on tickets now.
Welcome to the Apache Ignite community!
Note that the tickets above have ignite-3 label - see
https://github.com/apache/ignite-3 repo
Welcome to the Apache Ignite community!
Pavel
On Fri, Ju
Hello Matvei,
I've added you to the Contributors group in JIRA, you should be able to
work on issues now.
Welcome to the Apache Ignite community!
On Tue, Jul 9, 2024 at 4:39 PM Матвей Калистратов
wrote:
> Hello, Everyone!
>
> My name is Matvei Kalistratov. I want to contribute to Ignite. I woul
Hello Ivan,
I've added you to the Contributors role in JIRA, you should be able to work
on tickets now.
Welcome to the Apache Ignite community!
On Thu, Jun 13, 2024 at 2:31 PM Ivan Artiukhov wrote:
> Hello Igniters!
>
> I'd like to contribute to Apache Ignite. I want to take the following
> ti
I'm sorry, I missed the approval email. The account is now created, and
contributors permissions granted.
Welcome to the Apache Ignite community!
On Fri, May 31, 2024 at 10:46 AM Pavel Tupitsyn
wrote:
> Hello Stas, a JIRA profile with the specified name does not seem to exist:
Hello Stas, a JIRA profile with the specified name does not seem to exist:
https://issues.apache.org/jira/secure/ViewProfile.jspa?name=stasmarkin
On Thu, May 30, 2024 at 5:35 PM Stas Markin wrote:
> Hello, Everyone!
> My name is Stanislav Markin. I want to contribute to Ignite. I would like
> to
Mikhail, could you please use JIRA labels to link tickets to IEPs?
- Add iep-xxx label to tickets
- Use "JIRA" macro in Confluence with "labels=iep-xxx" filter
On Thu, May 16, 2024 at 10:43 AM Mikhail Pochatkin
wrote:
> Igniters,
>
> Please review the proposal [1] and let me know what you think
Hello Maxim,
I've added you to the Contributors role in JIRA, you should be able to work
on tickets now.
Welcome to the Apache Ignite community!
On Wed, May 15, 2024 at 12:15 PM Maxim Myskov
wrote:
> Hello Ignite devs,
>
> Could you please add me to contributors group of Apache ignite project
uch unwanted mails
> > in my inbox from ignite Apache mails
> >
> > On Tue, May 7, 2024 at 10:35 PM Pavel Tupitsyn
> wrote:
> >
> > > > In case of such response we need some new
> > > > error code to distinguish entry processor exceptions and general
> In case of such response we need some new
> error code to distinguish entry processor exceptions and general
client/server exceptions.
I don't think we do this anywhere else (e.g. Compute).
Full stack trace should be present in the server logs, or sent back to the
client when sendServerException
process. This should enable better productivity.
Roman, congratulations on your new role!
Pavel Tupitsyn
on behalf of Apache Ignite PMC
process. This should enable better productivity.
Mikhail, congratulations on your new role!
Pavel Tupitsyn
on behalf of Apache Ignite PMC
Hello Tiago,
Welcome to the Apache Ignite community!
I've added you to the Contributors group in Jira, you should be able to
work with tickets now.
On Tue, May 7, 2024 at 7:12 PM Tiago Godinho wrote:
> Hello, Everyone!
>
> My name is Tiago. I want to contribute to Ignite. I would like to
> sta
we
> should reflect that in its type/parameter name?
> 4. Can you please elaborate on the "deploymentUnits" parameter? Are these
> the units that contain the receiver classes? Can you please reflect that in
> the documentation?
> 5. It would be nice to have an example of a
Igniters,
Please review the proposal [1] and let me know what you think
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-121%3A+Data+Streamer+with+Receiver
Hello Nusrat,
Welcome to the Apache Ignite community!
I've added you to the contributors group in JIRA, you should be able to
work on tickets now.
Pavel
On Wed, Apr 24, 2024 at 1:07 PM Nusrat Shakarov wrote:
> Hello Ignite Community!
>
> My name is Nusrat. I want to contribute to Apache Ignite
- I think we should have separate lists for test and non-test dependencies.
Non-test list should be a lot more strict
- Created a ticket to remove unused jackson-dataformat-msgpack [1]
[1] https://issues.apache.org/jira/browse/IGNITE-22030
On Thu, Apr 11, 2024 at 2:36 PM Vadim Kolodin wrote:
>
Congratulations Iurii!
On Wed, Feb 14, 2024 at 8:17 AM Roman Puchkovskiy <
roman.puchkovs...@gmail.com> wrote:
> Congratulations!
>
> вт, 13 февр. 2024 г. в 23:51, Dmitriy Pavlov :
> >
> > Dear Igniters,
> >
> > The Project Management Committee (PMC) for Apache Ignite
> > has invited Iurii Gerzhe
Could you please clarify:
- Does this proposal affect the user in any way?
- Does it introduce or remove functionality?
- Does it affect compatibility?
As I understand, all the answers are NO, and this is only a refactoring -
correct? Let's make this clear in the IEP
P.S. Separate IEP naming for
+1
- Started the node from binaries
- Tested .NET examples
- Tested NuGet packages
On Sun, Dec 17, 2023 at 2:48 PM Nikita Amelchev
wrote:
> Dear Community,
>
> The release candidate is ready.
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.16.0-rc0
> h
r IEP is fresh?
> >
> > чт, 26 окт. 2023 г. в 14:05, Vladimir Steshin :
> >> All right. Pavel, thank you.
> >>
> >> IEP:
> >>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-110+Thin+Client+Service+Awareness
> >>
> &g
- Client continue service requesting and misses instance node forever
> > or often.
> >
> > If we provide, for example, version or hash of client topology version
> > in every service call request, we always get actual service topology
> > just by comparing on server si
Sounds good, new JDK support seems to be in demand.
On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov wrote:
> +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 accumulate
ge event preceedes service redeployment and service
> mapping change? There a possibility for client to save new topology version
> before services are actually redeployed. If we rely on actual change of the
> service mapping (redeployment), there is no such problem.
>
> On 17.10.202
rvice is being
> requested. Or you think this is not significant?
>
>
> On 17.10.2023 11:13, Pavel Tupitsyn wrote:
> > Hi Vladimir,
> >
> > 1. A topology of a deployed service can change only when the cluster
> > topology changes.
> > 2. We already have a
Hi Vladimir,
1. A topology of a deployed service can change only when the cluster
topology changes.
2. We already have a topology change flag in every server response.
Therefore, the client can request the topology once per service, and
refresh it when cluster topology changes, right?
On Mon, O
Congrats, Stephen!
On Mon, Sep 4, 2023 at 12:52 PM Вячеслав Коптилин
wrote:
> 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，Zhan
- Changes merged
- ARM64 tags pushed to Docker hub for Ignite 2.15
- Release Process document updated
Thanks!
On Sat, Aug 19, 2023 at 4:06 PM Andrey Gura wrote:
> Looks good to me. No objections at all.
>
> Thanks a lot, Pavel!
>
> On Fri, Aug 18, 2023 at 2:30 PM Pavel Tu
Congratulations, Aleksandr! Well deserved!
On Mon, Aug 21, 2023 at 8:01 AM Kseniya Romanova
wrote:
> Igniters!
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Aleksandr
> Polovtsev to become a committer and we are pleased to announce that he has
> accepted.
>
> Alexand
Igniters,
I've added another Dockerfile for ARM64 (to support native execution on
Apple Silicon, AWS Graviton, etc).
This will require another command in section 6.3.9 of Release Process [2]
Ideally, we could publish a multi-arch image [1] under a single tag,
however, this would require switchin
Does it have any outstanding issues? A stable and useful module should not
be removed just because it does not evolve.
On Wed, Aug 9, 2023 at 1:46 PM Ivan Daschinsky wrote:
> Igniters, seems that this module is completely abandoned for more than 2
> years. But it is enormous and it seems that no
Igniters,
I propose to remove the artificial port range limitation
from ClientConfiguration (checked in TcpClientChannel#validateConfiguration
[1]) - it does not seem to be useful, and can be a problem for certain use
cases (e.g. TestContainers [2]).
Any objections?
[1]
https://github.com/apach
Approved with a suggestion
On Thu, Jul 6, 2023 at 4:27 PM Maksim Timonin
wrote:
> Hi Pavel,
>
> Could you please make a review?
>
> https://github.com/apache/ignite-website/pull/169/files
>
> Thanks!
>
> Maksim
>
> On Thu, Jul 6, 2023 at 12:48 PM Pavel T
Hi Maksim,
Yes, please go ahead with the release notes patch.
My bad - I forgot to update them even though it was mentioned in the ticket.
Note that ClientConfiguration#setAutoBinaryConfigurationEnabled provides a
way to revert to the old behavior.
Thank you,
Pavel
On Thu, Jul 6, 2023 at 11:42
Igniters,
I've added the "All async methods should have async suffix" rule to Ignite
3 style guide [1]
Reason:
- when both sync and async variants exist, async suffix is required for the
code to compile, because the only difference is return value type
- when only async variant exists, we want to
Hi Steven,
This is Apache Ignite dev list, for for Apache Kafka please follow
https://kafka.apache.org/contributing
On Thu, Jun 8, 2023 at 11:35 AM Steven Booke wrote:
> To whom this may concern,
>
> I am requesting contributors' permissions so that I may make my first
> contribution to the apa
gnment could be used for accessing the
> data.
> Regards,Colin.
>
> On Tuesday, 23 May 2023 at 11:48:55 BST, Pavel Tupitsyn <
> ptupit...@apache.org> wrote:
>
> Igniters,
>
> Please review Ignite 3.x Data Streamer proposal
>
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-102%3A+Data+Streamer
>
Basic streamer in Java client is ready for review:
https://issues.apache.org/jira/browse/IGNITE-19540
https://github.com/apache/ignite-3/pull/2128
On Tue, May 23, 2023 at 1:48 PM Pavel Tupitsyn wrote:
> Igniters,
>
> Please review Ignite 3.x Data Streamer proposal
>
> https://c
Igniters,
Please review Ignite 3.x Data Streamer proposal
https://cwiki.apache.org/confluence/display/IGNITE/IEP-102%3A+Data+Streamer
+1 (binding)
Downloaded binaries, tested node startup, NuGet packages, .NET examples.
On Wed, Apr 26, 2023 at 10:52 PM Alex Plehanov
wrote:
> Dear Community,
>
> The release candidate is ready.
>
> I have uploaded release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.15.0-rc0/
1 - 100 of 1108 matches
Mail list logo
