Blog about Ignite.NET changes:
https://ptupitsyn.github.io/Whats-New-In-Ignite-Net-2.11/
On Fri, Sep 24, 2021 at 2:32 PM Alexandr Shapkin
wrote:
> Hello!
>
> Since the new release comes with more modules extracted into the
> extensions repo, I think it’s vital to update them as well. Consider
>
Hello!
Since the new release comes with more modules extracted into the extensions
repo, I think it’s vital to update them as well. Consider
SpringTransactionManager which is now a part of ignite-spring-tx-ext [1] that
hasn’t been released yet. At least I failed to find any maven artifacts
pub
Thanks to Maxim and kudos to Alexey Gidaspov, who was serving role of Release
manager during all init, rampdown and stabilization phase.
Sincerely,
Dmitriy Pavlov
On 2021/09/21 09:01:55, Pavel Tupitsyn wrote:
> Maxim,
>
> I'll prepare a dedicated blog post about Ignite.NET changes later this
Maxim,
I'll prepare a dedicated blog post about Ignite.NET changes later this week.
Thanks for driving the release!
On Mon, Sep 20, 2021 at 11:20 PM Maxim Muzafarov wrote:
> Denis,
>
> The post is added:
> https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization
>
> I've fixed the
Denis,
The post is added:
https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization
I've fixed the image according to your suggestions.
On Mon, 20 Sept 2021 at 21:35, Denis Magda wrote:
>
> Maxim, thanks for driving the release and preparing the announcement
> article!
>
> A few qu
Maxim, thanks for driving the release and preparing the announcement
article!
A few questions:
- Should "dev" be replaced with "2.11" on the picture of the cellular
clusters deployment section?
- Will the article be published on our blogs.apache.org page?
-
Denis
On Sat, Sep 18, 2021
Pavel,
I've prepared a draft blog post [1] for the 2.11 release announcement
message, however, this post doesn't include changes related to the
.NET part of the Apache Ignite. Will you prepare a dedicated post
related to the .NET changes or I should include them in this one?
Folks,
all the comme
Hello, Igniters!
Apache Ignite 2.11.0 release (RC2) has been accepted.
5 - "+1" votes received.
1 - "+0,5" vote received.
Here are the votes received:
- Pavel Tupitsyn (binding)
- Alex Plehanov (binding)
- Nikolay Izhikov (binding)
- Ilya Kasnacheev
- Ivan Daschinsky
- Zhenya Stanilovsky
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.
> We ship one b
>> 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.
We ship one builded using Visual C++ 2010, so runtime libraries should be
installed first.
These runtime libraries are usually shipped in so called redistri
Ivan,
Can you please clarify in detail what exactly should be fixed? I'm not
familiar with running something from Ignite under the Windows
environment. It's weird if something is not available on the official
site, however available on mirrors. It's not good but not a crime but
doesn't sound like
>> Currently, it is not available on windows 10.
I mean that it is impossible to download this redist package from official
site, it was removed.
It is weird to make user search this on suspicious sites over the internet.
The main issue that we still build C++ packages on TC using Visual
Studion 2
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 from source --
+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
+1 (binding)
> 15 сент. 2021 г., в 12:24, Alex Plehanov написал(а):
>
> +1
>
> Checked sha512 and sign of archives, built from sources, started a cluster
> with a few nodes.
>
> вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn :
>
>> Ilya,
>>
>>> I'm still confused by this publish/ directory. Wh
+1
Checked sha512 and sign of archives, built from sources, started a cluster
with a few nodes.
вт, 14 сент. 2021 г. в 21:23, Pavel Tupitsyn :
> Ilya,
>
> > I'm still confused by this publish/ directory. Why are we shipping
> > something which is not for publishing in our binary package? I've al
Ilya,
> I'm still confused by this publish/ directory. Why are we shipping
> something which is not for publishing in our binary package? I've also not
> heard of it before.
I think this was introduced in 2.8.0 as part of [1].
It is how the build process works by default and we just copy the enti
Hello!
+ 0.5
I have got it to run with the following command:
% COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30
Apache.Ignite.dll
I'm still confused by this publish/ directory. Why are we shipping
something which is not for publishing in our binary package? I've also not
heard of
Folks,
> Maxim, should we fix it and rebuild RC?
I've cherry-picked the [1] issue to the release branch. This will not
require rebuilding the RC since the issue is related to the
documentation task.
[1] https://issues.apache.org/jira/browse/IGNITE-15503
On Tue, 14 Sept 2021 at 12:37, Pavel Tupi
Ilya,
> When I have also installed 3.1 and 2.0
Please try .NET SDK 2.1 to run tests.
Yes, it went out of support last month, I've created a ticket [1].
> dotnet Apache.Ignite.dll
That's correct, but should be done
in platforms/dotnet/bin/netcoreapp2.0/publish, please try again.
We should deal wi
> check again, 15503 not cherry-pick, right?
Yes, the above ticket is not in the ignite-2.11 branch.
Maxim, should we fix it and rebuild RC?
вт, 14 сент. 2021 г. в 11:58, Ilya Kasnacheev :
> Hello!
>
> - 0.5
>
> Installed DEB package, built binary from source, ran sqlline, built .NET.
>
> I have
Hello!
- 0.5
Installed DEB package, built binary from source, ran sqlline, built .NET.
I have failed to run .NET tests though.
If I only install Current .NET, I get the following:
It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '2.0.0'
check again, 15503 not cherry-pick, right?
在 2021/9/14 15:55, Shishkov Ilya 写道:
Should the following two issue be merged into the ignite-2.11 branch?
Hi, as I see, both tickets are fixed in 2.10 and 2.11.
вт, 14 сент. 2021 г. в 04:13, 18624049226<18624049...@163.com>:
Should the following tw
> Should the following two issue be merged into the ignite-2.11 branch?
Hi, as I see, both tickets are fixed in 2.10 and 2.11.
вт, 14 сент. 2021 г. в 04:13, 18624049226 <18624049...@163.com>:
> Should the following two issue be merged into the ignite-2.11 branch?
>
> https://issues.apache.org/ji
Should the following two issue be merged into the ignite-2.11 branch?
https://issues.apache.org/jira/browse/IGNITE-14404
https://issues.apache.org/jira/browse/IGNITE-15503
在 2021/9/13 17:12, Pavel Tupitsyn 写道:
+1
Downloaded binary packages, started a cluster with a few nodes, tested new
.NET
+1
Downloaded binary packages, started a cluster with a few nodes, tested new
.NET examples.
On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky
wrote:
>
>
> Thanks Maxim !
> I tries to compare this ver with 2.10 (some performance tests with
> persistence and transactional\atomic payload) and s
Thanks Maxim !
I tries to compare this ver with 2.10 (some performance tests with persistence
and transactional\atomic payload) and seems all ok there.
+1 from me.
>
>
>Dear Community,
>
>
>The release candidate for the 2.11 version is ready.
>
>
>I have uploaded a release candidate to:
>https
Dear Community,
The release candidate for the 2.11 version is ready.
I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/
The following staging can be used for testing:
https://repos
28 matches
Mail list logo
