Re: Issue with custom security plugin and thin clients

Hello! I afraid these changes will not be included in the 2.10 version. сб, 19 дек. 2020 г. в 06:03, Vishwas Bm : > Hi Denis, > > Thanks for the feedback. > > I had also put a comment in one of your PR regarding iep-41. > https://github.com/apache/ignite/pull/8038#issuecomment-742230009 > > > It

Re: [DISCUSSION] 3.0.0 Alpha release

Hi Val, That's the pace, I'll be happy to play with the alpha and share feedback. Also, what if we arrange a community gathering after the holidays to demonstrate what alpha does and get more details from the involved contributors on what's coming next? As for the release process, yes, that

Re: Issue with custom security plugin and thin clients

Hi Denis, Thanks for the feedback. I had also put a comment in one of your PR regarding iep-41. https://github.com/apache/ignite/pull/8038#issuecomment-742230009 It will be great if you can provide input on this. Regards, Vishwas On Fri, 18 Dec, 2020, 21:39 Denis Garus, wrote: > Hi! > I

Re: Query on ignite-kafka artifact (ignite-kafka-ext)

Hi Denis, Thanks for the reply. I will try to use the version of kafka-ext available in mvn repository with ignite master branch code. Regards, Vishwas On Sat, 19 Dec, 2020, 01:48 Denis Magda, wrote: > Hi Vishwas, > > Kafka and all other extensions I being moved to that separate repository >

[DISCUSSION] 3.0.0 Alpha release

Igniters, The repository for Ignite 3.x [1] was created less than a month ago, and we already have several merged pull requests. Many thanks to everyone involved for the contributions! Currently, we have the following functionality available in the main branch: - New configuration framework

[GitHub] [ignite-3] asfgit closed pull request #4: IGNITE-13610 Initial version of unified CLI tool

asfgit closed pull request #4: URL: https://github.com/apache/ignite-3/pull/4 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the

Re: [DISCUSS] Ignite 3.0 development approach

Hi Ivan, There was a very brief discussion around this. Basically, it looks like switching from Maven to something else is not going to bring much value, but at the same time will be quite demanding because the community has much more experience with Maven. However, I would say that it is still

Re: [DISCUSS] Notifications for ignite-3 repository

Folks, Can someone take a look at this PR? I'm generally OK with the change, but I'm not familiar with the mechanisms used here. -Val On Thu, Dec 17, 2020 at 11:16 PM Ivan Pavlukhin wrote: > Igniters, > > I noticed notifications about PRs in ignite-3 repository sent to > dev-list. I suppose

Re: Query on ignite-kafka artifact (ignite-kafka-ext)

Hi Vishwas, Kafka and all other extensions I being moved to that separate repository and will be released independently. We'll update and release new versions of extensions whenever is needed. In the meantime, the Kafka extension should be compatible with all Ignite version. So, just update your

[RESULT] [VOTE] Release Apache Ignite 2.9.1 (RC1)

Hello, Igniters! Apache Ignite 2.9.1 release (RC1) has been accepted. 6 "+1" votes received. Here are the votes received (in order received): - Pavel Tupitsyn (binding) - Ilya Kasnacheev (binding) - Nikolay Izhikov (binding) - Denis Magda (binding) - Alex Plehanov (binding) -

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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Maxim, Presently, there are 70 documentation tickets. Probably, these are all the tickets that we are moving from a release to a release. Could you help to prepare a list of 2.10-specific tickets (features, enhancements, required updates due to a change in the behavior)? As before, we can track

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Hello Nikita, Thanks for your support. You can find the 2.10 related documentation issues on the release wiki page [1]. Currently, some of the important issues don't have the right priorities, so it's better to sort them first. As for the time estimates, we've previously agreed that

Re: Issue with custom security plugin and thin clients

Hi! I don't understand why you do something related to thin clients inside onDisconnected method? The rest looks good to me. ср, 9 дек. 2020 г. в 17:00, vbm : > Hi Denis, > > Any thoughts on the approach mentioned above ? > > > Regards, > Vishwas > > > > -- > Sent from:

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Hi guys, I'd be more than happy to support the 2.10 release and contribute to the documentation. So could you please give me a scope of documentation tasks for 2.10 with the approximate time estimates? Regards, Nikita пн, 7 дек. 2020 г. в 16:23, Alexey Zinoviev : > Support it > > пн, 7 дек.

Static hierarchy in jmx tree

Hello, everyone! Ignite has a changeable jmx hierarchy now. It may lead a lot of problems for product maintenance and monitoring: - By default where would be classloader that change every time that node has been restarted. It will lead to rediscover all metrics for node. - It's hard to

Limit amount of space available for Ignite persistence

Hi everyone! Ignite has a way to limit the amount of memory available to store information. If this limit is reached, then page eviction or page replacement will kick in and make sure that the amount occupied space stays in the configured limits. There are no such settings for the disk storage

[GitHub] [ignite-3] alievmirza commented on a change in pull request #4: IGNITE-13610 Initial version of unified CLI tool

alievmirza commented on a change in pull request #4: URL: https://github.com/apache/ignite-3/pull/4#discussion_r545802730 ## File path: modules/cli-demo/cli/src/main/java/org/apache/ignite/cli/IgniteCLIException.java ## @@ -0,0 +1,30 @@ +/* + * Licensed to the Apache Software

Re: Metastorage limitations

Nikolay, Thanks for your reply! I encountered a similar case to what you've described in point #1. I used a private plugin that writes some information to the metastorage. After that I decided to get rid of that plugin, while the information had already been written to the metastorage.

Re: Metastorage limitations

Hello everybody! If you look at the stackTrace, the error is that deserialized objects are being sent to listeners. It may be more correct to send a raw arrays of bytes, and each plugin will be able to process it if needed. 18.12.2020, 12:18, "Nikolay Izhikov" : > Hello, Denis. > > It’s a

[jira] [Created] (IGNITE-13876) Update documentation for 2.9.1 release

Yaroslav Molochkov created IGNITE-13876: --- Summary: Update documentation for 2.9.1 release Key: IGNITE-13876 URL: https://issues.apache.org/jira/browse/IGNITE-13876 Project: Ignite

Re: Metastorage limitations

Hello, Denis. It’s a known issue for me. Metastore is a private API, isn’t it? AFAICU it can occur for two reasons: * User migrates from custom Ignite fork that has private improvements or plugins that write to the metastore. * We have a blocker bug and just remove some internal class that can

Metastorage limitations

Hi everyone! Ignite has a limitation that it can’t work with custom classes put into metastorage: https://issues.apache.org/jira/browse/IGNITE-13642 If you put a POJO into the metastorage, then Ignite will try to deserialize it using the classes it finds on the classpath. If it can’t do the