11:30 AM Vladimir Steshin
wrote:
Mikhail, congratulations!
11.11.2022 11:20, Maxim Muzafarov пишет:
The Project Management Committee (PMC) for Apache Ignite has invited
Mikhail Petrov to become a committer and we are pleased to announce
that they have accepted.
Mikhail Petrov is an active
e versions, and put
tags for already released versions.
According to [5] 1.0 and 2.0 versions are no longer supported
According to this 2.2 isn't supported too, the last release was a year ago,
is it? Do we have plans to support spring-data with the latest version?
On Fri, Feb 18, 2022 at 1
Igniters,
Currently, we have three separate modules for Ignite Spring Data
integrations - [1 - 3]. Each of them depends on the specific version of
the Spring Data - 1.0, 2.0, and 2.2, respectively.
I propose to:
1. remove extension modules that are tied to the specific Spring Data
versions
Thank you all for your replies!
I got the idea and agreed with it. Based on the results of the
discussion, I have filed a ticket [1].
I will try to investigate it.
[1] - https://issues.apache.org/jira/browse/IGNITE-16157
On 16.12.2021 20:11, Ivan Daschinsky wrote:
Andrey, agree with you, good
ncoded
in
UTF-8?
AFAIK multi OS cluster is a quite common case.
пн, 13 дек. 2021 г. в 11:36, Mikhail Petrov
:
Igniters,
Recently we faced the problem that if the cluster consists of
nodes
running in the JVM with different encodings, many issues arise.
The root cause of the mentioned issues
common case.
пн, 13 дек. 2021 г. в 11:36, Mikhail Petrov :
Igniters,
Recently we faced the problem that if the cluster consists of nodes
running in the JVM with different encodings, many issues arise.
The root cause of the mentioned issues is components that use
`String#getBytes()` and `new
Igniters,
Recently we faced the problem that if the cluster consists of nodes
running in the JVM with different encodings, many issues arise.
The root cause of the mentioned issues is components that use
`String#getBytes()` and `new String()`, which relies on the
system default encoding. Thus,
Igniters,
it seems that issues [1] and [2] that were discovered recently are
blockers for the 2.12 release.
[1] https://issues.apache.org/jira/browse/IGNITE-15951
[2] https://issues.apache.org/jira/browse/IGNITE-15966
On 22.11.2021 11:04, Nikolay Izhikov wrote:
Hello.
One more tiny fix that
Ilya, thank you for your comments.
The documentation has been updated according to your suggestions - [1].
The Spring Cache and Spring Transactions integrations have now been
restricted to use with Ignite only since version 2.11 (the spring-tx and
spring-cache integration classes were migrated
Ilya, for Ignite 2.10 versions and earlier spring-tx and spring-cache
integrations are stored in the ignite-spring module. Initially, there
were no dedicated modules for them. As I see, we cannot fully migrate
the ignite-spring module as it is responsible for parsing Ignite XML
configurations a
Igniters, I propose to migrate CacheSpringStoreSessionListener to
ignite-extensions in the ignite-spring-tx module as part of Spring
Transactions integration migration. It also helps to
1. Make the ignite-spring module responsible only for parsing XML
configurations.
2. Reduce the number of depe
+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.
On 25.06.2021 12:43, Nikita Amelchev wrote:
Dear Ignite Community,
I have uploaded a release
+1
I created separate Spring Applications for each version of Spring Data
Integration using the RC repository and following the documentation. And
tested common use cases.
On 14.05.2021 15:39, Nikita Amelchev wrote:
How do I actually run these examples?
Use the 'examples' maven profile, ple
Hello, Ilya.
As I understand it, Spring Data integration dependencies of the current
RC are stored in the repository referenced in the original email. To
download Spring Data dependencies with maven, you need to set up an
external repository in your application pom file using the specified
Mikhail Petrov created IGNITE-14616:
---
Summary: eplace the string variables that store the security
password with array of char.
Key: IGNITE-14616
URL: https://issues.apache.org/jira/browse/IGNITE-14616
Mikhail Petrov created IGNITE-14615:
---
Summary: Add support of grant/revoke commands for Ignite security
plugin
Key: IGNITE-14615
URL: https://issues.apache.org/jira/browse/IGNITE-14615
Project
Mikhail Petrov created IGNITE-14614:
---
Summary: Add the ability to create security user with custom
options
Key: IGNITE-14614
URL: https://issues.apache.org/jira/browse/IGNITE-14614
Project: Ignite
Igniters,
Changing the scope of Spring dependencies to "provided" in Ignite Spring
extensions does not currently work as expected:
some versions of Spring that a user can specify via maven configuration
for Spring extensions may conflict with the hard-coded version of Spring
dependencies that
Hello, Igniters.
I faced the following problem with the metrics - JmxMetricExporter fails
to export discovery metrics (ticket - [1]).
The main reason: JMX exporter assumes that each metric name must start
with the name of the registry it belongs to, but discovery metrics do
not obey this nam
Mikhail Petrov created IGNITE-14493:
---
Summary: Documents versions of Spring integration extensions.
Key: IGNITE-14493
URL: https://issues.apache.org/jira/browse/IGNITE-14493
Project: Ignite
Mikhail Petrov created IGNITE-14434:
---
Summary: Add examples of thin client using with spring-tx-ext
Key: IGNITE-14434
URL: https://issues.apache.org/jira/browse/IGNITE-14434
Project: Ignite
Mikhail Petrov created IGNITE-14428:
---
Summary: Formalize the names of the metrics included in the
metric registry.
Key: IGNITE-14428
URL: https://issues.apache.org/jira/browse/IGNITE-14428
Project
Mikhail Petrov created IGNITE-14399:
---
Summary: Document thin client support for spring-cache integration.
Key: IGNITE-14399
URL: https://issues.apache.org/jira/browse/IGNITE-14399
Project: Ignite
Mikhail Petrov created IGNITE-14398:
---
Summary: Document thin client support for spring-data integration.
Key: IGNITE-14398
URL: https://issues.apache.org/jira/browse/IGNITE-14398
Project: Ignite
Mikhail Petrov created IGNITE-14397:
---
Summary: Document spring-transactions integration.
Key: IGNITE-14397
URL: https://issues.apache.org/jira/browse/IGNITE-14397
Project: Ignite
Issue
haviour or do we need such
behaviour at all?
On Mon, 22 Mar 2021 at 13:34, Nikolay Izhikov wrote:
Hello, Mikhail.
I'm +1 to follow your suggestion.
чт, 18 мар. 2021 г. в 17:53, Mikhail Petrov :
Hello, Igniters.
As of now, there are two independent APIs related to security:
1. IgniteSe
Mikhail Petrov created IGNITE-14376:
---
Summary: JmxMetricExporter fails to export discovery metrics
Key: IGNITE-14376
URL: https://issues.apache.org/jira/browse/IGNITE-14376
Project: Ignite
Hello, Igniters.
As of now, there are two independent APIs related to security:
1. IgniteSecurity - handle node/client authentication and authorize all
operations.
2. IgniteAuthenticationProcessor - handle authentication of thin clients
only.
The main purpose of creating the IgniteAuthenticat
Mikhail Petrov created IGNITE-14335:
---
Summary: Merge APIs of IgniteAuthenticationProcessor and
IgniteSecurity
Key: IGNITE-14335
URL: https://issues.apache.org/jira/browse/IGNITE-14335
Project
Mikhail Petrov created IGNITE-14301:
---
Summary: Authentication processor can hang all user management
operation after server node reconnect
Key: IGNITE-14301
URL: https://issues.apache.org/jira/browse/IGNITE
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
Mikhail Petrov created IGNITE-14257:
---
Summary: Add copy constructor to ClientCacheConfiguration
Key: IGNITE-14257
URL: https://issues.apache.org/jira/browse/IGNITE-14257
Project: Ignite
Mikhail Petrov created IGNITE-14251:
---
Summary: Ignite extension: refactor usage of proxy classes and
their names
Key: IGNITE-14251
URL: https://issues.apache.org/jira/browse/IGNITE-14251
Project
Mikhail Petrov created IGNITE-14249:
---
Summary: Ignite extensions: Flaky
IgniteSourceConnectorTest.testEventsInjectedIntoKafkaWithoutFilter test
Key: IGNITE-14249
URL: https://issues.apache.org/jira/browse
Mikhail Petrov created IGNITE-14213:
---
Summary: Ignite extensions: javadoc ignitelink tag is unsupported
Key: IGNITE-14213
URL: https://issues.apache.org/jira/browse/IGNITE-14213
Project: Ignite
.
About flakiness — send me link to build where problem is, I will try to
investigate.
On 10 Feb 2021, at 11:17, Mikhail Petrov wrote:
Petr, ticket [1] was merged to the master branch. TC build is ok now - [2].
Sometimes i faced that some tests can be flaky because test nodes were trying
=IgniteExtensions_Tests&branch_IgniteExtensions_Tests=%3Cdefault%3E
On 10.02.2021 10:40, Petr Ivanov wrote:
I've updated Extensions template to use only Linux agents.
Will wait for ticket in master, thanks!
On 10 Feb 2021, at 01:05, Mikhail Petrov wrote:
Hi, Petr.
It seems that the problem
Hi, Petr.
It seems that the problem is in an outdated version of the maven
surefire plugin that is used in ignite-extensions.
I created the corresponding ticket [1].
I also faced that current ignite-extensions build is broken on windows
agents - [2]. It fails with the following error:
/[22
Mikhail Petrov created IGNITE-14150:
---
Summary: Update version of surefire plugin in ignite-extensions
Key: IGNITE-14150
URL: https://issues.apache.org/jira/browse/IGNITE-14150
Project: Ignite
Mikhail Petrov created IGNITE-14146:
---
Summary: Migrate Spring Cache integration to igntie-extensions
Key: IGNITE-14146
URL: https://issues.apache.org/jira/browse/IGNITE-14146
Project: Ignite
repository.
This is done for ability to test new features in extensions against
non-published changes in main project.
[1]
https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_SpringTransactions/5857868
On 5 Feb 2021, at 12:51, Mikhail Petrov wrote:
Hi, Petr.
PR with new
of tests for extensions.
I will refactor that project in couple of days and add suite for your extension
too.
On 28 Jan 2021, at 16:34, Mikhail Petrov wrote:
Petr, I planned to copy the existing ignite-extensions build configuration and
change its parameters [1] to add a new module and test
/IgniteExtensions_Tests?mode=builds
On 28 Jan 2021, at 15:34, Mikhail Petrov wrote:
Igniters,
I am currently working on the migration of the Spring Transactions integration
to a separate ignite-extensions module - [1]. I need to create a debug
ignite-extensions build on TC with the migrated test suite
Igniters,
I am currently working on the migration of the Spring Transactions
integration to a separate ignite-extensions module - [1]. I need to
create a debug ignite-extensions build on TC with the migrated test
suite included, making sure the new tests are ok. Can anyone help me get
the req
Mikhail Petrov created IGNITE-14030:
---
Summary: Java thin client: Add containsKeys, clearKey, clearKeys
and getAndPutIfAbsent operations to API
Key: IGNITE-14030
URL: https://issues.apache.org/jira/browse/IGNITE
Mikhail Petrov created IGNITE-14015:
---
Summary: Tracing SQL: tracing of SELECT queries causes incorrect
span inheritance
Key: IGNITE-14015
URL: https://issues.apache.org/jira/browse/IGNITE-14015
Mikhail Petrov created IGNITE-14013:
---
Summary: Add documentation for node validation failed event
Key: IGNITE-14013
URL: https://issues.apache.org/jira/browse/IGNITE-14013
Project: Ignite
Mikhail Petrov created IGNITE-14010:
---
Summary: Ignite-extensions: KafkaIgniteSteamerSelfTest is flaky
Key: IGNITE-14010
URL: https://issues.apache.org/jira/browse/IGNITE-14010
Project: Ignite
Mikhail Petrov created IGNITE-14009:
---
Summary: Ignite-extensions: PubSubStreamerSelfTest is flaky
Key: IGNITE-14009
URL: https://issues.apache.org/jira/browse/IGNITE-14009
Project: Ignite
Mikhail Petrov created IGNITE-14007:
---
Summary: Ignite-extensions: ignite-kafka integration test suite
fails TC build
Key: IGNITE-14007
URL: https://issues.apache.org/jira/browse/IGNITE-14007
Mikhail Petrov created IGNITE-14006:
---
Summary: Node fails with assertion error during event listener
registration
Key: IGNITE-14006
URL: https://issues.apache.org/jira/browse/IGNITE-14006
Project
Mikhail Petrov created IGNITE-13993:
---
Summary: Ignite-extensions: Change version of Ignite dependency to
2.11.0
Key: IGNITE-13993
URL: https://issues.apache.org/jira/browse/IGNITE-13993
Project
Mikhail Petrov created IGNITE-13992:
---
Summary: Migrate spring-transactions integration to
ignite-extensions
Key: IGNITE-13992
URL: https://issues.apache.org/jira/browse/IGNITE-13992
Project: Ignite
Igniters,
I propose to migrate the Spring Transactions [1] and Spring Cache [2]
integrations, that are currently stored in the ignite-spring module [3],
to the ignite-extensions repository and split them as two separate
modules - ignite-spring-transactions-ext and ignite-spring-cache-ext.
T
Mikhail Petrov created IGNITE-13981:
---
Summary: Documentation: SQL tracing.
Key: IGNITE-13981
URL: https://issues.apache.org/jira/browse/IGNITE-13981
Project: Ignite
Issue Type: Improvement
Mikhail Petrov created IGNITE-13902:
---
Summary: Add IgniteClient Spring Bean wrapper
Key: IGNITE-13902
URL: https://issues.apache.org/jira/browse/IGNITE-13902
Project: Ignite
Issue Type
Mikhail Petrov created IGNITE-13769:
---
Summary: Add examples of using the Ignite Spring Data thin client
integration.
Key: IGNITE-13769
URL: https://issues.apache.org/jira/browse/IGNITE-13769
Mikhail Petrov created IGNITE-13768:
---
Summary: Provide documentation on using the Spring Data
integration with thin client.
Key: IGNITE-13768
URL: https://issues.apache.org/jira/browse/IGNITE-13768
s,
Mikhail
On 19.11.2020 12:31, Petr Ivanov wrote:
If it is not an extensions, so why do we put it to ignite-extensions repository?
Do we need additional separate ignite-utilities repository for modules like
spring-data-commons?
On 19 Nov 2020, at 12:08, Mikhail Petrov wrote:
Saikat,
s11-ext
ignite-kafka-ext
It will be great if we can release all these modules also together.
Regards,
Saikat
On Wed, Nov 18, 2020 at 8:00 AM Mikhail Petrov
wrote:
Denis,
I omitted "-ext" for simplicity. Currently, this suffix is present in
the name of all Spring Data integrat
s of other extensions end with “ext”.
Also, how about making a single release of all the extensions that were
migrated from the main Ignite repo. There are many of them waiting for this
to happen. Saikat, Alex Goncharuk what do you think?
Denis
On Wednesday, November 18, 2020, Mikhail Petrov
wrot
Mikhail Petrov created IGNITE-13722:
---
Summary: Ignite Spring Data: Ignite resources are not closed
properly when closing Spring context.
Key: IGNITE-13722
URL: https://issues.apache.org/jira/browse/IGNITE-13722
Hello, Igniters.
Since the migration of Ignite Spring Data modules to extensions, thin
client support for Spring Data integration was implemented. - [1].
To make this feature available for users, I propose to start the release
process of the following modules:
* ignite-spring-data
* ignite-
Mikhail Petrov created IGNITE-13708:
---
Summary: Add thin client support for Spring Transactions.
Key: IGNITE-13708
URL: https://issues.apache.org/jira/browse/IGNITE-13708
Project: Ignite
pring-data
extension because I do not know whether there are maintenance releases for
each of the sprint-data-[2.0, 2.1, 2.2] streams. If spring-data-2.0.x is no
longer supported, then definitely we should be good to release it once and
move on.
--AG
ср, 11 нояб. 2020 г. в 17:26, Mikhail Petrov :
Al
hts?
вт, 10 нояб. 2020 г. в 14:14, Mikhail Petrov :
Igniters,
It seems that we came to decision on change of Ignite dependency scopes
to "provided". Don't we?
The corresponding ticket [1] is ready to final review. Saikat Maitra
have already reviewed and approved PR [2].
Could som
Igniters,
It seems that we came to decision on change of Ignite dependency scopes
to "provided". Don't we?
The corresponding ticket [1] is ready to final review. Saikat Maitra
have already reviewed and approved PR [2].
Could some committer take a final look?
[1] - https://issues.apache.org
Mikhail Petrov created IGNITE-13647:
---
Summary: Spring Data: Avoid creation of cache object through
reflection when _VAL field is present in query.
Key: IGNITE-13647
URL: https://issues.apache.org/jira/browse
Mikhail Petrov created IGNITE-13624:
---
Summary: Extend tracing of communication socket write with number
of sent bytes.
Key: IGNITE-13624
URL: https://issues.apache.org/jira/browse/IGNITE-13624
Mikhail Petrov created IGNITE-13621:
---
Summary: Remove dependency of spring-data modules on Ignite version
Key: IGNITE-13621
URL: https://issues.apache.org/jira/browse/IGNITE-13621
Project: Ignite
Manuel Nunez, Ilya Kasnacheev,
I'm working on the support of thin clients for ignite spring data
integration. And I faced that in method
IgniteRepositoryQuery#rowToEntity that was introduced by ticket [1],
BinaryObject is used to create cache value class from SQL result row and
to determine c
chev
написал(а):
Mikhail,
+1 for migrate
чт, 8 окт. 2020 г. в 18:34, Mikhail Petrov <
pmgheap@gmail.com
:
Igniters,
I propose to migrate spring-data modules from ignite main
repository
to
ignite-extensions.
Are there any objections?
I've created ticket [1] and PR t
Ilya, I haven't meant that removal of spring-data from Ignite main
repository should be done before the 2.9 release and be included in it.
Migration of spring-data to ignite-extensions could help us to make
SpringData integration updates available for users earlier then the next
Ignite release
Igniters,
I propose to migrate spring-data modules from ignite main repository to
ignite-extensions.
Are there any objections?
I've created ticket [1] and PR to both ignite [2] and ignite-extensions
[3] repositories.
[1] - https://issues.apache.org/jira/browse/IGNITE-13559
[2] - https:
Mikhail Petrov created IGNITE-13559:
---
Summary: Migrate spring-data modules to ignite-extensions.
Key: IGNITE-13559
URL: https://issues.apache.org/jira/browse/IGNITE-13559
Project: Ignite
Mikhail Petrov created IGNITE-13519:
---
Summary: Add thin client support for Spring Data.
Key: IGNITE-13519
URL: https://issues.apache.org/jira/browse/IGNITE-13519
Project: Ignite
Issue Type
Mikhail Petrov created IGNITE-13488:
---
Summary: Add command to control.(sh|bin) to get an arbitrary Metric
Key: IGNITE-13488
URL: https://issues.apache.org/jira/browse/IGNITE-13488
Project: Ignite
Mikhail Petrov created IGNITE-13477:
---
Summary: Fix NPE in SQL tracing implementation.
Key: IGNITE-13477
URL: https://issues.apache.org/jira/browse/IGNITE-13477
Project: Ignite
Issue Type
Mikhail Petrov created IGNITE-13456:
---
Summary: Expand info collected during tracing of SQL queries.
Key: IGNITE-13456
URL: https://issues.apache.org/jira/browse/IGNITE-13456
Project: Ignite
Mikhail Petrov created IGNITE-13426:
---
Summary: Add command to control.(sh|bin) to get an arbitrary
SystemView
Key: IGNITE-13426
URL: https://issues.apache.org/jira/browse/IGNITE-13426
Project
Nikolay, thanks a lot. Now everything works just fine.
On 02.09.2020 14:08, Nikolay Izhikov wrote:
Hello, Mikhail.
Thanks.
Done.
https://ci.ignite.apache.org/viewLog.html?buildId=5579056&tab=queuedBuildOverviewTab
2 сент. 2020 г., в 11:41, Mikhail Petrov написал(а):
Igniters,
Not
Igniters,
Not all tests from the IgniteOpenCensusSuite are currently running on
TeamCity. It seems that it due to incorrect TC settings - TEST_SUITE
value for OpenCensus suite configuration should be IgniteOpenCensusSuite
but the current value is OpenCensusMetricExporterSpiTest [1].
Unless t
Mikhail Petrov created IGNITE-13361:
---
Summary: SQL Select query hangs during cursor iteration.
Key: IGNITE-13361
URL: https://issues.apache.org/jira/browse/IGNITE-13361
Project: Ignite
Mikhail Petrov created IGNITE-13310:
---
Summary: Add SQL tracing.
Key: IGNITE-13310
URL: https://issues.apache.org/jira/browse/IGNITE-13310
Project: Ignite
Issue Type: Improvement
Hello, Igniters.
At the moment execution of the following SQL queries via JDBC requires
no security permissions:
ALTER TABLE ADD
ALTER TABLE DROP COLUMN
CREATE INDEX
DROP INDEX
Could someone clarify does this behavior considered desired or it is
needed to be fixed?
Tests that shows describe
Hello, Igniters.
I am working on IGNITE-12894 - [1]. It seems that it has the root cause
which is similar to the problem described in this thread.
To solve these problems, I propose to change the behavior of the
IgniteServiceProcessor#serviceTopology if the timeout argument is 0.
At the momen
Hello, Igniters.
I propose to cherry-pick to 2.8.1 ticket [1].
In addition to adding a new metric, it fixes a bug when, after deactivation,
GridDhtPartitionsExchangeFuture#rebalanced flag was not reset. And therefore,
it can be different on nodes that are already in the cluster from newly joi
Mikhail Petrov created IGNITE-12925:
---
Summary: Flaky test SystemViewSelfTest.testContinuousQuery.
Key: IGNITE-12925
URL: https://issues.apache.org/jira/browse/IGNITE-12925
Project: Ignite
s can be introduced to the SPI to resolve
this issue.
пн, 13 апр. 2020 г. в 09:33, Mikhail Petrov :
Hello, Igniters.
I recently noticed that if the client node failed to register the CQ
handler during CQ start, the start of CQ succeeds despite this.
In this case, the error message appears i
Hello, Igniters.
I recently noticed that if the client node failed to register the CQ
handler during CQ start, the start of CQ succeeds despite this.
In this case, the error message appears in the client log. It can be
something like this:
[2020-04-13
09:20:48,315][ERROR][disco-notifier-wo
:
Hello, Mikhail.
Can you, please, double-check link to the ticket?
For now it’s a IGNITE-12049 Add user attributes to thin clients which is
resolved.
16 марта 2020 г., в 12:04, Mikhail Petrov
написал(а):
Hello, Igniters.
I'd like to propose a small improvement in control.sh configura
Hello, Igniters.
I'd like to propose a small improvement in control.sh configuration,
which is to add the ability to pass parameters needed for cluster
connection via a special properties file located in the same directory
as control.sh script.
The connection parameters in the proposed prope
Hi, Alexei.
The ticket [1] describes the general problem for all thin client
authorizations. Its particular case is described in the mentioned in [1]
ticket [2] on the example of a JDBC client with the reproducer attached.
[1] https://issues.apache.org/jira/browse/IGNITE-12589
[2] https://is
Hi, Andrey.
The approach of setting plugins via IgniteConfiguration provides an
additional feature to control the order in which plugins will be loaded.
It's important in the case when several plugins provide different
implementations of the same GridComponent while providing some other
unique
I am fine with the approach.
ср, 4 дек. 2019 г. в 20:30, Mikhail Petrov :
Ivan,
Am I right, that current approach to solving this problem looks good for
you?
Regards,
Mikhail.
On 03.12.2019 15:12, Ivan Pavlukhin wrote:
Mikhail,
Yep, I see IgniteNodeValidationResult in new event in PR [1
PR[1]).
https://github.com/apache/ignite/pull/7057/files
вт, 3 дек. 2019 г. в 14:32, Mikhail Petrov :
Nikolay, Ivan,
I understood the possible problem. It seems that it can be solved using
EventStorageSpi which starts before DiscoveryManager.
As for me, ClusterNode is enough. It contains all info abo
Start is the right place. Is it enough to pass
only problematic node id (or ClusterNode) with an event? Actually such
event seems to fit naturally node join/left/failed events.
вт, 3 дек. 2019 г. в 10:38, Mikhail Petrov :
Hi Ivan.
No other lifecycle events are needed in my case.
We can regis
019 г. в 18:09, Mikhail Petrov :
Hi, Andrey.
It doesn't influence on authentication or authorization process. There
is a security requirement that demands to notify some outer security
subsystems in a specific way when joining node validation failed in any
Ignite component (e.g. GridCacheProc
ateNewNode(org.apache.ignite.cluster.ClusterNode,
java.io.Serializable) method. Does it fit for your needs?
On Mon, Dec 2, 2019 at 12:54 PM Mikhail Petrov wrote:
Hi, Ivan.
Unfortunately, we came to no decision yet. As I mentioned above this
event is disabled by default and no node will receive this event without
a
нояб. 2019 г. в 10:10, Mikhail Petrov :
Hi, Ivan.
I'm sorry that the discussion was moved in private channel. The problem
I'm trying to solve is described below in the thread. The security
plugin in my case stores and analyzesinfo about a node that failed to join.
Re
1 - 100 of 107 matches
Mail list logo
