[VOTE] Release Apache Ignite ML Extension 1.0.0 RC1

Dear Community, I am happy to start this voting thread. The release candidate have been uploaded to: https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-ml-ext-1.0.0-rc1/ The staging maven repository is here: https://repository.apache.org/content/repositories/orgapacheignite-15

Re: [VOTE] Release Apache Ignite ML Extension 1.0.0 RC1

Sorry for my mistake, this vote will be open till Jan 26, 2024 вт, 23 янв. 2024 г. в 16:27, Ivan Daschinsky : > Dear Community, > I am happy to start this voting thread. > > The release candidate have been uploaded to: > > https://dist.apache.org/repos/dist/dev/ignite/ignite-ex

[VOTE] Release Apache Ignite ML Extension 1.0.0 RC1

Dear community, The release of Apache Ignite ML Extension 1.0.0. RC1 has been accepted Vote result: +1 -- 4 votes (4 binding votes) 0 -- 0 votes -1 -- 0 votes +1 votes: Nikita Amelchev Alex Plehanov Maxim Muzafarov Alexey Zinoviev The new release will be announced soon.

[ANNOUNCE] Apache Ignite ML Extension 1.0.0 released

/org.apache.ignite/ignite-ml-ext Please let us know if you encounter any problems: https://ignite.apache.org/community/resources.html#ask --- Best Regards Ivan Daschinsky on behalf of Apache Ignite PMC

Re: [ANNOUNCE] Apache Ignite ML Extension 1.0.0 released

All parsers also have been uploaded to maven central: https://central.sonatype.com/artifact/org.apache.ignite/ignite-ml-ext/dependents пн, 29 янв. 2024 г. в 12:00, Ivan Daschinsky : > The Apache Ignite Community is pleased to announce the release of Apache > Ignite ML Extension 1.0.0. &

Re: Possible concurrency bug in GridCacheLockImpl

