Semen Boikov created IGNITE-12005:
-
Summary: AssertionError when put/get byte arrays in cache
Key: IGNITE-12005
URL: https://issues.apache.org/jira/browse/IGNITE-12005
Project: Ignite
Issue T
Huzzah!
From: Dmitriy Pavlov
Sent: Monday, July 22, 2019 6:54 AM
To: dev ; user ;
annou...@apache.org
Subject: [ANNOUNCE] Apache Ignite 2.7.5 Released
The Apache Ignite Community is pleased to announce the release of Apache Ignite
2.7.5.
Apache Ignite [1] is a memory-centric distributed datab
Igniters,
I did the first run through the wishlist and selected integrations and APIs
for discontinuation. My suggestion would be to use IEP-36 (Modularization)
page for the final list that we'll send to the user list for feedback:
- Integrations for discontinuation:
https://cwiki.apache.o
Hi Sercan,
Apache Ignite is an open-source product, it is licensed under Apache
License 2.0, as all Apache products. You can find full license text here
https://github.com/apache/ignite/blob/master/LICENSE (with notice related
to dependencies licenses here
https://github.com/apache/ignite/blob/mas
Ignite is an open-source project and doesn't have any licenses. You can use
it for free the way you like.
As for a relation DB acceleration, please refer to these docs:
https://apacheignite.readme.io/docs/3rd-party-store
-
Denis
On Mon, Jul 22, 2019 at 11:35 AM Sercan DURSUN <
sercan.dur...@vat
Hi,
I have some questions about apache-ignite licensing and product editions. We
are planning to create a cluster cache with two servers We will use these cache
system to get high performance with web servers. We are planning to use
Distributed-SQL and Distributed Key Value features of apache-
Denis, I'm will make my best to contribute till October:
* IEP-39. Monitoring&Profiling. Phase2: Framework for observing
lists of Ignite objects(services, caches, jobs, etc.)
* IEP-39. Monitoring&Profiling. Phase3: Watchdog for user
provided code.
В Пн, 22/07/2019 в
Igniters,
How about doing this release in October? There are many bug fixes plus by
that time we should be able to roll out our new metrics framework. Nickolay
what do you think about the latter?
-
Denis
On Mon, Jul 22, 2019 at 9:41 AM Nikolay Izhikov wrote:
> Hello, Akhil.
>
> There are no s
Hi, igniters!
In the context of IEP-30 and IGNITE-10958 in particular [1], the JUnit5
tests are going to appear in master.
During migration Ignite on JUnit5 I faced that the test naming will be
changed.
The names are different, in the version before path consists from "path to
suite: path to test
Hello, Akhil.
There are no specific dates for now.
But, as always, you can easily build distr from sources.
We try to keep Ignite master release ready.
пн, 22 июля 2019 г., 19:37 apada...@kent.edu :
> Hello Ignite team ,
> I am looking for 2.8 version release, specifically for automatic baselin
Hello Ignite team ,
I am looking for 2.8 version release, specifically for automatic baseline
topology adjustment enhancement.
https://issues.apache.org/jira/browse/IGNITE-8571
please let me know when will 2.8 version with IGNITE-8571 is going to
release.
Thanks
Akhil
--
Sent from: http://apa
Ivan Pavlukhin created IGNITE-12004:
---
Summary:
CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields is flaky
Key: IGNITE-12004
URL: https://issues.apache.org/jira/browse/IGNITE-12004
Projec
Ivan Pavlukhin created IGNITE-12003:
---
Summary: Java thin client fails to get object with compact footer
from cache
Key: IGNITE-12003
URL: https://issues.apache.org/jira/browse/IGNITE-12003
Project:
Great news! Go forward to 2.8! or more, to 3.0!
пн, 22 июл. 2019 г. в 14:54, Dmitriy Pavlov :
> The Apache Ignite Community is pleased to announce the release of Apache
> Ignite 2.7.5.
>
> Apache Ignite [1] is a memory-centric distributed database, caching,
> and processing platform for transacti
+1 for moving from RunAll to RunAllNighlty
пн, 22 июл. 2019 г. в 12:21, Павлухин Иван :
> Igniters,
>
> As you know Ignite RunAll on TC takes significant resources. I noticed
> that build job "Queries (Binary Objects Simple Mapper)" [1] actually
> duplicates "Queries 1" [2] job and the same test
The Apache Ignite Community is pleased to announce the release of Apache
Ignite 2.7.5.
Apache Ignite [1] is a memory-centric distributed database, caching,
and processing platform for transactional, analytical, and streaming
workloads delivering in-memory speeds at petabyte scale.
This release in
Philippe Anes created IGNITE-12002:
--
Summary: [TTL] Some expired data remains in memory even with eager
TTL enabled
Key: IGNITE-12002
URL: https://issues.apache.org/jira/browse/IGNITE-12002
Project:
Igniters,
As you know Ignite RunAll on TC takes significant resources. I noticed
that build job "Queries (Binary Objects Simple Mapper)" [1] actually
duplicates "Queries 1" [2] job and the same test set using simple name
mapper for binary objects. I suppose that we can exclude it from daily
RunAll
Ivan, NIkita
"test still fails with LWM > HWM assertion"
I recently did some fixed on this in GridGain CE but still not donated to
Apache. Currently I'm on vacation and have plans to donate in the start of
August.
"How do you think, does this problem looks solvable? "
Looks like it's impossible
I think all agreed items should be marked @Deprecated in the code
base, so we will be able to remove them transparently for the
end-users.
On Mon, Jul 22, 2019 at 9:32 AM Павлухин Иван wrote:
>
> Alex,
>
> I already added a couple of items to wishlist [1].
>
> Yes, I agree that the process should
20 matches
Mail list logo
