Re:Ignite support for IoC beyond spring framework

Hello! I've started the review of your PR, should be ready tomorrow, but looks good overall! Kind regards, Semyon.

Re: Ignite support for IoC beyond spring framework

Hi! This sounds like a good enhancement. Feel free to create a pull request! As I see it, for now we should continue using SpringResource annotation (even if it injects non-spring resources), but at the same time create a new annotation (maybe something like @IgniteInject, I am bad with

Re: Control.sh command that schedules index rebuild in the maintenance mode

the application. Kind regards, Semyon. > Hello, Семен. > > Why index rebuild should be done in maintenance mode? > >> 31 мая 2022 г., в 18:24, Данилов Семён написал(а): >> >> Hello, igniters! >> >> I want to propose a new control.sh cache sub-command tha

Control.sh command that schedules index rebuild in the maintenance mode

Hello, igniters! I want to propose a new control.sh cache sub-command that schedules a rebuild of cache indexes in the maintenance mode. We already have a force rebuild command but sometimes (for example, under load) user may want to first stop the node and then rebuild indexes. For this

Request for a review (Java 17 support)

Hello Igniters! I'd like to request a review for an improvement that adds support for Java 17. Description of the improvement: - Added new maven profile that allows running tests with Java 17 (--add-opens and all that). This maven profile is also used for source folder with IgniteLinkTaglet

Re: [MTCGA]: new failures in builds [5994077, 5994075] needs to be handled

Hi! The fix was merged yesterday and the JDBC driver suite https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_JdbcDriver?branch=%3Cdefault%3E=overview=builds#all-projects is stable again. Semyon. 19.05.2021, 14:07, "Ilya Kasnacheev" : > Hello! > > I suggest that you may revert

Obsolete classnames.properties

Hello, Igniters! I've recently stumbled across an issue where some tests can't be run locally due to the absence of some entries in "classnames.properties" file. For example, TcpRestUnmarshalVulnerabilityTest can't be run locally because "classnames.properties" lacks

Obsolete classnames.properties

Hello, Igniters! I've recently stumbled across an issue where some tests can't be run locally due to the absence of some entries in "classnames.properties" file. For example, TcpRestUnmarshalVulnerabilityTest can't be run locally because "classnames.properties" lacks 

Re: Significant Items to Tackle

Hello Atri! Would you like to contribute into Ignite Spring integrations? You can take a look at this particular jira filter: https://issues.apache.org/jira/browse/IGNITE-9524?jql=project%20%3D%20Ignite%20and%20summary%20~%20%22spring%22%20and%20status%20not%20in%20(Resolved%2C%20Closed) .

Re: IGNITE-2399: Implement acquireAndExecute Utility Method

Hello Atri, I've read through your changes, have a look at the review. Kind regards, Sam. 23.02.2021, 08:07, "Atri Sharma" : > Hi All, > > Please help in reviewing the following PR: > > https://github.com/apache/ignite/pull/8820 > > Regards, > > Atri > > -- > Regards, > > Atri > Apache

Re: Move WAL archive cleanup from checkpoint to rollover

Hello! I also have an issue in progress regarding WAL archive: https://issues.apache.org/jira/browse/IGNITE-12892. In this ticket I tried clarifying WAL archive size configuration, removing usage of the deprecated walHistSize property. Also, IGNITE_PDS_MAX_CHECKPOINT_MEMORY_HISTORY_SIZE is now

Re: [DISCUSSION] Java 11 for Ignite 3.0 development

+1 for sure. AFAIK, the only thing holding us back from using Java 11 is the dominance of Java 8, but I'm sure that by the time Ignite 3 is GA, there will be much fewer Java 8 users if any significant number at all. By the by, Ignite's sources need minimal effort to be able to be compiled with

Re: Migrating NodeJS client to TypeScript

lue in keeping both versions - the plain JavaScript one and >>  the TypeScript specific? >> >>  - >>  Denis >> >>  On Mon, Nov 30, 2020 at 12:16 PM Данилов Семён wrote: >> >>  > Hello Igniters! >>  > >>  > I'd like to propose a big change for

Migrating NodeJS client to TypeScript

Hello Igniters! I'd like to propose a big change for the nodejs thin client: a full rewrite from JavaScript to TypeScript. Strong typing will not only help us in future while developing new features, but will also indicate existing type inconsistencies (I know there is a couple). Also, we will

Spring Session integration module

Hello, Igniters! I recently submitted a pull request to the Spring Framework's spring-session repository adding Apache Ignite integration module so that users will be able to store HTTP sessions in Ignite backed repository. If you know any Spring committers that can review and merge these

Re: Migration of spring-data modules to ignite-extensions

+1 And, as a matter of fact, I think that spring data integration should be in spring-projects organization, just like spring-data-neo4j, spring-data-mongodb and the others. This way we will always have spring-data integration working correctly with the latest version of spring-data.

Security issue with control.sh and ignite.sh

Hello, Igniters! I recently got my eye on the fact that we have JMX enabled by default and it's configured in a very insecure way. Our default JMX parameters are authenticate=false and ssl=false. I propose removing default configuration of JMX altogether, as user must *consciously* and

Re: JVM_OPTS in control.sh and ignite.sh

t; Can we at least print a warning when control.sh is run and JVM_OPTS is set? > Then you can use other env var. Or get rid of it and rely on -J. > > Regards, > -- > Ilya Kasnacheev > > пн, 28 сент. 2020 г. в 12:39, Данилов Семён : > >>  Hello, everyone! >> >>

Re: JVM_OPTS in control.sh and ignite.sh

docker only, then maybe we should get rid of >>  JVM_OPTS >>  > with docker entirely? E.g. pass them as parameters. >>  > >>  > I'm not sold on this change yet, it breaks backward compatibility for >>  > marginal benefit. >>  > >>  &g

JVM_OPTS in control.sh and ignite.sh

Hello, Igniters! I recently discovered, that control.sh and ignite.sh both use JVM_OPTS environment variable. This can lead to various issues (especially in docker), such as: * Control utility will have the same xms/xmx parameters. * Control utility won't launch due to JMX port being in use

Re: [DISCUSSION] Add autocompletion for commands in control.sh

Hello! I've looked through the picocli manual and it looks really great. We will be able easily add i18n and stuff like this. Nevertheless, we will get rid of the manual formatting of examples and help texts. Kind regards, Semyon. 14.09.2020, 13:00, "Alexey Goncharuk" : > Hi folks, > > Despite

Changes in Spring Data Integration

Hello igniters! I've been working on a tutorial regarding Spring Cloud + Ignite and came across this issue: IgniteRepositoryFactoryBean (Spring Data module) requires Ignite instance bean with specific name! And in the same time, Ignite autoconfiguration module provides Ignite instance bean

Re: Spring Committers Wanted

m do you mean under the Spring > Project committers - those who already contribute to the Spring > ecosystem and have some merit there, or those among us who are willing to > contribute the integration? > > - > Denis > > On Mon, Jun 15, 2020 at 6:27 AM Данилов Семён wrote: >

Spring Committers Wanted

Hello Igniters! I recently stumbled upon a fact that Apache Ignite doesn't have any Spring integrations in spring-project repositories. To increase Ignite's popularity, I think it would be best to fix that inconvenience. The best way to start would be to create a web-session repository based on

Re: Moving binary metadata to PDS storage folder

Hello everyone, can we move forward with the merge of IGNITE-12994? Semyon 18.05.2020, 19:08, "Denis Mekhanikov" : > Users shouldn't care about binary_meta and marshaller directories. Those > are internal details. Having to go through the documentation on those > things to figure out whether

Re: Can I get write permissions for Apache Wiki?

Hello! It's sdanilov Regards, Semyon Danilov 09.06.2020, 13:04, "Ilya Kasnacheev" : > Hello! > > What is your login for apache wiki? > > Regards, > -- > Ilya Kasnacheev > > вт, 9 июн. 2020 г. в 10:11, Данилов Семён : > >>  ello Igniter

Can I get write permissions for Apache Wiki?

ello Igniters, I’m planning to change https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood (because I have pending pull request for changing binary meta location), but don’t have rights for this. Can someone please give me the access? Sincerely yours,

Re: Moving binary metadata to PDS storage folder

gt;>  This is a good idea! >> >>  вт, 12 мая 2020 г. в 15:53, Вячеслав Коптилин : >> >>>  Hello Semyon, >>> >>>  This is a good and long-awaited improvement! Thank you for your efforts! >>> >>>  Thanks, >>>  S. >

Moving binary metadata to PDS storage folder

Hello! I would like to propose moving /binary_meta and /marshaller folders to the PDS folder. Motivation: data, directly related to the persistence, is stored outside the persistence dir, which can lead to various issues and also is not very convenient to use. In particular, with k8s,

Joining Ignite ASF

Hello! I would like to start contributing, could you please add me to contributors list? My login for https://issues.apache.org/ is sdanilov. Kind regards, Semyon Danilov.