Slava, unfortunately, after some works that improves C++ bulding process,
now it is impossible to build old releases.
пт, 17 дек. 2021 г. в 16:28, Вячеслав Коптилин :
> Hello Maxim,
>
> Honestly, I don't quite understand why ODBC improvement is included in the
> release.
> It seems to me, we have
Haha, it becomes funny :) What if another vulnerability will be discovered
a few days later?
сб, 18 дек. 2021 г. в 18:04, Maxim Muzafarov :
> Folks,
>
>
> I've found that LOG4J2 2.17.0 version is released [1]. According to
> the description and risk mitigation [2] it is recommended the version
>
s.apache.org/jira/browse/IGNITE-16153
> [2] https://lists.apache.org/thread/w7kob4v6f3wm63g5j48wvcbj7l9y343q
>
> On Sat, 18 Dec 2021 at 19:31, Ivan Daschinsky wrote:
> >
> > Haha, it becomes funny :) What if another vulnerability will be
> discovered
> > a few days later?
> >
>
What do you mean, Anton? This is quite dangerous 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 bugf
+1 from me
Checked ODBC drivers (32-bit and 64-bit) installers on Windows with running
locally Ignite with
pyodbc and python 3.9 using this script [1]
[1] -- https://gist.github.com/ivandasch/6cc0b56e055b826e5840b5c04fa3b2fa
пн, 20 дек. 2021 г. в 15:45, Pavel Tupitsyn :
> +1
>
> Checked .NET bi
investigate it.
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-16157
>
> On 16.12.2021 20:11, Ivan Daschinsky wrote:
> > Andrey, agree with you, good point.
> >
> > чт, 16 дек. 2021 г., 16:27 Andrey Mashenkov >:
> >
> >> Guys,
> >>
ven if it was
> "upgraded" successfully?
>
> As I see, we just copy metastorage keys to a temporary one in key-by-key
> manner... and then do write-back to the original one.
> Seems, if smth goes wrong, the user may get both (original and temporary)
> stores b
> namelc...@apache.org
> > > > > > > >:
> > > > > > > > > >>>>>
> > > > > > > > > >>>>> Hi, Igniters.
> > > > > > > > > >>>>>
> > > > > > &g
Also, zookeeper ip finder depends on good old log4j 1.x
вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky :
> As for me, I am +1 for removing ZookeeperIpFinder from ignite-zookeeper.
>
>
> вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev :
>
>> Folks,
>>
>> What do you
gt; > >> >> On Tue, 21 Dec 2021 at 14:47, Denis Magda
> wrote:
> > >> >> >
> > >> >> > Hi Maxim,
> > >> >> >
> > >> >> > Just a reminder that since the release of the new website, we
> need
>
>> a lot of code in core code base is dedicated for enabling it.
It is simply not true. ZookeeperDiscovery has nothing common with
ZookeeperIpFinder.
The last one is simply one class and similar to others IP finders.
ср, 22 дек. 2021 г. в 13:25, Ilya Kasnacheev :
> Hello!
>
> I think it might no
I am +1 for removing ZookeeperIpFinder from ignite-zookeeper module. It is
not needed here.
ср, 22 дек. 2021 г. в 14:00, Ivan Daschinsky :
> >> a lot of code in core code base is dedicated for enabling it.
> It is simply not true. ZookeeperDiscovery has nothing common with
> Zo
e two packages have nothing common except substring "zookeeper". I
don't have any idea why they are present in one package.
ср, 22 дек. 2021 г. в 14:00, Ivan Daschinsky :
> I am +1 for removing ZookeeperIpFinder from ignite-zookeeper module. It is
> not needed here.
>
Vlad, congrats! You have definitely deserved it!
ср, 22 дек. 2021 г. в 20:40, Andrey Mashenkov :
> Congrats, Vlad!
>
> ср, 22 дек. 2021 г., 20:23 Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
> > The Apache Ignite Project Management Committee (PMC) has invited
> Vladislav
> > Pyatkov
t at the nearest
> time
> >>> > and prepare RC.
> >>> >
> >>> > Also, I suggest including issues [4, 5] that block the snapshot
> restore process.
> >>> >
> >>> > [1] https://issues.apache.org/jira/browse/IGNITE-13464
them from MyGet.
>
> Nikita,
>
> No, we won't upload NuGet packages to any registry before a successful RC
> vote.
> Only then we'll push them to nuget.org (as we always do).
>
>
> On Thu, Dec 30, 2021 at 12:38 PM Ivan Daschinsky
> wrote:
>
> > I'
-0.5. We should update log4j2 to version 2.17.1
пт, 31 дек. 2021 г., 00:43 Nikita Amelchev :
> Dear Community,
>
> The release candidate is ready.
>
> I have uploaded a release candidate to:
> https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc1/
> https://dist.apache.org/repos/dist/dev/ignit
ri, Dec 3, 2021 at 10:58 AM Valentin Kulichenko <
> valentin.kuliche...@gmail.com> wrote:
>
> > I think we can safely remove it.
> >
> > -Val
> >
> > On Thu, Dec 2, 2021 at 11:52 PM Ivan Daschinsky
> > wrote:
> >
> >> Hi, igniters.
>
+1 From me.
Checked Ignite.C++ on ubuntu 20.04 and windows:
1. Building and installing all components (Core, thin client and ODBC)
2. Run examples.
Checked building 64-bit and 32-bit ODBC driver installers (python + pyodbc)
Checked ODBC driver installers, shipped with ignite. (python + pyodbc)
в
Yep, seems that current behaviour is not correct at all. `serviceProxy()`
should return exactly what it should -- proxy.
ср, 19 янв. 2022 г. в 10:32, Maksim Timonin :
> Hi, guys!
>
> > this is not a good idea to change the behavior of serviceProxy()
> depending on statistics
>
> I think that the
eate a ticket.
>
> -Val
>
>
> On Thu, Jan 6, 2022 at 1:22 AM Ivan Daschinsky
> wrote:
>
> > Hi, Val. My plan was to file a specific ticket after discussion. If the
> > community agrees that this module should be removed, I will file a
> specific
>
I suppose it is great idea, but this functionality can be hard to implement
for some platforms. I.e. sync python client or php (there is no real
multithreading for python (GIL) and php is single threaded by design). But
for async clients it is not very hard to implement. Nevertheless, this
feature
Patch is ready for review
пт, 4 февр. 2022 г. в 14:45, Ivan Daschinsky :
> https://issues.apache.org/jira/browse/IGNITE-16480 -- I've filed ticked.
>
> пт, 7 янв. 2022 г. в 23:44, Valentin Kulichenko <
> valentin.kuliche...@gmail.com>:
>
>> Doesn't look like
van,
>
> Ideally, the check should come from both sides.
> - Client periodically sends keepalive to server
> - Server periodically sends keepalive to client
>
> Feature flags will be added accordingly, so it is not necessary to
> implement this in all thin clients.
>
> On Mon
> > >
> > > > Ivan,
> > > >
> > > > I suggest the following:
> > > >
> > > > 1. Server sends KEEP_ALIVE feature flag, which means it accepts
> > > > OP_KEEP_ALIVE empty message
> > > > 2. Client sends OP_KE
> > > it works (or did I misunderstand you?)
> > > >
> > > > Of course, enabling heartbeats means that otherwise idle clients will
> > no
> > > > longer be disconnected by the server.
> > > > I think we should cross-link those properties i
) and sent to the client during handshake.
> > Also we can introduce something like a negotiation mechanism as in
> > zookeeper.
>
> I tend to agree with Maksim here, let's keep it simple and explicit.
> Log a warning, but don't do anything clever.
>
> On Mon, Feb 7,
Patch has been reviewed by Andrey Mashenkov and Max Muzafarov and approved.
If nobody disagrees, I will merge it in a few hours.
пн, 7 февр. 2022 г. в 12:21, Ivan Daschinsky :
> Patch is ready for review
>
> пт, 4 февр. 2022 г. в 14:45, Ivan Daschinsky :
>
>> https://issu
Igniters, I'd like to discuss the future of this functionality in Apache
Ignite
Today this functionality seems to be unusable
1. It is limited (especially redis)
2. It doesn't support HA (redis sentinel or redis cluster)
3. Nobody maintains it and even nobody fixes bugs. (i.e. [1] is not merged
fo
nes that a really important for
> production e.g. Calcite for Ignite 2.x. However, talking in terms of
> open-source development it's better to find a volunteer who will fix
> all the issues you describe.
>
> On Tue, 8 Feb 2022 at 14:27, Ivan Daschinsky wrote:
> >
>
Congrats, Pasha!
чт, 10 февр. 2022 г. в 18:16, Maxim Muzafarov :
> The Project Management Committee (PMC) for Apache Ignite has invited
> Pavel Pereslegin to become a committer and we are pleased to announce that
> he has accepted.
>
> He made a lot of major contributions to the Apache Ignite cod
/pull/9817#discussion_r805628955
пт, 11 февр. 2022 г. в 10:58, Pavel Tupitsyn :
> I've prepared a PR, please have a look:
> https://github.com/apache/ignite/pull/9817
>
> On Mon, Feb 7, 2022 at 6:37 PM Ivan Daschinsky
> wrote:
>
> > I see potential in this feature, especi
etc. Clients should check every response and in case of
> > changed idleTimeout. For 2nd case write a WARN message, and for 3rd -
> > reconfigure themself in case of changed idleTimeout.
> >
> >
> >
> >
> > On Tue, Feb 15, 2022 at 9:51 AM Ivan Daschinsky
&
Pavel, sorry, i've made mistake. But current behaviour is ok for me. This
timeout cannot be change on server side runtime. But we can simplify
protocol just use one opcode and message
вт, 15 февр. 2022 г., 14:54 Ivan Daschinsky :
> > Idle timeout can't change, why send it
16:32, Ivan Daschinsky :
> Pavel, sorry, i've made mistake. But current behaviour is ok for me. This
> timeout cannot be change on server side runtime. But we can simplify
> protocol just use one opcode and message
>
> вт, 15 февр. 2022 г., 14:54 Ivan Daschinsky :
>
>>
tsEnabled = true;
> > > long defaultHeartbeatInterval = 60_000; // Default 1 minute, used
> > >
> > > Logic:
> > > if (heartbeatsEnabled) {
> > > heartbeatInterval = serverIdleTimeout > 0 ? serverIdleTimeout / 3 :
> > > defaultHeartbeatInterval;
> > > }
>
meout when the user-specified value is
> not already less than that.
>
> On Wed, Feb 16, 2022 at 7:19 PM Pavel Tupitsyn
> wrote:
>
> > Ok, let's keep heartbeatInterval then.
> > I've updated the code to reflect our recent agreement, please review.
> >
>
Problem was introduced in 2b74474b7220df046c5c6d7a12a23ba90a697025. Suite
has not been run since that commit.
чт, 24 мар. 2022 г. в 19:01, Shishkov Ilya :
> Hi everyone,
>
> As I see, both 'Control Utility' and 'Control Utility (Zookeeper)' test
> suites have empty test results and there are mess
l) of junit and tests
> just don't start due to different junit version (5 instead of 4).
>
> I'll fix it today.
>
> On Mon, Mar 28, 2022 at 11:50 AM Ivan Daschinsky
> wrote:
>
> > Problem was introduced in 2b74474b7220df046c5c6d7a12a23ba90a697025. Suite
> &
Seems that after update of zookeeper and curator, behaviour of testing
cluster have been slightly changed. I've tried to
increase zookeeper.electionPortBindRetry for testing zk ensemble
nodes and seems all issues are resolved now.
пн, 4 апр. 2022 г. в 17:37, Ilya Shishkov :
> Hi all,
>
> As I see
Seems that somehow numa-allocator is not included in binary releases.
ср, 20 апр. 2022 г. в 14:14, Nikita Amelchev :
> I will make sure this issue is included in the 2.13 documentation. Thanks.
>
> ср, 20 апр. 2022 г. в 14:09, 18624049226 <18624049...@163.com>:
> >
> > I think the following commi
erry-picked and prepare a new RC.
>
> ср, 20 апр. 2022 г. в 14:45, Ivan Daschinsky :
>
> >
> > Seems that somehow numa-allocator is not included in binary releases.
> >
> > ср, 20 апр. 2022 г. в 14:14, Nikita Amelchev :
> >
> > > I will make sure
+0.5
Checked ODBC drivers binaries on windows (32 and 64 bit) using pyodbc and
python 3.8
Checked both H2 and Calcite engines (setted in DSN and Connection
configurations)
Works with issues -- cannot start ignite without copying slf4j-api jar into
ignite-calcite module. Calcite depends itself on
Since nuget packages have been built on the same linux agent as the main
release, it sounds logical to me that this step can be done within the
maven lifecycle.
I am for it, +1
ср, 8 июн. 2022 г. в 15:13, Maxim Muzafarov :
> Hello Igniters,
>
>
> I'd like to simplify the release build for the Apa
As for the last number in .NET version, AFAIK it is used as the unique
build id and is required for nightly builds as nuget doesn't have
functionality a-la maven's 'snapshots'
ср, 8 июн. 2022 г. в 16:07, Ivan Daschinsky :
> Since nuget packages have been built on the same
Seems that we forgot to disable the cloud test suite after removing this
module?
ср, 15 июн. 2022 г. в 10:53, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this failure(s): We're grateful that y
Guys, I simply cant understand why providing simple function Object ->
int32 in cache configuration is wrong decision, but implementing cryptic
logic with class names, feature flags and still being unable to solve the
probem is ok. I don't understand how an ability to obtain a classname of
java cla
> >> feature flags
> >
> > What's bad about feature flags?
> >
> >> how an ability to obtain a classname of java class can help my python or
> > C++ client map key to partition
> >
> > Not a java class name, but type id. You can set up type id
t; > > > @Override public AffinityFunction apply(Integer groupId, Integer
> > > > parts) {
> > > > return new RendezvousAffinityFunction(false, parts);
> > > > }
> > > > }
> > > >
> > > > This cases will
I am strongly against serialization, it simply doesn't work except some
trivial cases. Explicit is better than implicit.
вт, 12 июл. 2022 г., 12:56 Ivan Daschinsky :
> Unfortunately, affinity function is not rivially constructible, at least
> default one
>
> вт, 12 июл. 202
Congrats, Slava!
чт, 18 авг. 2022 г. в 18:26, Вячеслав Коптилин :
> Hi Igniters,
>
> Many thanks to all of you! I really appreciate this.
>
> Thanks,
> S.
>
> чт, 18 авг. 2022 г. в 17:17, Andrey Mashenkov >:
>
> > Congratulations, Slava!
> >
> > On Wed, Aug 17, 2022 at 5:35 PM Kseniya Romanova
Congrats! Keep on going!
пн, 22 авг. 2022 г., 13:34 Вячеслав Коптилин :
> Congratulations, Taras, very well deserved!
>
> Thanks,
> S.
>
> вс, 21 авг. 2022 г. в 19:26, Ilya Shishkov :
>
> > Congratulations, Taras!
> >
> > вс, 21 авг. 2022 г. в 09:52, Pavel Tupitsyn :
> >
> > > Congrats!
> > >
> >
I suppose that we are not in rush, because we have just cut off a release
branch for 2.14. Let us wait for a new release of Calcite. By the way, has
that bug been already reported?
вт, 30 авг. 2022 г., 20:35 Zhenya Stanilovsky :
>
> Igniters, i found that new release of apache calcite was release
Oh, sorry, I see that it has been alredy reported. So let us wait for a bug
fix.
ср, 31 авг. 2022 г., 08:10 Ivan Daschinsky :
> I suppose that we are not in rush, because we have just cut off a release
> branch for 2.14. Let us wait for a new release of Calcite. By the way, has
> that
t; >
> > >
> > > вс, 18 сент. 2022 г. в 12:10, Zhenya Stanilovsky
> > > > > >:
> > >
> > > >
> > > > Join the congratulations !
> > > >
> > > >
> > > >
> > > >
> > > > >Hi Igniters!
> > >
+1 (binding)
Checked C++ module and C++ examples compilation on windows 10 (msvc 2017)
and ubuntu 22.04 (gcc 11.2.0).
Checked ODBC on windows 10 and ubuntu 22.04 (unixodbc) by pyodbc and python
script (both H2 and CALCITE query engines).
Checked ODBC pre-built binaries on windows 10
Despite the f
Congrats, Kirill!
вт, 11 окт. 2022 г. в 11:26, Denis C :
> Congratulations!
>
> вт, 11 окт. 2022 г. в 09:46, Aleksandr Pakhomov :
>
> > Congratulations!
> >
> > > On 10 Oct 2022, at 22:15, Pavel Tupitsyn wrote:
> > >
> > > The Project Management Committee (PMC) for Apache Ignite
> > > has invite
Hi, we don't link our odbc driver with openssl libraries. We load them
dynamically. So don't worry, our odbc driver is not affected at all.
Moreover, it supports multiple versions of openssl, up to 3.0.x
пн, 7 нояб. 2022 г. в 12:17, Ilya Kasnacheev :
> Hello!
>
> For the most part, we to not supp
So you should just download the latest openssl binaries, add them to PATH
and that's it. The ignite odbc driver will load them automatically.
You could also set OPENSSL_HOME env variable to the specific folder with
the valid openssl binaries.
Hi, Igniters!
I suppose it is time to release pyignite 0.6.0, since we have released our
previous release more than a year ago.
Firstly, python 3.6 reached its EOL, the brand new python, 3.11, was just
released. So it is a good idea to build new wheels targeting the new
versions.
Also, there are
Actually, I've arleady created release branch, release notes. I suppose
that tomorrow I will start a voting process. Is there any objection?
вт, 8 нояб. 2022 г. в 11:18, Igor Sapego :
> +1
>
> Github Actions look great to me.
>
> Best Regards,
> Igor
>
>
> On
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.6.0.rc0
If you follow the link above, you will find source packages (*.zip)
and binary packages (wheels) for windows (amd64), mac os
Please, send a mail to dev-unsubscr...@ignite.apache.org
пн, 14 нояб. 2022 г. в 11:58, John Liston :
> UNSUBSCRIBE
>
>
>
> From: Mikhail Petrov
> Sent: Monday, November 14, 2022 3:35 AM
> To: dev@ignite.apache.org
> Subject: Re: [ANNOUNCE] Welcome Mikhail Petrov
__.py
>
> Thanks,
>
> --
>
> Sergey Korotkov
>
>
> On 11.11.2022 20:40, Ivan Daschinsky wrote:
> > Dear Igniters!
> >
> > Release candidate binaries for subj are uploaded and ready for vote
> > You can find them here:
> > https://dist.apach
Ok, I've just fixed these issues. So I decided to cancel the vote. New vote
will be announced soon as I'll have uploaded artifacts.
пн, 14 нояб. 2022 г. в 14:50, Ivan Daschinsky :
> Great catch, especially the second one.
>
> Seems that it is a good idea to cancel the vote
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.6.0.rc1
If you follow the link above, you will find source packages (*.zip)
and binary packages (wheels) for windows (amd64), mac os
>>
https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.6.0.rc0/examples.html
https://apache-ignite-binary-protocol-client.readthedocs.io/en/0.6.0.rc1/examples.html
пн, 14 нояб. 2022 г. в 16:21, Ivan Daschinsky :
> Dear Igniters!
>
> Release candidate binaries for su
+1 (binding) Checked signature, hashsums, checked client on all 5 pythons
on all available platforms (mac x86_64, ubuntu x86_84 and windows 10
x86_64).
Checked docs (readthedocs).
вт, 15 нояб. 2022 г. в 09:10, Zhenya Stanilovsky :
>
> +1, thanks Ivan !
>
>
> >Dear Igniters!
> >
> >Release candida
Dear Igniters!
Vote is closed, the result is:
7 (4 binding) +1 votes (Igor Sapego, Sergey Korotkov, Zhenya Stanilovsky,
Ivan Daschinsky, Ilya Shishkov, Anton Vinogradov, Maxim Muzafarov)
No 0 votes
No -1 votes
Therefore, the release is accepted unanimously.
Release binaries will be uploaded
https://ignite.apache.org/community/resources.html#ask
Regards,
Ivan Daschinsky on behalf of the Apache Ignite community.
Cool, the first beta is a real achievement! Congrats!
пн, 21 нояб. 2022 г. в 18:20, Igor Sapego :
> Congrats, guys!
>
> Best Regards,
> Igor
>
>
> On Thu, Nov 17, 2022 at 4:39 PM Вячеслав Коптилин <
> slava.kopti...@gmail.com>
> wrote:
>
> > Dear Igniters,
> >
> > I'm happy to announce that the 1
+1 This module seems to be completely abandoned
чт, 1 дек. 2022 г., 00:46 Ilya Kasnacheev :
> Hello!
>
> Let's go ahead and remove what we don't use. Most of that stuff is deep
> legacy, even if it contains some rare gems of functionality that nobody
> knows how to use anymore.
>
> Regards,
> --
Alex, I agree with your proposal. It is ok to start scanning servers
firstly using the same default port, then continue with subsequent ports
within range.
пт, 20 янв. 2023 г. в 10:47, Alex Plehanov :
> Pavel,
>
> But in this case connections still will be unbalanced for disabled
> partition awar
Dear Igniters!
This is a patch release that contains an important fix for users of
pyignite
https://issues.apache.org/jira/browse/IGNITE-18788
Release candidate binaries for subj are uploaded and ready for vote
You can find them here:
https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.6.1
The vote is closed. The results will be announced soon.
ср, 15 февр. 2023 г. в 14:10, Maxim Muzafarov :
> +1
>
> On Wed, 15 Feb 2023 at 11:17, Вячеслав Коптилин
> wrote:
> >
> > +1
> >
> >
> > ср, 15 февр. 2023 г. в 10:21, Ivan Daschinsky :
> >
5 (4 binding) +1 votes (Nickolay Izhikov, Pavel Tupitsyn, Vladimir
Steshin, Slava Koptilin, Maxim Muzafarov)
No 0 votes
No -1 votes
Therefore, the release is accepted unanimously.
Release binaries will be uploaded soon. The release will be announced soon.
Thank you all!
Sorry, the mistake -- pyignite 0.6.1.rc0
пт, 17 февр. 2023 г. в 18:04, Ivan Daschinsky :
>
> 5 (4 binding) +1 votes (Nickolay Izhikov, Pavel Tupitsyn, Vladimir
> Steshin, Slava Koptilin, Maxim Muzafarov)
> No 0 votes
> No -1 votes
>
> Therefore, the release is accepted u
Hi, Igniters!
The release was releases and uploaded to pypi 02/17/22
Sorry for the late announcement
+1 (binding)
Checked signatures and hashsums.
Checked C++ compilation and examples on linux (ubuntu 22.04) and windows
(win10, vs 2017).
Checked ODBC on linux (ubuntu 22.04, built from source) and windows (built
from source and from installer, both 32 and 64 bit) using python and pyodbc
Checked
>> Tx processing is supposed to be thread bound by hashing the version to a
partition
This invariant is violated in many places. The most notorious example is tx
recovery.
Another example: I just added an assertion that checks tId of a creator
thread with tId of an accessor thread.
TxMultiCacheAsy
Igniters, seems that this module is completely abandoned for more than 2
years. But it is enormous and it seems that nobody wants to take care of
it. I suggest just removing it or moving it to extensions (as option). WDYT?
with
> > > > dependencies takes about 1/4 of our binary release package size) and
> > > > we spend team-city resources to test module.
> > > >
> > > > +1 for removing or moving to extensions.
> > > >
> > >
Actually, I haven't found any integration with tensorflow in AI code.
Actually, all integrations are some adapters that allow to load pretrained
models (h2o, catboost etc.)
чт, 10 авг. 2023 г. в 13:08, Ivan Daschinsky :
> I am personally for moving to extensions. Alex has already menti
doc.
> >>
> >> Adapters may require compilation time dependencies, but these
> dependencies
> >> shouldn't be part or release package,
> >> regardless whether the ML module is a part of Ignite or extensions.
> WDYT?
> >>
> >> On Thu, Aug 10, 2023 a
I've filed a ticket and created 2 PRs. After tuning of TC I'm going to
merge both of them, if nobody disagrees with it.
https://issues.apache.org/jira/browse/IGNITE-20216
пн, 14 авг. 2023 г. в 22:29, Ivan Daschinsky :
> >> * com.github.fommil.netlib:core:1.1.2 - not dev
>> https://issues.apache.org/jira/browse/IGNITE-20216
Also, I've updated dependencies and fixed BLAS issue (tested with intel mkl
blas on ubuntu 22.04)
ср, 16 авг. 2023 г. в 12:11, Ivan Daschinsky :
> I've filed a ticket and created 2 PRs. After tuning of TC I'm going to
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,
>
> I started the TX code cleanup [1] last month and almost finished with the
> obvious garbage.
> Now, started the code deduplication, I w
ML Extensions suite is ready and it works, all tests from the main module
and parsers, all examples -- everything works and all green [1].
The green visa has been obtained. So I am going to merge it tomorrow, if
there is no objection.
[1] ---
https://ci.ignite.apache.org/buildConfiguration/Ignit
+1. It's time to do it at last.
пт, 25 авг. 2023 г. в 12:06, Peter Ivanov :
> Mostly, yes.
>
> In other words - proposal is about starting shipping Apache Ignite releases
> with JDK11 compiled binaries thus dropping JDK8-10 runtime support.
>
> пт, 25 авг. 2023 г. в 12:03, Anton Vinogradov :
>
>
> version for our needs (and especially LTS versions 1.8, 11 and 17) with all
> necessary updates.
>
> So, I suggest we update our build agents for TeamCity accordingly, provide
> OpenJDK framework for those 3 major versions and discontinue Oracle's
> builds.
> WDYT?
>
PRs have been merged. Many thanks for review to Nikita Amelchev and Aleksei
Zinoviev
пт, 25 авг. 2023 г. в 17:05, Nikita Amelchev :
> +1 for moving to extensions
>
> This module is good as an extension:
> - does not depend on the internal Ignite API,
> - the released module will be compatible wit
Hi! It seems that these checks simply don't work, at least for PRs.
Yep, they work ok for master, but some of warnings from these tools seem to
be just rubbish, like
this one -- [1].
We should either do a tremendous job to fix these issues or simply disable
these checks.
Simply ignoring is not an
d* code we have.
>
> Both issues should be solved properly, not by removing the quality tool.
>
> My huge -1 here
>
> On Thu, Sep 28, 2023 at 1:36 PM Ivan Daschinsky
> wrote:
>
> > Hi! It seems that these checks simply don't work, at least for PRs.
> > Yep,
f such
> hints.
> Could you please show "a lot" of false positives?
> The url you provided contains a lot of *correct* hints.
>
> > But constantly red checks lead to ignoring of all checks.
> I'm checking each report, and fixed a lot of dummy issues thanks to it.
>
ed checks lead to ignoring of all checks.
> > I'm checking each report, and fixed a lot of dummy issues thanks to it.
> >
> > On Thu, Sep 28, 2023 at 1:49 PM Ivan Daschinsky
> > wrote:
> >
> >> Sonar shows lots of false positives. We cannot add //NOSONA
>> No, I just think that we should remove 1 yaml file unless the sonar
check is not properly configured.
No, I just think that we should remove 1 yaml file unless the sonar check
is properly configured. -- corrected
чт, 28 сент. 2023 г. в 14:12, Ivan Daschinsky :
> No, I just thin
Congratulations, you deserve it
On Wed, Nov 22, 2023, 18:10 Nikita Amelchev wrote:
> Thank you everyone, I'm very pleased!
>
> ср, 22 нояб. 2023 г. в 15:46, Ilya Shishkov :
> >
> > Congratulations, Nikita!
> >
> > ср, 22 нояб. 2023 г. в 14:53, Maksim Timonin :
> > >
> > > Congratulations!
> > >
+1 from me (binding)
1. Checked checksums
2. Checked C++/ODBC driver: built from source and ran examples on Ubuntu
22.04/gcc 11.4.0/OpenJDK-Temurin 17.0.8
3. Checked ODBC driver with pyodbc (python 3.11 + pyodbc 4.0.35). Checked
on calcite and H2 engines. (Ubuntu 22.04)
вт, 19 дек. 2023 г. в 13:5
Hi, Steven. Currently I am preparing an initial release of the ML
extension. Just thinking about creating a new thread and here you are :)
The release branch is ready, I just need to prepare artifacts and upload
them to staging. Then I am going to start the vote thread.
https://github.com/apache/i
Also, I have updated dependencies and fixed native BLAS integration (tested
on ubuntu 22.04 with Intel MKL)
пн, 22 янв. 2024 г. в 19:18, Ivan Daschinsky :
> Hi, Steven. Currently I am preparing an initial release of the ML
> extension. Just thinking about creating a new thread and here y
301 - 400 of 429 matches
Mail list logo