Re: [DISCUSSION] Common approach to print sensitive information

Ivan, I've been talking with different users from different industries and some of them(definitely not all of them) consider schema sensitive information. As a framework, that can be used by different types of users, we should cover this use case too. The solution, suggested by Ilya sounds very

[jira] [Created] (IGNITE-14482) Update the code snippet

Nikita Safonov created IGNITE-14482: --- Summary: Update the code snippet Key: IGNITE-14482 URL: https://issues.apache.org/jira/browse/IGNITE-14482 Project: Ignite Issue Type: Bug

Re: Azure Cloud IP Finder

Hello again! I re-checked our cloud discovery options by moving ignite-aws, ignite-gce, ignite-cloud directories from lib/optional to lib/ and trying to run Ignite with simple config taken from examples. The results are the following: ignite-aws seems to work (complains about unknown key)

[jira] [Created] (IGNITE-14481) Missing dependencies for JClouds discovery (ignite-cloud)

Ilya Kasnacheev created IGNITE-14481: Summary: Missing dependencies for JClouds discovery (ignite-cloud) Key: IGNITE-14481 URL: https://issues.apache.org/jira/browse/IGNITE-14481 Project: Ignite

Contributor grants request

Hello! Can I get contributor access? Task https://issues.apache.org/jira/browse/IGNITE-14474 -- Rodion Smolnikov +7(915)256-54-81 Software Developer, Russia *gridgain.com *

[jira] [Created] (IGNITE-14480) Add release notes for performance-statistics-ext, spring-data*-ext, spring-tx-ext extensions 1.0.0 version

Amelchev Nikita created IGNITE-14480: Summary: Add release notes for performance-statistics-ext, spring-data*-ext, spring-tx-ext extensions 1.0.0 version Key: IGNITE-14480 URL:

[jira] [Created] (IGNITE-14479) Add column default values support.

Andrey Mashenkov created IGNITE-14479: - Summary: Add column default values support. Key: IGNITE-14479 URL: https://issues.apache.org/jira/browse/IGNITE-14479 Project: Ignite Issue Type:

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Denis, If the initial release of some of the extension happens there is no need to release each time a new Ignite version is released (if there are no changes of a particular extension). So we should release the initial release as fast as possible and do the others according to needs. This is my

Re: Azure Cloud IP Finder

Hello! I'm not sure that I can see any attachment to your e-mail. Can you please re-send? We could have broken some of those, I guess, since we seem to not run integration tests for them. Regards, -- Ilya Kasnacheev пт, 2 апр. 2021 г. в 12:59, Atri Sharma : > Hello, > > Thank you for

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Hi Maxim, I would suggest we time a release of the Ignite core and the extensions in the future. As of now, I can't switch to Ignite 2.10 only due to the Spring Data module. Not the end of the world but delays the upgrade to the new version. - Denis On Mon, Apr 5, 2021 at 6:32 AM Maxim

[jira] [Created] (IGNITE-14478) Custom fork/Custom tests Documentation at README.MD

Anton Vinogradov created IGNITE-14478: - Summary: Custom fork/Custom tests Documentation at README.MD Key: IGNITE-14478 URL: https://issues.apache.org/jira/browse/IGNITE-14478 Project: Ignite

Re: [DISCUSSION] IgniteFuture class future in Ignite-3.0.

Hi Ivan, JDK flow API looks interesting. I think we should use it abroad. Though, Java 14 is not LTS (long-term support) release. I guess many users will prefer Java 15, but actually, we have no agreement about switching to Java 15 which may require some additional efforts. For now, we could

Re: [DISCUSSION] Common approach to print sensitive information

Ilya, great idea, but I suppose that third option is a little bit paranoid. But nevertheless, let it be, it's quite simple to implement it. пн, 5 апр. 2021 г. в 14:04, Ilya Kasnacheev : > Hello! > > I have two ideas here: > > - Let's have more than a single level of sensitive information

Re: [DISCUSSION] Common approach to print sensitive information

