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
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
>
at 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 receiver implementation
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
- 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
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
>
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
ontinue 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 side. Indepe
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
ent 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.2023 13:
eing
> 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 topology c
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,
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
> >
> > > 在
- 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.
>
>
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
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
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]
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
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
t 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/
Erlan, thank you, looks great!
Two suggestions:
- There is no easy way to get back to the main Blog page once you click on
an article - can we add a link somewhere?
- Let's replace "Blogging in Action" header/title with "Apache Ignite Blog"
On Wed, Apr 26, 2023 at 2:39 PM Kseniya Romanova
Alex,
Just in case, Bugyard credentials are available to all PMCs in the private
SVN repo, see [1]
> a lot of changes from 'ignite' to 'gridgain'
That's not good, requested changes on that PR.
[1]
+1
On Thu, Mar 30, 2023 at 2:08 AM Ilya Kasnacheev
wrote:
> +1!
> --
> Ilya Kasnacheev
>
>
> ср, 29 мар. 2023 г. в 23:13, Vladimir Steshin :
>
> > +1
> >
> > 29.03.2023 21:56, Alex Plehanov пишет:
> > > Dear Ignite Community!
> > >
> > > I suggest starting Apache Ignite 2.15 release activities.
t; summarizes
> some knowledge on force pushes
> Gael.
>
>
>
>
> On Mon, 27 Mar 2023 at 03:31, Pavel Tupitsyn wrote:
>
> > Nikolay, to avoid expensive mistakes.
> > We don't need force pushes or merge commits, it is easy to disallow them,
> > so why not?
> >
Nikolay, to avoid expensive mistakes.
We don't need force pushes or merge commits, it is easy to disallow them,
so why not?
On Mon, Mar 27, 2023 at 1:24 PM Николай Ижиков wrote:
> Hello, Pavel.
>
> Why do we need any new restrictions?
>
> > 27 марта 2023 г., в 12:32, Pavel Tup
Mirza, yes, I've created a ticket for ignite-3 as well:
https://issues.apache.org/jira/browse/IGNITE-19122
On Mon, Mar 27, 2023 at 12:27 PM Mirza Aliev wrote:
> Thanks! Nice idea!
>
> I wonder if this changes work for ignite-3 repo as well?
>
> пн, 27 мар. 2023 г. в 12:47,
Igniters,
I'm going to enable master branch protection:
- Disallow force push (dangerous)
- Disallow merge commits (against our workflow)
Any objections?
[1] https://github.com/apache/ignite/pull/10608
[2] https://issues.apache.org/jira/browse/IGNITE-19123
Hi Gael, I've added your JIRA account to the Ignite project.
Welcome to the community!
On Fri, Mar 17, 2023 at 7:21 PM Gael Yimen Yimga
wrote:
> Hello Kseniya,
>
> My JIRA account is : yimengael
> My email address is : yimeng...@gmail.com
>
> Gael.
> --
>
>
>
>
> On Fri, 17 Mar 2023 at 05:24,
The design looks great!
What about some kind of a date-based navigation panel to the right, under
the tags list?
Pavel
On Thu, Mar 16, 2023 at 1:42 AM Mauricio Stekl wrote:
> Hey, these plans for the blog migration and other updates look awesome! If
> you need any help or assistance along the
Well deserved! Welcome, Alexander!
On Thu, Feb 23, 2023 at 3:08 PM Kseniya Romanova
wrote:
> The Project Management Committee (PMC) for Apache Ignite has invited
> Alexander Pakhomov to to become a committer and we are pleased to announce
> that he has accepted.
>
> Alexander recently completed
+1 (binding)
On Wed, Feb 15, 2023 at 11:07 AM Vladimir Steshin
wrote:
> + 1
>
> 15.02.2023 11: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
> >
> >
Hello,
JIRA account 'dzabotlin' has been created, please check your email (
dvzabot...@gmail.com) to activate it.
Welcome to the Apache Ignite community!
On Tue, Feb 14, 2023 at 1:06 PM Dmitrii Zabotlin
wrote:
> Hello,
>
> I want to contribute to Apache Ignite, could you please make a
sults for IN Query combined with other clauses
>
> Answered this question.
>
> On Mon, Feb 6, 2023 at 9:46 AM Pavel Tupitsyn
> wrote:
>
>> Igniters, please have a look at open GitHub issues, some of them require
>> attention:
>>
>> IndexQuery retur
Igniters, please have a look at open GitHub issues, some of them require
attention:
IndexQuery returns wrong results for IN Query combined with other clauses
· https://github.com/apache/ignite/issues/10515
SqlFieldQueries with partitions on Calcite ·
Hi Kamalesh,
You can try this one from Ignite 3:
Add 'contains' method to Record API
https://issues.apache.org/jira/browse/IGNITE-15889
On Sun, Jan 22, 2023 at 2:01 PM kamalesh palanisamy
wrote:
> Hi Ilya,
> I think I will contribute to Ignite 3. Can you point to an issue related to
> this
t; > the set of addresses with the same (minimal) port? This will cover most
> of
> > the production cases, since several nodes on the same host can mostly be
> > found in test environments.
> >
> > пт, 20 янв. 2023 г. в 09:43, Pavel Tupitsyn :
> >
> > >
Alex, I agree with proposals 2 and 3.
However, IGNITE-15807 is not about random server, it is about random port
on the same server.
As I understand, the scenario is: we know that the server is at address
a.b.c.d,
but we are not sure which port will be chosen,
because ClientConnectorConfiguration
Hi Roman,
Done - I've added permissions to add, edit, and comment on Ignite space in
Confluence
On Thu, Jan 5, 2023 at 3:48 PM Roman Puchkovskiy <
roman.puchkovs...@gmail.com> wrote:
> Hi Igniters!
>
> I would like to contribute by commenting on Confluence pages (namely,
> I would like to add
Hello Maksim,
I've added you to the Jira project.
Welcome to the Apache Ignite community!
On Mon, Jan 2, 2023 at 12:00 PM Maksim Zhuravkov
wrote:
> Hello,
>
> I would like to start working on the following issue
> https://issues.apache.org/jira/browse/IGNITE-17972
> I have an access to Apache
Agree with the proposal.
Those properties go into config files (json/hocon), and it is difficult to
navigate to relevant docs from there.
I would go with point 3 - longer suffixes like Millis - to make it
unambiguous.
On Fri, Dec 23, 2022 at 10:06 AM Roman Puchkovskiy <
Hello Venkatesh,
I have created a JIRA account for you, please check your email (
venkatesh_kan...@outlook.com).
Also have a look at our contribution guidelines:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
Welcome to the Apache Ignite community!
Pavel
On Wed, Dec 14,
Hi Jian Chen, welcome to the Apache Ignite community!
I've added user chenjian2664 to Contributors role, you should be able to
work on tickets now.
Regarding JIRA full name - looks like it can't be changed (I can't even
change my own).
On Tue, Dec 13, 2022 at 11:20 AM Jian Chen wrote:
> Hi
+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:
> > >
> > > +1
> > >
> > > Checked compilation, ran some examples.
> > >
> > > пт, 9 дек.
Igniters,
Since ASF Infra recently disabled JIRA public signup for all projects (due
to spam), we (Ignite PMC) have enabled GitHub Issues for the Ignite project
at [1].
*This change does not affect contributors. The development process does not
change.*
GitHub issues replace JIRA *only for the
+1 (binding)
On Mon, Nov 14, 2022 at 9:05 PM Вячеслав Коптилин
wrote:
> 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:
Slava, Stan - thoughts?
I'll be glad to help with .NET, but what about missing sources and README
issues?
On Thu, Nov 10, 2022 at 4:00 PM Pavel Tupitsyn wrote:
> Stanislav,
>
> > Isn't nuget package enough for .NET ecosystem?
> Isn't Maven enough for the Java ecosystem? I would
for .NET ecosystem?
>
> Thanks,
> Stan
>
> > On 9 Nov 2022, at 19:55, Pavel Tupitsyn wrote:
> >
> > Also:
> > - Source code is missing (*src.zip files)
> > - .NET client binaries are missing in binary zips
> >
> > On Wed, Nov 9, 2022 at 7:51 PM Pavel
Also:
- Source code is missing (*src.zip files)
- .NET client binaries are missing in binary zips
On Wed, Nov 9, 2022 at 7:51 PM Pavel Tupitsyn wrote:
> -0.5 (binding)
>
> README.md contains a mix of "Alpha 5" and "Beta 1"
>
> On Wed, Nov 9, 2022 at 7:45 PM Вя
-0.5 (binding)
README.md contains a mix of "Alpha 5" and "Beta 1"
On Wed, Nov 9, 2022 at 7:45 PM Вячеслав Коптилин
wrote:
> 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
>
A small post about .NET changes:
https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.14/
Cheers!
On Tue, Oct 11, 2022 at 10:56 AM Taras Ledkov wrote:
> The Apache Ignite Community is pleased to announce the release of
> Apache Ignite 2.14.0.
>
> Apache Ignite® is an in-memory computing
Community!
Regards,
Pavel Tupitsyn
+1
On Sat, Oct 8, 2022 at 8:08 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> +1 Sounds good
>
> пт, 7 окт. 2022 г. в 18:07, Andrey Gura :
>
> > Hi, Igniters!
> >
> > It's time for a new release of Apache Ignite 3 beta 1. The expected
> > feature list consists of:
> >
> > - RPM
+1
Started .NET and Java nodes, checked examples, checked NuGet packages.
On Fri, Sep 30, 2022 at 4:07 PM Alex Plehanov
wrote:
> > Added new experimental, Apache Calcite based SQL engine
> It was added in 2.13, in 2.14 it became ignite-indexing (and H2)
> independent.
>
> +1
>
> Build from
Ready for review, any feedback is appreciated:
https://issues.apache.org/jira/browse/IGNITE-17725
On Tue, Sep 20, 2022 at 9:04 AM Pavel Tupitsyn wrote:
> Igniters, thanks for your input. I'll move on with the implementation.
>
> On Thu, Sep 15, 2022 at 6:46 PM Pavel Tupitsyn
Igniters, thanks for your input. I'll move on with the implementation.
On Thu, Sep 15, 2022 at 6:46 PM Pavel Tupitsyn wrote:
> Mirza,
>
> This is a good point.
>
> I assumed that assignment change is caused by a topology change, like in
> Ignite 2.x, and this affects all t
levant to that client
> as long as we cannot say which table's assignments were changed.
> Am I right in my assumption? If yes, it seems to me kinda inefficient to
> check assignments for all tables. WDYT?
>
>
> чт, 15 сент. 2022 г. в 11:07, Pavel Tupitsyn :
>
> > Igor,
>
> Regardless of the Tracking Assignment Changes section, I like the first
> approach
> the best. Yeah, idle clients do not get updates, but why would idle clients
> need
> assignment update anyway if they are idle?
>
> Best Regards,
> Igor
>
>
> On Thu
Igniters,
Please review the IEP for client partition awareness in Ignite 3 and let me
know what you think.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-95+Client+Partition+Awareness
[2] https://github.com/apache/ignite-3/pull/1080
is ok, apply the same logger pattern to the default
> production log4j-config,
> If you think it's worth applying them now to the production config - I
> can do it.
>
> вт, 6 сент. 2022 г. в 12:33, Pavel Tupitsyn :
> >
> > Looks great!
> >
> > However
Looks great!
However, I'm a bit confused - does it apply to node output in production
build?
Why does it say "test console output"?
On Tue, Sep 6, 2022 at 12:20 PM Mirza Aliev wrote:
> Hello Pavel! Looks awesome! Thank you for the enhancement!
>
> вт, 6 сент. 2022 г. в 10:37, Pavel Pereslegin
Congrats!
Pavel
On Sun, Aug 21, 2022 at 9:07 AM Ivan Pavlukhin wrote:
> Congratulations, Taras!
>
> Best regards,
> Ivan Pavlukhin
>
> сб, 20 авг. 2022 г. в 00:18, Dmitriy Pavlov :
> >
> > Hi Igniters!
> >
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Taras
Compute API requires code deployment, which may be an obstacle in some
cases.
But instead of withAffinityNode, I think we can add a new method to
IgniteClient:
public ClientTransactions transactions(ClusterGroup grp);
Similar to existing compute(ClusterGroup) and services(ClusterGroup)
methods.
The change looks good to me, good catch.
> I can create a new Jira ticket and pull request.
Please do, let's merge it.
On Thu, Aug 4, 2022 at 2:11 AM Arthur Naseef wrote:
> Testing with 60,000+ services, found that cancelling large numbers of
> services takes significant time. Found another
or java thin client). For other thin clients (except
> java) type id can be retrieved from the binary object and some key to
> partition mapper can be provided based on this type id (for example by
> configured factory).
>
> пн, 11 июл. 2022 г. в 16:22, Pavel Tupitsyn :
>
> >
; As I said earlier - It must be absolutely clear for user - PA works or
> not.
> > >
> > > With the logic you propose it will be hiding inside Ignite machinery
> and
> > > logs.
> > >
> > > > Unfortunately, this is a breaking change. Currently th
f
> java class can help my python or C++ client map key to partition.
>
> Max's proposal seems to be a good variant, just change naming a little bit,
> maybe
>
> пт, 8 июл. 2022 г., 15:35 Pavel Tupitsyn :
>
> > Nikolay,
> >
> > > Add ability to sent c
y can’t be
> instantiated on the client - throw an exception.
>
> WDYT?
>
> > 8 июля 2022 г., в 08:37, Pavel Tupitsyn
> написал(а):
> >
> > To clarify: you can use a different AffinityFunction implementation on
> the
> > client side. It just has to map to t
this should cover any use case.
On Thu, Jul 7, 2022 at 10:36 PM Pavel Tupitsyn wrote:
> AffinityKeyMapper is just a subset of AffinityFunction, isn't it?
> So by supporting AffinityFunction we cover all AffinityKeyMapper use cases.
>
>
> > managing the classpath, a user should a
ng/instantiating
> AffinityFunction. We can provide for a user a control on which channel
> (node) a particular cache request will be executed (this thing also
> have a drawback - a transactional operation cannot be executed on an
> arbitrary node, it should be executed on node it's start
ferent from the one that is on server
> doesn’t look good.
> > >
> > > I’d even go further and try sending the affinity function class itself
> over the network, so users won’t have to alter the classpath by adding the
> class that is not directly used in the codebase.
> &
> int applyAsInt(Object key, Integer parts);
> }
>
>
> I agree with you that "setPartitionAwarenessKeyMapper" may be is not
> good naming here, we can rename it and move it to the public API, of
> course.
>
> On Thu, 7 Jul 2022 at 20:06, Pavel Tupitsyn wrote:
> >
> > Maxim
issue with the
> partition awareness, but also specifies that the custom mapping
> function and deprecated AffinityKeyMapper should not be used, in
> general.
>
> Please, take a look at my patch:
>
> https://issues.apache.org/jira/browse/IGNITE-17316
> https://github.com/apache/ignite/pul
+1, seems like a good idea
On Thu, Jul 7, 2022 at 4:10 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:
> I’ve been thinking about the “first run” experience and some of the
> defaults we have.
>
> For example, I can start a thick client entirely with the defaults:
>
> var cfg =
I have no objections to extending the Thin Client configuration with a
pluggable Affinity Function.
Let's make it a normal Java setter though, system properties are hacky.
Especially when only some of the caches use custom affinity, as Maxim
mentioned.
On Wed, Jun 29, 2022 at 7:20 PM Николай
We can rename "Supplier delegate" to "next", like in ASP.NET Core
Middleware.
So it is clear that there is a chain of calls.
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/middleware/write?view=aspnetcore-6.0#middleware-class
On Wed, Jun 29, 2022 at 2:08 PM P
also seems to be more error prone from the user side. The user may
> > return a result of the wrong type for example. But I think this is ok,
> > so if there is no objection, I will update the IEP and prepare a patch
> > using the suggested approach.
> >
> > вт, 28 июн. 202
Hello Pavel,
The IEP looks good to me in general. It is a good addition to the service
API.
One suggestion is to improve control over service method execution within
the interceptor:
1. Bypass service call without throwing an exception.
2. Convert service call result in some way
This can be
Hi, you already have contributor permissions (JIRA username is
wkhapy123123):
https://lists.apache.org/thread/g2hlllxo7232yw1qh9wkhjrkf8mocc9j
On Tue, Jun 28, 2022 at 2:36 PM wkhapy...@gmail.com
wrote:
> Hi,
>
> I want to contribute to Apache ignite .
>
> Would you please give me the
Filed a ticket for Thin Client project timeouts. I'm on it.
testValidInvalidNodeAddressesMix test hangs, this happened before too, so
not related to Mikhail's changes.
https://issues.apache.org/jira/browse/IGNITE-17247
On Tue, Jun 28, 2022 at 8:53 AM wrote:
> Hi Igniters,
>
> I've detected
definitely
> > > easier to implement it properly.
> > >
> > > Pavel,
> > >
> > > Wow, that's really cool that you've already started working on it.
> > >
> > > Regarding your proposal I like it - it will really make a procedure
> > easier
> > > an
rsonally prefer the closeable iterator approach, since it is
> what
> > most Java libraries use and most users should be familiar with it. Also
> > most IDEs will warn you, if you don't close an AutoCloseable.
> >
> > On Fri, Jun 24, 2022 at 6:24 PM Pavel Tupitsyn
> &
Igniters,
I'm working on IgniteSet in Java thin client [1], and I'm not sure how to
deal with iterator release.
On the "thick" API side we use WeakReferenceCloseableIterator [2] to
release iterator resources automatically when the iterator instance is
claimed by GC.
a) Reuse this on the client
Hi,
I've added you to the Contributors group in JIRA.
Welcome to the Apache Ignite community!
On Fri, Jun 24, 2022 at 5:21 PM wkhapy...@gmail.com
wrote:
> Hi,
>
> I am interesting in ignite. I want to contribute to Apache ignite .
>
> Would you please give me the contributor permission?
>
>
Aleksey,
I fully support the idea of a common tuple format to avoid conversions when
passing data around (servers, clients).
The IEP looks good to me.
> Integer Field Compression
Agree with this, we can even extend the idea to float/double fields.
> size of table elements might be 1, 2, 4, or
+1 (binding)
On Fri, Jun 10, 2022 at 4:35 PM Igor Sapego wrote:
> +1
>
> Best Regards,
> Igor
>
>
> On Fri, Jun 10, 2022 at 1:37 AM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > +1
> >
> > On Thu, Jun 9, 2022 at 9:17 AM Alexander Polovtcev <
> > alexpolovt...@gmail.com>
>
question is - can we have the following version
> > committed in the source files 2.14.0.0, but when the 'release' profile
> > get activated (or probably the build happened) revision number will
> > changed to 2.14.0.62943? This will be the final release version ready
1 - 100 of 1753 matches
Mail list logo
