Hello, Alexey.
I suggest adding to the 2.11 scope the resolved issue [1]. It fixes
incorrect values of cache, cache groups, data region metrics after
cluster reactivation.
WDYT?
[1] https://issues.apache.org/jira/browse/IGNITE-14990
вт, 29 июн. 2021 г. в 15:09, Alexey Gidaspov :
>
> Ok, we can a
Hi, Nikita!
I think it's important fix and should be included in 2.11 release. I've tagged
ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11 branch? And
please fill release notes or delete flag.
On 2021/06/30 07:55:04, Nikita Amelchev wrote:
> Hello, Alexey.
>
> I suggest a
Hi Pavel,
2. Schema and its version are internal things and shouldn't be exposed,
otherwise, eventually, it will lead to the user will manage schemas
manually on his side for some purposes.
This will force us to bother about interfaces/contracts and compatibility
aspects in the future with uncerta
Thanks! I have cherry-picked the commit to the 2.11 branch.
ср, 30 июн. 2021 г. в 11:00, Alexey Gidaspov :
>
> Hi, Nikita!
>
> I think it's important fix and should be included in 2.11 release. I've
> tagged ticket by fixVersion 2.11. Can you cherry-pick it to ignite-2.11
> branch? And please fi
Folks,
Permission to create and configure the extensions
release project can't be granted to me. I have created the issue [1].
Petr, could you take a look, please?
I think we can start RC5 now and use TC with the next an extension release.
[1] https://issues.apache.org/jira/browse/IGNITE-15032
Dear Ignite Community,
I have uploaded a release candidate of the performance-statistics-ext
extension module.
The release candidate of the performance-statistics-ext extension:
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-performance-statistics-ext/1.0.0-rc5/
The instr
Dear Ignite Community,
I have uploaded a release candidate of the following extension modules:
spring-data-commons
spring-data-ext
spring-data-2.0-ext
spring-data-2.2-ext
The release candidate of the extensions:
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-a
+1
Check sha512, sign of archives and versions of released artifacts.
Check licenses with "mvn validate -DskipTests -P check-licenses"
Build modules from the source with Java 8
Run examples:
from modules/spring-data-2.0-ext/examples with artifacts: Ignite
v2.10.0/ignite-spring-data-2.0-ext v1.0.0/
Hi Andrey,
> This will force us to bother about interfaces/contracts and compatibility
> aspects in the future
Schemas and versions are part of thin client wire protocol.
This protocol is a public API - we'll have to care about compatibility
anyway.
Schema evolution is an important feature that
Hey Ilya
It's the data tables that keep growing not the WAL.
We will try to rebuild the cache and see if that fixes the issue
On Mon, Jun 28, 2021 at 8:46 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Is it WAL (wal/) that is growing or checkpoint space (db/)? If latter, any
> specific caches that are
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
CacheExchangeMergeTest.testJoinExchangeCoordinatorChange_NoMerge_2
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testName
Hi All,
I have been playing around with Collision SPI and specifically used
FifoQueueCollisionSPI and noticed that it is not really adhering to
the specified task of restricting the number of concurrent tasks that
can be run.
Specifically, if there is only one slot available and N tasks
concurren
Igniters,
I'm happy to announce that Ignite 3 project reached a significant
milestone, as we release the 2nd alpha version of the product.
On top of the functionality that was previously released, Alpha 2 adds
the following major features:
- Replication infrastructure based on Raft.
- New in-memo
Hi Igniters,
This feature [1, 2] prevents logging of the VM arguments when
IGNITE_TO_STRING_INCLUDE_SENSITIVE option is set to false. Till now, method
IgniteKernal#ackVmArguments remains mostly the same [3].
Is this behaviour actual now? Often, we should be able to get from logs the
actual VM opt
Pavel,
Thanks for your response, makes sense.
Regarding the values() method: I would instead add the required methods to
the Tuple itself. E.g., it can implement Iterable, and additionally have
the value(int index) method, plus anything else that we might need.
I don't like returning a collection
Hello, Alexey!
Is it possible to add system views for BaselineNode attributes [1] and
corresponding documentation [2] to 2.11?
1. https://issues.apache.org/jira/browse/IGNITE-15007
2. https://issues.apache.org/jira/browse/IGNITE-15028
ср, 30 июн. 2021 г. в 11:07, Nikita Amelchev :
> Thanks! I ha
+1
Checked a report with an ignite-performance-statistics-example.
--
Best regards,
Sergei Ryzhov
+1
Building modules from source and running tests successfully on Java 8
ср, 30 июн. 2021 г. в 16:02, Alex Plehanov :
> +1
>
> Check sha512, sign of archives and versions of released artifacts.
> Check licenses with "mvn validate -DskipTests -P check-licenses"
> Build modules from the source with
+1
Checked on Ubuntu 20.04. Created separate Spring Applications for each
version of Spring Data Integrations using the Maven RC repository and
following the documentation. Tested common use cases. Checked archive
signs. Built from the sources.
On 01.07.2021 00:31, Sergei Ryzhov wrote:
+1
B
I suppose, that we should revert this particular line. I don't understand
who ever considers vm options as sensitive info.
ср, 30 июн. 2021 г., 22:52 Shishkov Ilya :
> Hi Igniters,
>
> This feature [1, 2] prevents logging of the VM arguments when
> IGNITE_TO_STRING_INCLUDE_SENSITIVE option is set
+1
Checked on Ubuntu 20.04. Checked built-report and print-statistics
scripts for the custom Ignite application. Checked archive signs. Built
from the sources.
On 01.07.2021 00:24, Sergei Ryzhov wrote:
+1
Checked a report with an ignite-performance-statistics-example.
+1 for reverting, can anybody (possibly ticket starter?) explain how jvm
settings will rise some security problems ?
>I suppose, that we should revert this particular line. I don't understand
>who ever considers vm options as sensitive info.
>
>ср, 30 июн. 2021 г., 22:52 Shishkov Ilya < shish
22 matches
Mail list logo