Re: Spring 6 support for ignite extensions

Hi. In general proposal looks good to me, but I agree with Andrey that sticking to same *major.minor* is too much. From my perspective using same major is enough. It still will make it easier to understand correlation between spring and corresponding extension module, meanwhile preserving enough

Re: [DISCUSSION] IEP-107 Logging in Ignite 3

Hi Konstantin, Btw, Ignite 2 has also public methods that accepts a Marker.     public void info(String marker, String msg); Was this part of previous Implementation considered as redundant? I'm concerned because, despite it might not be needed for Ignite 3 itself, IgniteLogger is also a comp

Re: [DISCUSSION] IEP-107 Logging in Ignite 3

Hi Konstantin. Thanks for you work. Despite you proposal is more about public API of logging Ignite facility, I believe that this thread is the best place to highlight some topic about internal details of IgniteLogger based on my experience with Ignite 2 I already tried to initiate a discuss

Re: IgniteLogger improvement

, Aleksandr Polovtsev пишет: Thank you for the proposal, Ilya! Looks like a really nice change. I can't see any of the mentioned attachments for some reason, though On Sun, Nov 6, 2022 at 10:05 AM Ilya Korol wrote: Hi Igniters, I would like to discuss the Ignite logging. I found current lo

IgniteLogger improvement

Hi Igniters, I would like to discuss the Ignite logging. I found current logging implementation a little bit inflexible for several use-cases. Assume that I want to run multiple Ignite instances in same JVM process and I also want that all messages from each Ignite instance go to separate fil

Re: [VOTE] Add micronaut dependency to Ignite 3 (reopened)

+1 01.06.2022 19:14, ткаленко кирилл пишет: + 1

Re: [DISCUSSION] IEP-88: CLI Tool

From my perspective we should move towards existing UX approaches. For example: python - enters shell python --help  - prints help python -c - executes command What about other CLI tools that works with remote services? I can't remember properly but do AWS, openshift or maybe GCP CLIs also supp

IndexOutOfBoundsException in GridCacheWriteBehindStore Flusher thread lookup (IGNITE-14893)

Hi, All. I'm going to fix issue with IndexOutOfBoundsException in GridCacheWriteBehindStore#flusher(K key) method. https://issues.apache.org/jira/browse/IGNITE-14893 This could happen when flush thread count is not a power of 2 an we fallback to mapping via modulo operation: idx = ((h = k

IndexOutOfBoundsException in GridCacheWriteBehindStore Flusher thread lookup (IGNITE-14893)

Hi, All. I'm going to fix issue with IndexOutOfBoundsException in GridCacheWriteBehindStore#flusher(K key) method. https://issues.apache.org/jira/browse/IGNITE-14893 This could happen when flush thread count is not a power of 2 an we fallback to mapping via modulo operation: idx = ((h = k

Re: Default Lucene index for String cache values

figuration it will not create LuceneIndex, as there is no table with String as value class. You can check it with my code just replace Long and String classes in cache definition. [1] https://gist.github.com/timoninmaxim/e477ddfcbe56ec9892c7ba6ad44bfadb On Thu, Jun 3, 2021 at 10:56 AM Ilya Korol wr

Re: Default Lucene index for String cache values

indexed. If you just create a simple cache (without entities, indexed types) with String.class as value it won't be indexed, as indexes created per table, not per cache. Do I miss something? On Wed, Jun 2, 2021 at 12:56 PM Ilya Korol wrote: Hi, All. According to https://issues.apache.org/

Default Lucene index for String cache values

Hi, All. According to https://issues.apache.org/jira/browse/IGNITE-14805 there is default index creation for caches with String values: if (type().valueClass() == String.class) {     try {     luceneIdx = new GridLuceneIndex(idx.kernalContext(), tbl.cacheName(), type);     }     catch (

Re: Building with maven 3.8.1

mall comment on formatting issue. Otherwise looks good! Considering 3.8.1 maven support — we will be migrating builds there after TC 2021.1 will be delivered. On 20 May 2021, at 19:22, Ilya Korol wrote: Hi, all. Maybe someone has already faced the issue with Ignite and latest Maven release

Building with maven 3.8.1

Hi, all. Maybe someone has already faced the issue with Ignite and latest Maven release 3.8.1? https://issues.apache.org/jira/browse/IGNITE-14753 From 3.8.1 maven supplied with config that will block any http repository/mirror. (See details here https://maven.apache.org/docs/3.8.1/release-n

Re: Proposal to remove explicit "GC disable" startup suggestion

, Out of curiosity - what are the potential problems with memory buffers that you're referring to? -Val On Fri, May 14, 2021 at 5:06 AM Ilya Korol wrote: Hi, everyone. There is a proposal to remove suggestion that user should disable explicit GC calls in https://issues.apache.org/jira/b

Proposal to remove explicit "GC disable" startup suggestion

Hi, everyone. There is a proposal to remove suggestion that user should disable explicit GC calls in https://issues.apache.org/jira/browse/IGNITE-14720. Nowadays people usually don't use this facility directly without huge need (at least we hope so), so this suggestion doesn't bring much pro

Greetings

Hello Ignite Community! My name isIlya Korol. I want to contribute to Apache Ignite. My JIRA username*Korol*. Thanks!