doSomething(tuple.floatValue("weight"))
>
> Whereas in other languages you could do it in one shot:
>
> if (tuple.TryGetFloatValue("weight", out var weight))
> doSomething(weight)
>
> or Option weight = tuple.floatValue("weight") and so on.
ized
> > as maps (String -> val).
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach#IEP54:SchemafirstApproach-Dynamicschemaexpansion(Live-schema)
> >
> > On Thu, Jul 1, 2021 at 8:31 PM Ivan Daschinsky
> > wrote:
gt;
> Out of curiosity, what would this code do if the value is NULL? What is the
> type of the 'weight' variable?
>
> if (tuple.TryGetFloatValue("weight", out var weight))
> doSomething(weight)
>
> -Val
>
> On Tue, Jul 6, 2021 at 2:13 AM Ivan Dasch
Valentin Kulichenko :
> So what happens if the value is NULL? Exception?
>
> -Val
>
> On Tue, Jul 6, 2021 at 1:52 PM Ivan Daschinsky
> wrote:
>
> > > Out of curiosity, what would this code do if the value is NULL? What is
> > the
> > type of the 'weigh
I'm sorry, but why we didn't consider to separate creation of Client and
connection? Why not to make async variant of connection? See for example [1]
[1] --- https://lettuce.io/core/release/api/index.html
чт, 8 июл. 2021 г., 09:50 Pavel Tupitsyn :
> Val,
>
> So the plan is:
>
> - Remove Ignition
://www.baeldung.com/java-redis-lettuce
чт, 8 июл. 2021 г., 23:47 Valentin Kulichenko :
> Ivan,
>
> Can you please clarify what you mean by "separate creation of client and
> connection"? Can you give an example?
>
> -Val
>
> On Thu, Jul 8, 2021 at 12:53 PM Ivan Daschinsky
&g
bootstrap/ServerBootstrap.html
> >
> > 2021-07-09 1:41 GMT+03:00, Valentin Kulichenko <
> > valentin.kuliche...@gmail.com>:
> > > Ivan,
> > >
> > > I've seen the link, but I still don't understand what exactly you
> propose
&
.get" and see a list of suggestions
> like get, getAsync, getAndPut, getAndPutAsync.
> I don't want to have a separate interface and a separate variable to deal
> with sync and async methods.
>
> Not sure what's the problem with documentation - can you elaborate please?
>
>
n, it works with CompletableFuture.
>
> On Fri, Jul 9, 2021 at 1:31 PM Ivan Daschinsky
> wrote:
>
> > You forget about reactive api :)
> >
> > And whats a problem with discocerability?
> >
> > var syncApi = client.sync();
> > syncApi.put(k, v);
> &
about "core library" as a primary set of modules that we
> > > ship.
> > > Integrations with 3rd party libraries and frameworks can be shipped as
> > > extensions.
> > >
> > > Anyway, let's postpone the discussion of Rx and Kotlin.
> >
e an example of that, a piece of code with suggested
> API usage? Ideally compared to the current 2.x approach.
>
> On Sat, Jul 10, 2021 at 3:20 PM Ivan Daschinsky
> wrote:
>
> > It is a quite questionable decision , as for me, to have specific static
> > method within
ll the corresponding benefits,
> like easy serialization.
> WebClient.Builder is an interface that does not even provide a way to get
> the property value back.
>
>
> To be clear, I don't have strong opinions on naming (it can be
> Ignition.start or IgniteClient.connect or w
1 июл. 2021 г., 17:48 Pavel Tupitsyn :
> Serialization is just one example, and it does not have to be XML.
> JSON, YAML, HOCON configs are widely used.
>
> Anyway, I see no reason for it NOT to be a POJO.
> POJOs are ergonomic and work everywhere.
>
>
> On Sun, Jul 11, 20
onomic and work everywhere.
>
>
> On Sun, Jul 11, 2021 at 8:24 AM Ivan Daschinsky
> wrote:
>
> > > But configuration should be a POJO - a class with setters and getters,
> > nothing else.
> > Why it should? Why ClientConfiguration should be serializable? Who needs
gt; why thin client should be in core module
> > > > >
> > > > > It will be in a separate module (ignite-client).
> > > > > I was talking about "core library" as a primary set of modules that
> > we
> > > > > ship.
> > > > >
Alexey, and is there any analogue to close() of transaction? When you start
transaction, you should somehow to close it, if you don't catch exception
or forget to commit.
I suggest to add method closeAsync() to Transaction, so user can call it in
handle or whenComplete, i.e.
So code will looks li
, I would keep tx API as small as possible for now.
> Anyway, these methods can be added later, if the need arises.
>
>
>
>
>
> ср, 14 июл. 2021 г. в 10:13, Ivan Daschinsky :
>
> > Alexey, and is there any analogue to close() of transaction? When you
> start
> > t
tent all table projections for better UX.
> > Let's allow
> > table.kvView().withTx(tx)
> > to user may cache kvVew instance and do
> > kvView.withTx(tx)
> > rather than
> > table.withTx(tx).kvVew()
> >
> >
> >
> > On Wed,
Hi, igniters!
Recently, one user asked me to add this functionality to pyignite.
Many users want:
1. To expose client metrics of app to prometheus (for example)
2. To write custom logic on specific client events (connect, disconnect,
reconnect)
3. To perform tracing
I suggests to introduce client
Igniters!
I suppose it is time to release pyignite 0.5.1. There are few good features
available and some users are eager to try it.
1. Added ability to record clients' events by event listeners. This is a
quite agile mechanism, and it allows writing custom metrics, tracing and
debugging.
2. Added
Hi!
Firstly, lets talk about interfaces.
1. First of all, do we have an automatic inspection for it? AFAIK we don't
2. I am for consistency. At least for production code. Nothing worse is
when someone mixes both approaches.
About a prohibition of curly brackets around one line -- I am strongly
a
+1 For current fix. Code is clean and understandable. I suppose that the
current fix is a correct variant to update heartbeatTs.
вт, 20 июл. 2021 г. в 16:13, Alex Plehanov :
> Hello, Ilya
>
> > But anyway, I propose to remove the update of the heartbeat from other
> threads altogether and wrap th
Since there is no any activity and contradiction, I decided to announce
code freeze now. Release candidates for voting will be available tomorrow
вт, 20 июл. 2021 г. в 09:45, Ivan Daschinsky :
> Igniters!
>
> I suppose it is time to release pyignite 0.5.1. There are few good
> featur
Branch for release --
https://github.com/apache/ignite-python-thin-client/tree/pyignite-0.5.1
Release notes --
https://github.com/apache/ignite-python-thin-client/blob/pyignite-0.5.1/RELEASE_NOTES.txt
чт, 22 июл. 2021 г. в 12:18, Ivan Daschinsky :
> Since there is no any activity
+1 for pony mail. It is a great tool with nice interface with zero ads
stuff.
чт, 22 июл. 2021 г. в 15:26, Dmitry Pavlov :
> Folks,
>
> My vote goes for ponymail. Actually it is a project under ASF itself, it
> is the part of Incubator.
>
> If we have a contributor who is aware about CEO setup, w
Dear Igniters!
Release candidate binaries for subj are uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.1-rc0
If you follow the link above, you will find source packages (*.tar.gz and
*.zip)
and binary packages (wheels) for windows (am
The voting finishes at 07/27/2021 12:00 UTC
пт, 23 июл. 2021 г. в 13:49, Ivan Daschinsky :
> Dear Igniters!
>
> Release candidate binaries for subj are uploaded and ready for vote
> You can find them here:
> https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.1-rc0
>
&
://downloads.apache.org/ignite/KEYS)
пт, 23 июл. 2021 г. в 13:52, Ivan Daschinsky :
> The voting finishes at 07/27/2021 12:00 UTC
>
> пт, 23 июл. 2021 г. в 13:49, Ivan Daschinsky :
>
>> Dear Igniters!
>>
>> Release candidate binaries for subj are uploaded and ready for
Hello, Igniters!
Release pyignite-0.5.1-rc0 has been accepted.
The votes received:
3 "+1" binding votes
1 "+1" votes
There are no "+0" or "-1"
Here the votes received:
- Igor Sapego (binding) +1
- Pavel Tupitsyn (binding) +1
- Nickolay Izhikov (binding) +1
- Ivan Daschinsky +1
oad sources and binary packages (wheels) from
here:
https://dist.apache.org/repos/dist/release/ignite/pyignite/0.5.1/
Please let us know if you have any problems
https://ignite.apache.org/community/resources.html#ask
Regards,
Ivan Daschinsky on behalf of the Apache Ignite community.
Zhenya, congrats, well deserved!
пт, 30 июл. 2021 г. в 00:44, Andrey Mashenkov :
> Congratulations Zhenya!
>
>
> On Fri, Jul 30, 2021 at 12:06 AM Maxim Muzafarov
> wrote:
>
> > The Project Management Committee (PMC) for Apache Ignite has invited
> > Zhenya Stanilovsky to become a committer and w
>> A user might want to use one more version.
Am I wrong, but user is supposed to use thin client in ignite 3? So why we
should care about guava since, frankly, it is not needed in thin client and
we can make it not dependent on guava at all?
чт, 5 авг. 2021 г. в 18:18, Alexander Polovtcev :
Hi, Dmitry. We also have released pyignite 0.5.1
пт, 6 авг. 2021 г. в 16:36, Dmitry Pavlov :
> Hi Igniters,
>
> It's time to submit ASF Board report, so, as usual, I encourage every
> community member to suggest some addition to that report.
>
> What was the most recognizable (releases, decisions
I suppose, that https://issues.apache.org/jira/browse/IGNITE-15274 is a
blocker.
Fix is quite easy and straightforward
пн, 2 авг. 2021 г. в 03:11, Igor Sapego :
> Cherry-picked to release branch.
>
> Best Regards,
> Igor
>
>
> On Fri, Jul 30, 2021 at 3:11 PM Alexey Gidaspov
> wrote:
>
> > Ok, I
Hi, I suppose that we should add javadoc to QuerySqlFileds. It is weird
that this feature is not documented.
ср, 11 авг. 2021 г. в 00:08, Maksim Timonin :
> Hi, Igniters!
>
> I dived to the precision param of QuerySqlField and SQL data types. The
> javadocs of QuerySqlField say that the param is
sues.apache.org/jira/browse/IGNITE-13364
>
> On Wed, Aug 11, 2021 at 1:12 PM Ivan Daschinsky
> wrote:
>
> > Hi, I suppose that we should add javadoc to QuerySqlFileds. It is weird
> > that this feature is not documented.
> >
> > ср, 11 авг. 2021 г. в 00:08, Mak
I'm sorry, but what about storing TC configs in separate repo?
It is quite common approach.
вт, 17 авг. 2021 г. в 17:33, Pavel Tupitsyn :
> Anton,
>
> > This will kill repo history.
> > You'll see dozens of TC config updates vs a single Ignite fix
>
> Not really.
> I'm not suggesting something cr
with this approach?
>
> On Tue, Aug 17, 2021 at 6:05 PM Ivan Daschinsky
> wrote:
>
> > I'm sorry, but what about storing TC configs in separate repo?
> > It is quite common approach.
> >
> > вт, 17 авг. 2021 г. в 17:33, Pavel Tupitsyn :
> >
> >
nown open-source project
> other than Ignite?
>
> Btw, I was always against moving thin clients into separate repos. Monorepo
> approach in some large companies is used for a reason.
> Dealing with multiple repositories is always hard.
>
>
> On Tue, Aug 17, 2021 at 6:23 PM
Hi. As for me, it is quite strange to make thin client dependent on third
party libraries like hocon parser and so on. What's the purpose of this?
сб, 21 авг. 2021 г., 13:32 Pavel Tupitsyn :
> Igniters,
>
> I'd like to discuss Java thin client configuration API in Ignite 3.0.
>
> On one hand, it
ith HOCON.
>
> On Sat, Aug 21, 2021 at 3:37 PM Ivan Daschinsky
> wrote:
>
> > Hi. As for me, it is quite strange to make thin client dependent on third
> > party libraries like hocon parser and so on. What's the purpose of this?
> >
> > сб, 21 авг. 2021 г
I am against to make user write index name. It is quite simple and
straightforward algorithm to match index to field names, so it is strange
to compare it to sql engine optimizer.
It is an usability nightmare to make user write index name in all cases.
чт, 26 авг. 2021 г., 14:42 Maksim Timonin :
IndexQuery<>(..)
> .setCriteria(lt("b", 1), lt("a", 2));
>
> On 26.08.2021 15:23, Ivan Daschinsky wrote:
> > I am against to make user write index name. It is quite simple and
> > straightforward algorithm to match index to field names, so it is s
To be honest, Pavel, your benchmark is not quite correct. Please, rewrite
it using BlackHole
чт, 9 сент. 2021 г. в 10:28, Nikolay Izhikov :
> +1 to ban Streams usage.
>
>
>
> > 9 сент. 2021 г., в 02:59, Valentin Kulichenko <
> valentin.kuliche...@gmail.com> написал(а):
> >
> > Pavel,
> >
> > Quit
.
So I am against a complete ban of streams, but I am for using this tool
with caution. Often streams make code ugly and non-readable at all.
чт, 9 сент. 2021 г. в 10:50, Ivan Daschinsky :
> To be honest, Pavel, your benchmark is not quite correct. Please, rewrite
> it using BlackHole
>
>> 2. In languages with proper async support (async-await, etc.), we can
skip sync API altogether.
It sounds pretty strange, as for me. Usually you cannot mix both functions
easily, it is called blue-red functions problem [1]
In python you definitely cannot do sync over async, for example
(principa
use sync API when async API should be used
> - when they really have to use sync API, potentially dangerous behavior is
> not hidden
>
>
> [1]
>
> https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclient?view=net-5.0#methods
> [2]
>
> https://devblo
avaScript: only async (sync is not possible)
>
> Thin clients in other languages are to be discussed.
>
> On Thu, Sep 9, 2021 at 11:49 AM Ivan Daschinsky
> wrote:
>
> > >> You can mix them easily.
> > This is far from easily (you have already mentioned continuatio
Hi, folks.
Unfortunately, a quite severe bug found in pyignite since 0.4.0 was found
[1]. Fortunately, it is already fixed. Also there are also a few bugs
already fixed.
I propose to prepare the next minor release. Branch was already cut and
commits were cherry-picked [3].
If there are no object
TC build of release branch --
https://tc.sbt-ignite-dev.ru/buildConfiguration/IgniteThinClients_Tests_ThinClientPython/6130289
чт, 9 сент. 2021 г. в 13:40, Ivan Daschinsky :
> Hi, folks.
>
> Unfortunately, a quite severe bug found in pyignite since 0.4.0 was found
> [1]. Fortun
x27;ve mentioned. Can not we solve it by
> using different thread pools for completion and continuation of futures or
> does
> CompletableFuture interface not allowing for that?
>
> Best Regards,
> Igor
>
>
> On Thu, Sep 9, 2021 at 1:15 PM Ivan Daschinsky
> wro
, Igor Sapego :
> +1
>
> Best Regards,
> Igor
>
>
> On Thu, Sep 9, 2021 at 8:33 PM Maxim Muzafarov wrote:
>
> > +1
> >
> > On Thu, 9 Sept 2021 at 14:08, Nikolay Izhikov
> wrote:
> > >
> > > +1 to release ASAP.
> &g
Dear Igniters!
Release candidate binaries for subj are uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.2-rc0
If you follow the link above, you will find source packages (*.tar.gz and
*.zip)
and binary packages (wheels) for windows (am
Hi, Maxim. And what is the plan of removing this functionality? And I also
have some questions regarding deprecation in binary protocol
Currently thin client binary protocol
1. Does support LOCAL caches
2. Does not support node filters.
I can hardly imagine the usefulness of this feature on thin
k them as deprecated.
>
> On Mon, 13 Sept 2021 at 11:29, Ivan Daschinsky
> wrote:
> >
> > Hi, Maxim. And what is the plan of removing this functionality? And I
> also
> > have some questions regarding deprecation in binary protocol
> >
> > Currently
e.
pyignite) before 2.13 release?
вт, 14 сент. 2021 г. в 10:11, Nikolay Izhikov :
> I proposed the following plan:
>
> 1. 2.12 - deprecation of LOCAL caches.
> 2. 2.13 - complete removal LOCAL caches from codebase.
>
> > 13 сент. 2021 г., в 13:30, Ivan Daschinsky
> напис
. -- passed
Checked hashsums and gpg signatures -- passed
пт, 10 сент. 2021 г. в 19:08, Ivan Daschinsky :
> Dear Igniters!
>
> Release candidate binaries for subj are uploaded and ready for vote
> You can find them here:
> https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.2
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 Tue, Sep 14, 2021 at 10:30 AM Ivan Daschinsky
> wrote:
>
&
not
PARTITIONED, so inconsistent behaviour from the beginning.
So I suppose we should ban creation of LOCAL caches from thin client in
2.12 (fail attempt to create such caches in ClientRequestHandler
вт, 14 сент. 2021 г. в 11:31, Ivan Daschinsky :
> >> Unsupported operation exception.
Николай Ижиков
> wrote:
>
> > +1
> >
> > Отправлено с iPhone
> >
> > > 14 сент. 2021 г., в 11:39, Pavel Tupitsyn
> > написал(а):
> > >
> > > +1
> > >
> > > Checked on Ubuntu 20.04, ran a few examples.
> > >
&
ing the creation of LOCAL
> caches without a warning through the code sounds not good. Will it be
> better to do everything in three steps (releases)? 2.12 deprecate,
> 2.13 forbid new cache creation, 2.14 remove.
>
> On Tue, 14 Sept 2021 at 12:09, Ivan Daschinsky
> wrote:
> >
Igniters!
Currently we have CMake build system, that works on Windows, Linux and
MacOs flawlessly
1. CMake is supported natively in VS 2019
2. CMake can generate VS projects for about 20 years flawlessly.
3. Sometimes even maintainers forget to add test sources to VS projects [1]
4. Currently on
>> This may become an obstacle for some of the users and I'm not sure how
it improves anything.
Please specify more correctly. What is an obstacle? Current VS projects
(odbc) cannot be build on VC 2015+
without modification. CMake is an industry standard now.
>> I'm not sure how it improves anythin
>> Please specify more correctly.
Sorry, typo, more concretely.
ср, 15 сент. 2021 г. в 12:22, Ivan Daschinsky :
> >> This may become an obstacle for some of the users and I'm not sure how
> it improves anything.
> Please specify more correctly. What is an obstacle? C
ll of them are present in VS files
> Am I missing something? We have checks like this for Ignite.NET [1]
>
> [1]
>
> https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core.Tests/ProjectFilesTest.cs
>
>
> On Wed, Sep 15, 2021 at 12:22 PM Ivan
>> Currently user
Sorry typo, I meant developer.
ср, 15 сент. 2021 г. в 12:35, Ivan Daschinsky :
> > How?
> Currently user must add sources in 2 different places. One of this places
> is not specified and not intended to be edit outside VC.
> CMake can generate VS projects e
using existing VS
> projects to CMake-generated ones?
>
>
>
> On Wed, Sep 15, 2021 at 12:37 PM Ivan Daschinsky
> wrote:
>
> > >> Currently user
> > Sorry typo, I meant developer.
> >
> > ср, 15 сент. 2021 г. в 12:35, Ivan Daschinsky :
> &g
+0.5 From me
1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16
a. build from source -- passed
b. run examples -- passed
2. windows 10 x86_64 visual studio 2017 cmake 3.21
a. build from source using cmake --passed
b. build odbc driver using cmake -- passed
c. run examples -- passed
Installin
Ok, found issue -- need to install VC++ 2010 redistributable package.
Currently, it is not available on windows 10.
I suppose, that this is a blocker.
ср, 15 сент. 2021 г. в 20:07, Ivan Daschinsky :
> +0.5 From me
> 1.ubuntu 20.04 gcc9.3.0 oracle jdk 1.8.0_281 cmake 3.16
> a. build fr
tudion 2010.
ср, 15 сент. 2021 г. в 20:46, Ivan Daschinsky :
> Ok, found issue -- need to install VC++ 2010 redistributable package.
> Currently, it is not available on windows 10.
> I suppose, that this is a blocker.
>
> ср, 15 сент. 2021 г. в 20:07, Ivan Daschinsky :
>
>>
not available on the official
> site, however available on mirrors. It's not good but not a crime but
> doesn't sound like a release blocker. Should we at least mentioned it
> on documentation pages?
>
> On Wed, 15 Sept 2021 at 20:50, Ivan Daschinsky
> wrote:
> >
>
So +1 for me, checked all C++ and ODBC drivers on ubuntu 20.04 and windows
10 x86_64
чт, 16 сент. 2021 г. в 09:35, Ivan Daschinsky :
> >> Can you please clarify in detail what exactly should be fixed?
> Sure. The ODBC driver is a native shared library, it depends on C++
> runtime
afarov (binding)
- +1 Ilya Shishkov
- +1 Aleksandr Nikolaev
- +1 Ivan Daschinsky
New release will be announced soon
wnload sources and binary packages (wheels) from
here:
https://dist.apache.org/repos/dist/release/ignite/pyignite/0.5.2/
Please let us know if you have any problems
https://ignite.apache.org/community/resources.html#ask
Regards,
Ivan Daschinsky on behalf of the Apache Ignite community.
ed'?
>
> python-0.5.2
> python-0.5.1
> python-0.5.0
>
> On Thu, 16 Sept 2021 at 09:44, Ivan Daschinsky
> wrote:
> >
> > Hello, Igniters!
> >
> > Release pyignite-0.5.2-rc0 has been accepted
> >
> > The votes received:
> > 3 "+1&
+1
Let's consider building odbc driver using Visual C++ 2017?
2015, 2017 and 2019 share the same redistributable package and it is the
default one in Windows 10.
Also, let's remove vs project files, since the most of you all agree that
it is redundant.
If both suggestions are ok, I will create
Hi! I can share my experience how to drive this activity. Personally, I've
driven four recent releases of python thin client (pyignite). First of all,
you should start a discussion, this thread is a good place to start.
Secondly, you should prepare release branch (with help of commiters),
create re
Created issues related building ODBC module, running C++ suites and
removing VS project files
1. https://issues.apache.org/jira/browse/IGNITE-15637
2.https://issues.apache.org/jira/browse/IGNITE-15636
вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky :
> +1
>
> Let's consider buildi
+1 As for me. It is pretty weird that this few lines of code depend on full
spring :)
вт, 5 окт. 2021 г. в 11:24, Nikita Amelchev :
> Mikhail,
>
> +1 to migrate and include to the ignite-spring-tx 1.0.0, Ignite 2.12 scopes
>
> Please, create an issue.
>
> пн, 4 окт. 2021 г. в 18:51, Mikhail Petro
Hi.
Pavel T., Ok, http rest dosn't have the clean design, in your opinion.
But what about grpc? The same?
As for me, it is ok to pass additional parameters as list of key-value
pairs with keys as strings and values as bytearrays or strings. It is ok to
allow user to set up middlewares for service
ontract (backward-compatible or otherwise)
>are explicitly reflected in the API.
>
>
> -Val
>
>
> On Sun, Oct 10, 2021 at 6:21 AM Pavel Tupitsyn
> wrote:
>
> > Ivan,
> >
> > Yes, this approach is used by some other systems, and still, I don't lik
implement it. Just expressing my concerns.
>
> -Val
>
> On Sun, Oct 10, 2021 at 11:52 PM Nikolay Izhikov
> wrote:
>
> > +1 to have service proxy context.
> >
> > > 11 окт. 2021 г., в 09:43, Ivan Daschinsky
> > написал(а):
> > >
> > > Val
s.
> >>
> >> 3. Read context "wrapper" using special annotation and supplier.
> >>
> >>@ServiceRequestContextResource
> >>private Supplier ctxSupplier;
> >>
> >>public void serviceMethod() {
> >>Stri
Hi folks!
Recently I've discovered that nightly builds are generated with invalid
version
Namely 3.0.0.x instead of 2.12.0.x.
The main reason -- recent changes in maven pom's.
I've filled ticket [1] and described thoroughly what should be fixed.
Peter, could you take a look?
[1] -- https
No objections.
>
> On Wed, Sep 15, 2021 at 12:58 PM Ivan Daschinsky
> wrote:
>
> > >> 1. What percentage of our users rely on existing VS projects?
> > It is impossible to answer, but I suppose not so much. And, again, these
> > projects needs some tweaks in order to w
+0.5 from me
1. Checked signatures and sha512 sums -- both OK
2. Both source packages compiles and tests passed -- OK
3. Manually created examples project from provided examples in
spring-tx-ext -- works OK with spring 5.3.11 (with manual exclusion of
spring dependencies) - OK
4. Checked previous
Nikita, can we add https://issues.apache.org/jira/browse/IGNITE-15806 this
ticket for release?
ср, 27 окт. 2021 г. в 13:40, Maksim Timonin :
> Hi,
>
> I'd like to include the ticket in 2.12. There was a performance issue, I
> spent some time trying to figure it out. I prepared some fixes and I am
Pavel, but what is the problem to include a minor refactoring? Especially
before code freeze?
ср, 27 окт. 2021 г. в 14:25, Pavel Tupitsyn :
> Ivan, IGNITE-15806 seems to be a minor refactoring, not sure we should
> inflate the scope with this.
>
> On Wed, Oct 27, 2021 at 2:13 PM Iva
t; > > >
> > > > чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev :
> > > >
> > > > > Maksim, ok.
> > > > >
> > > > > Ivan,
> > > > > The minor issues can be considered if they will be merged before
> the
> > &g
Thanks, cherry-picked to master.
вт, 2 нояб. 2021 г. в 16:00, Nikita Amelchev :
> Ivan,
>
> Yes, the patch can be cherry-picked.
>
> вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky :
> >
> > Since code freeze is postponed, may be I can cherry-pick my patch already
>
Hi folks!
Some people found, that recently it is quite hard to obtain green visa of
tcbot due to some circumstances.
After some refactorings, there are two .NET suites.
1. Linux .NET suite is run using teamcity .NET runner.
2. Windows .NET suite run test assemblies directly and here is the
probl
Hi, folks.
Currently, I'm developing custom numa-aware allocator and development is
almost done. [1]
In order to run and build tests, it is required to install libnuma-dev
packet on TC agents.
Peter, could you please install it, it is available on default package repo.
[1] -- https://issues.apa
Great, thanks a lot!
пн, 22 нояб. 2021 г., 07:38 Petr Ivanov :
> Hi, Ivan.
>
>
> Lib has been installed on all agents.
>
> On 17 Nov 2021, at 18:38, Ivan Daschinsky wrote:
>
> Hi, folks.
>
> Currently, I'm developing custom numa-aware allocator and development
;> I've fixed almost all the review comments [1]. Hopefully, the
> > changes
> > >>>>>> will be merged by the end of the week.
> > >>>>>>
> > >>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-14744
> > >>>
Hi, igniters!
There is not a big secret that nowadays NUMA is quite common in
multiprocessor systems.
And this memory architecture should be treated in specific ways.
Support for NUMA is present in many commercial and open-source products.
I've implemented a NUMA aware allocator for Apache Ignit
Guys, what is the status of ignite-shmem and TcpCommunication through it?
1. Native part has not been built at all since 2015
2. It is currently broken in master -- I've fixed some NPE and metrics
conversion locally and it works for me. It is broken for almost a year.
3. GridShmemCommunicationClie
it is abandoned?
пн, 29 нояб. 2021 г. в 19:24, Ivan Daschinsky :
> Guys, what is the status of ignite-shmem and TcpCommunication through it?
>
> 1. Native part has not been built at all since 2015
> 2. It is currently broken in master -- I've fixed some NPE and metrics
> conve
Congrats, Max! Well deserved
пн, 29 нояб. 2021 г. в 19:13, Kseniya Romanova :
> Igniters,
>
> The Project Management Committee (PMC) for Apache Ignite has invited Maxim
> Timonin to become a committer and we are pleased to announce that he has
> accepted.
>
> Maxim makes valuable contributions to
Good job, Semyon!
ср, 1 дек. 2021 г. в 10:10, Mirza Aliev :
> Congratulations, Semyon!
>
> ср, 1 дек. 2021 г. в 08:51, Zhenya Stanilovsky >:
>
> >
> > Wellcome Semyon !
> > Andrey what`s Ivan are you talking at the end of the message or this is
> > some kind of phraseologism that all russians ar
Semyon D. and Maks T. -- thanks a lot for review.
BTW, Igniters, I will appreciate all opinions and feedback.
пн, 29 нояб. 2021 г. в 10:13, Ivan Daschinsky :
> Hi, igniters!
>
> There is not a big secret that nowadays NUMA is quite common in
> multiprocessor systems.
>
101 - 200 of 429 matches
Mail list logo
