Alex, thanks for driving the release to the final milestone. This release
is small but with crucial fixes. If anybody is on native persistence then
schedule an upgrade.
-
Denis
On Fri, Sep 20, 2019 at 3:25 AM Alexey Goncharuk
wrote:
> The Apache Ignite Community is pleased to announce the rele
I wrote about code freeze at December 18, 2019, ok, we can move one week
earlier to 11 December
Voting + Release could be after 10th January.
пт, 20 сент. 2019 г. в 15:43, Maxim Muzafarov :
> Alexey,
>
> It is not a problem to shift release a bit later or earlier, but I'm
> strictly against havi
Alexey,
It is not a problem to shift release a bit later or earlier, but I'm
strictly against having `code freeze` stage on holidays (the Christmas
holidays at the end of December and New Year holidays at the beginning
of January). From my point, it's better to have it completed `code
freeze` stag
Dmitriy Sorokin created IGNITE-12207:
Summary: Inclusion of super.toString() info into some descenders
of GridCacheMessage
Key: IGNITE-12207
URL: https://issues.apache.org/jira/browse/IGNITE-12207
+1 For Maxim as release manager.
Maxim,
It is a good thing that you have committer rights, and most of the steps
you will be able to complete yourself.
But please engage one from PMC member to complete steps from the release
process where PMC rights are required
https://cwiki.apache.org/confluen
For Spark and ML components the best dates should be moved to one month
later, what's about?
There are a lot of features there, but a lot of bugs and minor
improvements in JIRA too
Also I support you as a release manager
Scope Freeze: December 4, 2019
Code Freeze: December 18, 2019
Voting Date: J
Igniters,
It's almost a year has passed since the last major Apache Ignite 2.7
has been released. We've accumulated a lot of performance improvements
and a lot of new features which are waiting for their release date.
Here is my list of the most interesting things from my point since the
last maj
Hello, Alex.
Good catch, thank you.
I will add enabling of JMX and SQL exporters for system views, by default.
В Ср, 18/09/2019 в 16:09 +0300, Alex Plehanov пишет:
> One more point to discuss: Wouldn't it be better to have enabled system
> views by default?
> To enable views admin must restart t
Great, go 2.8!
пт, 20 сент. 2019 г. в 13:25, Alexey Goncharuk :
> The Apache Ignite Community is pleased to announce the release of Apache
> Ignite 2.7.6.
>
> Apache Ignite [1] is a memory-centric distributed database, caching, and
> processing platform for transactional, analytical, and streamin
Nikolay,
you are right in many ways. I updated the design on the wiki. [1]
[1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=95652381
пт, 20 сент. 2019 г. в 13:49, Nikolay Izhikov :
>
> Nikita
>
> > I suggested the implementation where the encryption manager is
> > responsible
Nikita
> I suggested the implementation where the encryption manager is
> responsible for storing the master key id.
I don't think it's a right proposal.
1. EncryptionSpi implementation becomes more complicated. Developer of it
should be aware of Ignite deployment scenarious, etc.
Imagine imple
Nikolay,
because I suggested the implementation where the encryption manager is
responsible for storing the master key id.
To implement this logic in the EncryptionSpi, we will need to
introduce the methods look like this:
setMasterKeyId(String masterKeyId) // Sets "current" master key id
String
The Apache Ignite Community is pleased to announce the release of Apache
Ignite 2.7.6.
Apache Ignite [1] is a memory-centric distributed database, caching, and
processing platform for transactional, analytical, and streaming workloads
delivering in-memory speeds at petabyte scale.
This release in
Stepachev Maksim created IGNITE-12206:
-
Summary: Partition state validation warns are not printed to log
Key: IGNITE-12206
URL: https://issues.apache.org/jira/browse/IGNITE-12206
Project: Ignite
Stepachev Maksim created IGNITE-12205:
-
Summary:
GridCachePartitionedSetWithClientSelfTest.testMultithreaded has 95,5% fail rate
for long time
Key: IGNITE-12205
URL: https://issues.apache.org/jira/browse/IGNI
Why do we need "defaultMasterKeyId" instead of *current* master key id that can
be obtained with `KeystoreEncryptionSpi#getMasterKeyName()`?
В Пт, 20/09/2019 в 12:56 +0300, Nikita Amelchev пишет:
> Nikolay,
>
> Thanks for the proposal, I like it.
>
> The GridEncryptionManager will control the p
Hello, Andrey.
Thanks for starting this discussion.
> 1. There is no unified approach to adding metrics during development.
Yes, we have it.
Just call `MetricRegistry#longMetric` or other method and you got your counter.
> Now the logic is spread throughout the code base and there is now any
>
Nikolay,
Thanks for the proposal, I like it.
The GridEncryptionManager will control the process of master key
rotation, so we should provide him master key id at startup. Seems we
should get it from some configuration for encryption.
I suggest just adding the String defaultMasterKeyId() method i
Ilya Kasnacheev created IGNITE-12204:
Summary: In binary distribution, essential dependencies for
ignite-spark missing
Key: IGNITE-12204
URL: https://issues.apache.org/jira/browse/IGNITE-12204
Pro
Hello, Nikita
> IgniteConfiguration: New methods will be added to the IgniteConfiguration:
> public IgniteConfiguration setEncryptionMasterKeyId(String masterKeyId) -
> sets master key id.
> public String getEncryptionMasterKeyId()
We don't need it in the IgniteConfiguration.
As you may know, w
Vladislav Pyatkov created IGNITE-12203:
--
Summary: Rebalance is loading partitions already loading after
cancellation without WAL
Key: IGNITE-12203
URL: https://issues.apache.org/jira/browse/IGNITE-12203
21 matches
Mail list logo
