[jira] [Created] (IGNITE-14264) Ignite extensions: Ignite client cache manager may create cache with incorrect name

Mikhail Petrov created IGNITE-14264: --- Summary: Ignite extensions: Ignite client cache manager may create cache with incorrect name Key: IGNITE-14264 URL: https://issues.apache.org/jira/browse/IGNITE-14264

[jira] [Created] (IGNITE-14265) Python thin: Support passwords for certificates

Igor Sapego created IGNITE-14265: Summary: Python thin: Support passwords for certificates Key: IGNITE-14265 URL: https://issues.apache.org/jira/browse/IGNITE-14265 Project: Ignite Issue Typ

Allow arrays in node attributes for thin clients

Hi guys! We have a restriction to filter array values from node attributes if it is not "org.apache.ignite.features" (GridTopologyCommandHandler.java:313). It will be useful to allow arrays for any attribute with suffix ".features" for external modules. Otherwise, these attributes are not allowed

[jira] [Created] (IGNITE-14266) System views for page statistics must include the bucktes sizes

Maxim Muzafarov created IGNITE-14266: Summary: System views for page statistics must include the bucktes sizes Key: IGNITE-14266 URL: https://issues.apache.org/jira/browse/IGNITE-14266 Project: Ig

Re: Allow arrays in node attributes for thin clients

I think we agreed to make thin client attributes String-only [1] However, this does not seem to be the case right now. Anyway, I'd like to avoid complicating the protocol even further with magic suffixes. Can we simply use a String instead of an array? [1] http://apache-ignite-developers.2346864.

Adding metrics of using WAL archive

Hi, Nikolay! I thought about your proposal and offer the following two metrics: 1)The number of bytes logged to the WAL; 2)The number of compressed bytes in the WAL. Monotonically increasing long. WDYT?

Re: Allow arrays in node attributes for thin clients

OK, I got it. Yes, we can use String instead. вт, 2 мар. 2021 г. в 18:27, Pavel Tupitsyn : > I think we agreed to make thin client attributes String-only [1] > However, this does not seem to be the case right now. > > Anyway, I'd like to avoid complicating the protocol even further with magic > s

Re: Adding metrics of using WAL archive

+1 For this. > 2 марта 2021 г., в 18:32, ткаленко кирилл написал(а): > > Hi, Nikolay! > > I thought about your proposal and offer the following two metrics: > > 1)The number of bytes logged to the WAL; > 2)The number of compressed bytes in the WAL. > > Monotonically increasing long. > > WDYT

[jira] [Created] (IGNITE-14267) Cluster snapshot must support encrypted caches

Maxim Muzafarov created IGNITE-14267: Summary: Cluster snapshot must support encrypted caches Key: IGNITE-14267 URL: https://issues.apache.org/jira/browse/IGNITE-14267 Project: Ignite Iss

[jira] [Created] (IGNITE-14268) [Ignite Website] Content updates 2021-03-02

Kseniya Romanova created IGNITE-14268: - Summary: [Ignite Website] Content updates 2021-03-02 Key: IGNITE-14268 URL: https://issues.apache.org/jira/browse/IGNITE-14268 Project: Ignite Issu

Hello

Hello everyone, My name is Michele Caputo and I would like to contribute to the Apache Ignite project. I am a Software Engineer, in my previous experience I worked as a full stack developer from IoT to frontend. My preference was definitely for the backend (experience in C#), DB (Oracle, SQL S

[MTCGA]: new failures in builds [5894444] needs to be handled

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 TxWithKeyContentionSelfTest.testOptimisticRepeatableReadCheckContentionTxMetricNear https://ci.ignite.apache.org/project.html?projectId=IgniteTes

Re: Hello

Hello Michele, Welcome to the community! I've added you to the contributors' list in JIRA, so go ahead and take over a ticket you're interested in: https://ignite.apache.org/community/contribute.html Speaking about Java vs Python contributions, we've been improving the Python thin client

[MTCGA]: new failures in builds [5897750] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master-nightly IgniteDbMemoryLeakWithExpirationTest.testMemoryLeak https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-743543135078

[jira] [Created] (IGNITE-14269) Design conditional multi update functionality for meta storage client

Andrey N. Gura created IGNITE-14269: --- Summary: Design conditional multi update functionality for meta storage client Key: IGNITE-14269 URL: https://issues.apache.org/jira/browse/IGNITE-14269 Project

[jira] [Created] (IGNITE-14270) Remove "project" param from Ducktape Specs.

Maksim Timonin created IGNITE-14270: --- Summary: Remove "project" param from Ducktape Specs. Key: IGNITE-14270 URL: https://issues.apache.org/jira/browse/IGNITE-14270 Project: Ignite Issue Ty