Hello, Igniters!
The Ignite Spark 2.0.0 RC1 and Ignite Spark 3.0.0 RC1 extensions have been
accepted.
5 - "+1" votes received.
Here are the +1 votes received:
- Nikita Amelchev
- Andrey Gura (binding)
- Maxim Muzafarov (binding)
- Pavel Tupitsyn (binding)
- Slava Koptilin (binding)
Here is
Dear Community,
The release candidates are ready.
These are new Ignite Spark integrations based on Spark 2.4 and 3.2 dependencies
respectively.
See the links below.
== Ignite Spark Extension Module 2.0.0 ==
The release candidate is uploaded to:
ibernate-ext-5.1.0
>
> On Mon, 7 Nov 2022 at 08:15, Ivan Gagarkin wrote:
>>
>> Hi Alexandr,
>> I would be glad if you can.
>> Not sure about all information. Vladimir Pligin has more details.
>> Right, no progress.
>>
>> On Fri, 4 Nov 2022 a
Hi Ivan,
I’d like to help with that. Is all release-related information described in the
DEVNOTES?
I suppose there has not been any progress on the release since your initial
message, correct?
> On 26 Oct 2022, at 09:05, Ivan Gagarkin wrote:
>
> Hi, Igniters
> ignite-spark3.2-ext is ready
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
Hello!
It looks like not all extensions have been published for the time being. This
is somewhat important with respect to the new Ignite 2.11 release which doesn’t
have corresponding extensions, in particular - ignite-spring-tx-ext meaning
that official documentation [1] is lying a bit.
[1]
Alexandr Shapkin created IGNITE-14324:
-
Summary: EVT_CLIENT_NODE_DISCONNECTED is not triggered in k8s
Key: IGNITE-14324
URL: https://issues.apache.org/jira/browse/IGNITE-14324
Project: Ignite
Alexandr Shapkin created IGNITE-13822:
-
Summary: NPE in SQL query [with xxx as (select xxx)]
Key: IGNITE-13822
URL: https://issues.apache.org/jira/browse/IGNITE-13822
Project: Ignite
Alexandr Shapkin created IGNITE-13453:
-
Summary: Docker: Change run.sh to call java directly
Key: IGNITE-13453
URL: https://issues.apache.org/jira/browse/IGNITE-13453
Project: Ignite
Alexandr Shapkin created IGNITE-13160:
-
Summary: .NET: wrong affinity key registration with
AffinityKeyMapped attribute
Key: IGNITE-13160
URL: https://issues.apache.org/jira/browse/IGNITE-13160
Alexandr Shapkin created IGNITE-12385:
-
Summary: .NET Thin Client: introduce ClusterGroup API
Key: IGNITE-12385
URL: https://issues.apache.org/jira/browse/IGNITE-12385
Project: Ignite
Alexandr Shapkin created IGNITE-12381:
-
Summary: QueryParser: propagate H2 ErrorCode to IgniteSQLException
Key: IGNITE-12381
URL: https://issues.apache.org/jira/browse/IGNITE-12381
Project: Ignite
millisecond precision for expiration, so we could
pass seconds as float values (3*4 bytes).
Thoughts?
On Fri, Oct 18, 2019 at 8:21 PM Alexandr Shapkin wrote:
> Pavel,
>
> Thanks for sharing your thoughts.
>
> Right now I see that 2 reserved bytes come with every cache request:
>
GridGain had released new documentation just a couple of weeks ago.
It should contain updated content with multilanguage examples.
Feel free to review the same article regarding eviction policies [1]
[1]
https://www.gridgain.com/docs/8.7.6/developers-guide/memory-architecture/eviction-policies
any parameters, so they carry only 1
bit of information.
https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients
On Fri, Oct 18, 2019 at 5:14 PM Alexandr Shapkin wrote:
> Igniters,
>
> I would like to add WithExpirePolicy support to thin
Igniters,
I would like to add WithExpirePolicy support to thin clients. [1]
For a thick client, we can obtain a reference to a cache wrapper instance and
use cache API through it. At the same time, the thin client protocol is
stateless, we do not hold a reference to a cache but rather a cache
Alexandr Shapkin created IGNITE-12293:
-
Summary: .NET thin client: config serialization should use OpCodes
Key: IGNITE-12293
URL: https://issues.apache.org/jira/browse/IGNITE-12293
Project: Ignite
Alexandr Shapkin created IGNITE-12177:
-
Summary: CPP: Add Java compute support
Key: IGNITE-12177
URL: https://issues.apache.org/jira/browse/IGNITE-12177
Project: Ignite
Issue Type
Hello,
Please, send an email to user-unsubscr...@ignite.apache.org and
dev-unsubscr...@ignite.apache.org
More details https://ignite.apache.org/community/resources.html#mail-lists
From: Deepa Kolwalkar
Sent: Monday, September 16, 2019 12:37 PM
To: u...@ignite.apache.org;
(Time, Scope, and Release manager)
Alexandr,
I almost sent the vote email :) When do you expect the fix to be in master
and 2.7.6?
ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin :
> Folks,
>
> A critical bug was detected in .NET [1].
>
> I understand that it’s a little bit late
Folks,
A critical bug was detected in .NET [1].
I understand that it’s a little bit late, but I propose to include this issue
into the release scope.
PR is ready, currently waiting for a TC visa.
Thoughts?
[1] - https://issues.apache.org/jira/browse/IGNITE-12163
From: Alexey Goncharuk
Alexandr Shapkin created IGNITE-12163:
-
Summary: CacheEntryEventType.Removed is not being rised
Key: IGNITE-12163
URL: https://issues.apache.org/jira/browse/IGNITE-12163
Project: Ignite
Alexandr Shapkin created IGNITE-11999:
-
Summary: .NET unable to specify JvmDllPath for standalone node
Key: IGNITE-11999
URL: https://issues.apache.org/jira/browse/IGNITE-11999
Project: Ignite
Alexandr Shapkin created IGNITE-11984:
-
Summary: .NET CompiledQuery won't work with strings
Key: IGNITE-11984
URL: https://issues.apache.org/jira/browse/IGNITE-11984
Project: Ignite
>1) Declaring older versions of Ignite.
>2) Is it correct to mention that Ignite uses .NET core controlled by .NET
>Foundation? E.g. as follows:
>(controlled by)
>.NET Foundation
>title=Designed to use .NET Framework Cryptography Model
>href=https://dotnetfoundation.org/projects
>Should it go
Alexandr Shapkin created IGNITE-11895:
-
Summary: .NET Resharper inspections got broken after update
Key: IGNITE-11895
URL: https://issues.apache.org/jira/browse/IGNITE-11895
Project: Ignite
Alexandr Shapkin created IGNITE-11893:
-
Summary: .NET enum platform compatibility
Key: IGNITE-11893
URL: https://issues.apache.org/jira/browse/IGNITE-11893
Project: Ignite
Issue Type
Alexandr Shapkin created IGNITE-11805:
-
Summary: .NET runnable core executable
Key: IGNITE-11805
URL: https://issues.apache.org/jira/browse/IGNITE-11805
Project: Ignite
Issue Type: New
Alexandr Shapkin created IGNITE-11709:
-
Summary: .NET thin client: introduce ClusterGroup methods
Key: IGNITE-11709
URL: https://issues.apache.org/jira/browse/IGNITE-11709
Project: Ignite
Alexandr Shapkin created IGNITE-11690:
-
Summary: .NET: Cache iteration hangs with enabled
peerAssemblyLoading
Key: IGNITE-11690
URL: https://issues.apache.org/jira/browse/IGNITE-11690
Project
Hello Ignite Community!
My name is Alexandr Shapkin. I want to contribute to Apache Ignite, my JIRA
username is ashapkin.
Thanks!
31 matches
Mail list logo