It's an amazing idea! I faced this problem several times and it's really
annoying, I'd be glad to this problem fixed.
Best regards,
Anton Dmitriev.
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Sergey Antonov created IGNITE-11889:
---
Summary: Add security permissions cluster state change operations
Key: IGNITE-11889
URL: https://issues.apache.org/jira/browse/IGNITE-11889
Project: Ignite
Hi Nikolay,
Great, another one nice step to clean code.
I scrolled down the commit [1] and have couple of observations:
1. According to our code style agreements each class member should be
separated by 1 empty line. As I see there were many places where it
was not followed for class fields. E.g.
Hello, Ivan.
> For me fields without extra empty lines between them look fine.
This is violation of Ignite code style, so we should fix it for now.
If we decide to change code style, we can change check.
> Can/should we enforce no empty lines there?
You can look into checkstyle documentation fo
I will have a look this week, currently it has conflicts with master
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Guys,
I updated the page.
-Artem
On 02.06.2019 22:20, Nikolay Izhikov wrote:
Hello, Denis.
Ignite doesn't encrypt memory page as long as it retains in memory.
Page encrypted when it is written to the disk.
пт, 31 мая 2019 г. в 19:39, Denis Magda :
Nikolay,
Do we really support encryption
Hi Alexey, thank you.
Hi Ravil,
4 blockers from TC bot seems to be unrelated to the change. Please check
only that contributed files have appropriate licenses. I see failure here
https://ci.ignite.apache.org/viewLog.html?buildId=4003665&buildTypeId=IgniteTests24Java8_LicensesHeaders&tab=artifacts
Sergey,
Do we have an IEP for this feature?
What should happen when on an active cluster with put operations if we
receive a read-only state change request? How we guarantee that all
cache operations delivered (or not yet) to backups are not rejected by
applied read-only request? I haven't found
Hi Igniters,
For older versions, where the needed configuration is absent you may found
the following behavior of tests
SPI [ tests 1 ] JDK8
IgniteSpiTestSuite: TestSuite$1.warning
Cache (Restarts) 1 [ tests 1 ] JDK8
IgniteCacheRestartTestSuite: TestSuite$1.warning
If you found such issue c
Nikolay,
> This is violation of Ignite code style, so we should fix it for now.
> If we decide to change code style, we can change check.
I wonder if it technically feasible. Do know is it possible to permit
no empty line before a class field?
пн, 3 июн. 2019 г. в 16:56, Nikolay Izhikov :
>
> He
Hey Peter, Anton,
Are any of you able to help Nickolay with [1]?
-
Denis
On Mon, Jun 3, 2019 at 6:17 AM Nikolay Izhikov wrote:
> Hello, Igniters.
>
> We have several issues with Examples suite on TC
>
> 1. IgniteExamplesSparkSelfTestSuite seems configure, bu not runs on suite
> execution. [1]
Nikolay,
It looks like that profile -Pscala should be activated to run
IgniteExamplesSparkSelfTestSuite. I was able to start that suite
execution on my machine but it failed during execution.
вт, 4 июн. 2019 г. в 03:08, Denis Magda :
>
> Hey Peter, Anton,
>
> Are any of you able to help Nickolay
12 matches
Mail list logo