Taras, it's strange that table schema and binary object schema are considered sensitive information. I suppose, that current realization is what it is because of simplicity of implementation. I've never heard from any cybersecurity expert, that sql plan or table schema are personal or sensitive

Re: [DISCUSSION] Common approach to print sensitive information

Hello! I have two ideas here: - Let's have more than a single level of sensitive information withholding. Currently it is on/off, but I think we may need three levels: "print all", "print structure but not content", "print none". By structure I mean table/column/field names and data types. So we

[jira] [Created] (IGNITE-14477) Ducktape test of rebalance for persistent mode

Dmitriy Sorokin created IGNITE-14477: Summary: Ducktape test of rebalance for persistent mode Key: IGNITE-14477 URL: https://issues.apache.org/jira/browse/IGNITE-14477 Project: Ignite

[DISCUSSION] Common approach to print sensitive information

Hi, I work on ticket IGNITE-14441 [1] to hide sensitive information at the log messages produced by SQL. There are negative comments for the patch. I guess we have to produce view to work with sensitive information and make rules to define sensitive information. See on the usage of the

Re: [DISCUSS] Release performance-statistics-ext, spring-data-ext and spring-tx-ext Ignite extensions

Denis, There is no spring data artifact for the 2.10 release. We should prepare the release of these extensions as fast as possible. On Fri, 2 Apr 2021 at 20:06, Denis Magda wrote: > > Is this the first time we're releasing spring data 2.2 as an ext? Can't > find any version available for 2.10?

[jira] [Created] (IGNITE-14476) Get rid of using storage implementation explicitly in ConfigurationRoot annotation

Vladislav Pyatkov created IGNITE-14476: -- Summary: Get rid of using storage implementation explicitly in ConfigurationRoot annotation Key: IGNITE-14476 URL: https://issues.apache.org/jira/browse/IGNITE-14476

[jira] [Created] (IGNITE-14475) C++/dotnet query-example select result is various with additional node

Igor Sapego created IGNITE-14475: Summary: C++/dotnet query-example select result is various with additional node Key: IGNITE-14475 URL: https://issues.apache.org/jira/browse/IGNITE-14475 Project:

[jira] [Created] (IGNITE-14474) Improve error message in case rebalance fails

Denis Chudov created IGNITE-14474: - Summary: Improve error message in case rebalance fails Key: IGNITE-14474 URL: https://issues.apache.org/jira/browse/IGNITE-14474 Project: Ignite Issue

Re: [DISCUSSION] Java thin client: Continuous Queries public API

I do agree with your proposition, but the idea of an interface being exposed through documentation seems a bit clunky to me. On Mon, Apr 5, 2021 at 12:40 PM Alex Plehanov wrote: > > Hi Atri, > > The new interface is only needed for thin client, it's not a good idea to > add such a method to

Re: [DISCUSSION] Java thin client: Continuous Queries public API

Hi Atri, The new interface is only needed for thin client, it's not a good idea to add such a method to thick client too. пн, 5 апр. 2021 г. в 09:48, Atri Sharma : > Hi Alex, > > Sorry for the late reply. > > Regarding the thick client, would it be a challenge to add a new method > which takes

Re: [DISCUSSION] Java thin client: Continuous Queries public API

Hi Alex, Sorry for the late reply. Regarding the thick client, would it be a challenge to add a new method which takes takes interface as parameter? That will not break the back compatible On Fri, 2 Apr 2021, 14:32 Alex Plehanov, wrote: > Hello, Atri > > 1. ClientChannelDisconnectListener is

Re: [DISCUSSION] Java thin client: Continuous Queries public API

Pavel, Ok, I agree. пт, 2 апр. 2021 г. в 18:47, Pavel Tupitsyn : > Alex, > > 1. Agree to deal with CacheEntryEvent as explained > 2. ClientChannelDisconnectListener - can we have an overload with a > parameter of this type? > > ClientCache#query(ContinuousQuery) - compatible with Thick API >