Sorry, I meant not GridCacheLockImpl but CacheLockImpl. пт, 3 апр. 2020 г. в 17:04, Ivan Daschinskiy : > Folks, > > Lurking through code, it seems I found some concurrency issue in subj. > > * This class contains two fields, volatile Thread lockedThread and > non-volatile int cntr (used for reent

Re: Why OPTIMIZE_REUSE_RESULT is set to 0 explicitly in o.a.i.i.p.query.h2.ConnectionManager#DEFAULT_DB_OPTIONS

Thank you for your response, Konstantin I think we cannot just turn this optimization > Of course not, that is the reason why I started this thread. org.apache.ignite.internal.processors.query.h2.opt.GridH2Table don't change > it neither on remove or update Yes, but we can increment this count

Re: [DISCUSSION] Ignite.C++ and CMake

Igor, I just said about native support from Visual Studio, not from cmake itself. Modern cmake can generate projects even for Visual Studio 2008 [1] [1] -- https://cmake.org/cmake/help/v3.16/generator/Visual%20Studio%209%202008.html вт, 26 мая 2020 г. в 16:16, Igor Sapego : > Nikolay, removing

Re: [DISCUSSION] Ignite.C++ and CMake

Guys, I will certainly thoroughly test my fix not only unices, but on windows too. And I will describe it very thoroughly. When I was C++ developer (more than 10 years ago), I have not any trouble at all with CMake and Visual Studio 2005. Everything works and works good. Moreover, you can build wi

Re: [DISCUSSION] Ignite.C++ and CMake

: > Hello! > > I will assist with checking on Linux if you would contribute a patch. > Please start with a ticket (or even an IEP maybe?) > > Regards, > -- > Ilya Kasnacheev > > > вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky : > > > Guys, I will certainly thor

Re: [DISCUSSION] Ignite.C++ and CMake

e code worth taking. > > https://github.com/apache/ignite/pull/4872 < > https://github.com/apache/ignite/pull/4872> > > Regards, > Stephen > > > On 26 May 2020, at 16:02, Ivan Daschinsky wrote: > > > > I appreciate any help, thank you, Ilya. > > >

Re: Prevent insertion of cache entry if the binary field type and the type of the query entity do not match.

I think this feature quite easy to implement. Before put in cache tree, we can iterate over query descriptor fields and check whether this field presents in binary object and if typeId is the same. But I think there can l be a quite noticeable performance penalty when this feature is enabled. It sh

Re: [DISCUSSION] Ignite.C++ and CMake

reports are welcomed! вт, 26 мая 2020 г. в 18:51, Ivan Daschinsky : > Stephen, looks great! I do mostly the same things in C++ code. Thank you! > > вт, 26 мая 2020 г. в 18:33, Stephen Darlington < > stephen.darling...@gridgain.com>: > >> Not sure if it’ll help, but I

Re: [DISCUSSION] Ignite.C++ and CMake

release, without and with odbc, checked running thick > node and ODBC connection on Linux. > > Regards, > -- > Ilya Kasnacheev > > > чт, 28 мая 2020 г. в 17:31, Ivan Daschinsky : > > > Ok, PR is ready > > https://issues.apache.org/jira/browse/IGNITE-13078 &g

Re: [DISCUSSION] Ignite.C++ and CMake

Also without with flag we can observe many failures of suites on TC https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCLinux?branch=%3Cdefault%3E&mode=builds#all-projects пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky : > Ilya, thanks a lot! What about tests? I fo

Re: Re[2]: [DISCUSSION] Ignite.C++ and CMake

>That's where we should wait for Igor Sapego to check. > > > >Regards, > >-- > >Ilya Kasnacheev > > > > > >пт, 29 мая 2020 г. в 12:20, Ivan Daschinsky < ivanda...@gmail.com >: > > > >> Ilya, thanks a lot! What about tests? I found

Re: Re[2]: [DISCUSSION] Ignite.C++ and CMake

Igor, could you please check my PR? пт, 29 мая 2020 г. в 15:28, Ivan Daschinsky : > Thanks you all. Run patch (I've changed some code also) on TC -- all CPP > suites are green (GCC, CLang, Win64) > > пт, 29 мая 2020 г. в 15:02, Zhenya Stanilovsky >: > >> >&g

Re: [DISCUSSION] Add autocompletion for commands in control.sh

+1 But this is not only usability improvement, but also a huge code improvement. With picocli developers can add custom command without writing a lot of boilerplate and error prone code to do a trivial task of parsing CLI arguments. Cleaner code, less bugs also matter. вт, 2 июн. 2020 г. в 16:02,

Re: [DISCUSSION] Add autocompletion for commands in control.sh

ive benchmark CLI, has ** Apache [Ignite TensorFlow] **, and Apache > Sling. > > > [1] https://github.com/remkop/picocli/blame/master/README.md#L199 > > On Tue, 2 Jun 2020 at 16:09, Ivan Daschinsky wrote: > > > > +1 But this is not only usability improvement, but also a

IGNITE-12808 Allow create tables for existing caches

Hi Igniters. I've recently submitted patch[1] that implemented subj. Any help with review would be appreciated. [1] - https://issues.apache.org/jira/browse/IGNITE-12808 -- Sincerely yours, Ivan Daschinskiy

Discussion: Existence of manual pinger for ZK client

Igniters, I suppose, that existence of manual pinger, introduced in [1], in our ZkDiscoveryImpl is under a big question. This weird thing was introduced to solve specific issue, specifically strange freeze of all threads of process during deallocate (Unsafe.freeMemory) of large amount of data. Actu

Re: Apache Ignite 2.7. Last Mile

Hi! Is it possible to merge IGNITE-9854? Fix is pretty simple, but quite important. ср, 17 окт. 2018 г. в 17:49, Andrey Gura : > JFYI > > IGNITE-9737 and IGNITE-9710 are merged to release branch. > On Wed, Oct 17, 2018 at 5:41 PM Pavel Tupitsyn > wrote: > > > > Thank you. Fix has been merged to

PR#3697 IGNITE-8021: Delete cache config files when destroyed

Hi Team, Could you review this PR https://github.com/apache/ignite/pull/3697 please? Tests result: https://ci.ignite.apache.org/viewLog.html?buildId=1159660 Jira ticket: https://issues.apache.org/jira/browse/IGNITE-8021 -- Sincerely yours, Ivan Daschinskiy

Re: IGNITE-6827 - Review needed.

Hi all, I've implemented corresponded .NET api. Pavel, could you review my PR, please? https://issues.apache.org/jira/browse/IGNITE-8075 2018-04-10 21:06 GMT+03:00 Dmitry Pavlov : > Hi Pavel, > > thank you for bring up test questions. It seems my previous comments were > not taken into account

Request for contributor permissions

Hello Ignite Community! My name is Ivan Daschinskiy. I want to contribute to Apache Ignite and want to start with this issue - IGNITE-6860 , my JIRA username *ivandasch*. Any help on this will be appreciated. Thanks a lot! -- Sincerely yours, Iv

[jira] [Created] (IGNITE-14511) Putting bytes to cache converted to string by default.

Ivan Daschinsky created IGNITE-14511: Summary: Putting bytes to cache converted to string by default. Key: IGNITE-14511 URL: https://issues.apache.org/jira/browse/IGNITE-14511 Project: Ignite

[jira] [Created] (IGNITE-14518) Generated PKG_INFO of package doesn't contains license info and long description

Ivan Daschinsky created IGNITE-14518: Summary: Generated PKG_INFO of package doesn't contains license info and long description Key: IGNITE-14518 URL: https://issues.apache.org/jira/browse/IGNITE-

[jira] [Created] (IGNITE-14564) Add LICENSE and NOTICE file to all packages

Ivan Daschinsky created IGNITE-14564: Summary: Add LICENSE and NOTICE file to all packages Key: IGNITE-14564 URL: https://issues.apache.org/jira/browse/IGNITE-14564 Project: Ignite Issue

[jira] [Created] (IGNITE-14595) ExpiryPolicy support to python thin client

Ivan Daschinsky created IGNITE-14595: Summary: ExpiryPolicy support to python thin client Key: IGNITE-14595 URL: https://issues.apache.org/jira/browse/IGNITE-14595 Project: Ignite Issue

<    1   2   3   4   5