Re:Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]

The tickets for metastorage compaction are still in progress. There is a small ticket to fully enable it - https://issues.apache.org/jira/browse/IGNITE-23280, but it's blocked by IGNITE-23280 and IGNITE-23466. I propose the hold the release for a few more days.

Re: Apache Ignite 3.0.0 RELEASE [Time, Scope, Manager]

Hi guys, I'd like to highlight that there's still an unfinished epic (https://issues.apache.org/jira/browse/IGNITE-20166) related to the compaction triggers for meta store. It's marked as "Important" in Jira and it totally reflects it's severity. Currently nodes of a cluster are being slowly o

Re: Default Lucene index for String cache values

Hi guys, I've checked that a text index is being created only if a user specifies indexedTypes (or something similar). It would be nice to give users an option to avoid this behaviour as it's technically a workaround because it's not possible to somehow specify the @QueryTextField annotation on a

[jira] [Created] (IGNITE-14331) Possible distributed race related to a data streamer flushing leading to a thread being stuck forever trying to close the streamer

Vladimir Pligin created IGNITE-14331: Summary: Possible distributed race related to a data streamer flushing leading to a thread being stuck forever trying to close the streamer Key: IGNITE-14331 URL: https

[jira] [Created] (IGNITE-14248) Handle exceptions in PartitionReservationManager.onDoneAfterTopologyUnlock properly

Vladimir Pligin created IGNITE-14248: Summary: Handle exceptions in PartitionReservationManager.onDoneAfterTopologyUnlock properly Key: IGNITE-14248 URL: https://issues.apache.org/jira/browse/IGNITE-14248

[jira] [Created] (IGNITE-14130) There's a race in WAL segment rollover procedure

Vladimir Pligin created IGNITE-14130: Summary: There's a race in WAL segment rollover procedure Key: IGNITE-14130 URL: https://issues.apache.org/jira/browse/IGNITE-14130 Project: I

Re: [VOTE] Release Apache Ignite 3.0.0-alpha1 RC3

+1 (non-binding) -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-13763) C++: Add a configuration property allowing thin CPP client to limit connection count.

Vladimir Pligin created IGNITE-13763: Summary: C++: Add a configuration property allowing thin CPP client to limit connection count. Key: IGNITE-13763 URL: https://issues.apache.org/jira/browse/IGNITE-13763

Re: Using deprecated active() and unhelpful message in console

Yeah, I suppose a ticket has been filed. I bet it's https://issues.apache.org/jira/browse/IGNITE-13534. Anyway the change looks really good, let's go on! Ilya, it's your turn. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Limit/Offset index scan

Denis, I absolutely agree with you that a SortedSet doesn't need to be partitioned. The main idea I wanted to put attention on is that now it's not possible to find a row with a particular number with log complexity. We need to scan node-local index until we reach some offset, it seems to be linea

Limit/Offset index scan

Hi Igniters, It seems that it's not possible to implement effective leader-board with the current Ignite indexes. Leader-board stores a score and an id of a player of some game. Score is indexed. One of the possible requests to that data structure is to get some range of scores based on their rank

[jira] [Created] (IGNITE-13396) ignite.queue return null instead of throwing IgniteException as declared in the javadoc

Vladimir Pligin created IGNITE-13396: Summary: ignite.queue return null instead of throwing IgniteException as declared in the javadoc Key: IGNITE-13396 URL: https://issues.apache.org/jira/browse/IGNITE-13396

Re: IEP-51: Java Thin Client Async API

Hi guys, It would be really cool to have async operations. My point is that the worst thing that we have at the moment is that we need to write data to the socket under the sndLock. It makes it nearly impossible for users to implement async operations on their side. Of course they can scale up by

Re: Thin Client Kubernetes discovery

Hi guys, Maybe I'm missing something but I don't undestand how StatefulSet relates to the described functionality. StatefulSet is more about persistence. Correct me if I'm wrong but my current understanding is that we don't need to have any explicit state for a thin client connection. I'd like thi

Re: [DISCUSS] Make AtomicConfiguration more flexible

I've raised the issue https://issues.apache.org/jira/browse/IGNITE-13118. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-13118) Make AtomicConfiguration more customizable

Vladimir Pligin created IGNITE-13118: Summary: Make AtomicConfiguration more customizable Key: IGNITE-13118 URL: https://issues.apache.org/jira/browse/IGNITE-13118 Project: Ignite Issue

[DISCUSS] Make AtomicConfiguration more flexible

Hi Igniters! It seems that AtomicConfiguration (https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/AtomicConfiguration.html) is not flexible enough to cover some reasonable use-cases. It's possible to configure only cache mode, group name, affinity and backups of the

Re: Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

Thanks, Ilya. It would be really great to have your patch included into 2.8 scope. I'd like to give my two cent as well. For example we have vulnerable dependencies here: modules/cassandra/store/pom.xml - commons-beanutils modules/zookeeper/pom.xml - transitive Jackson from Curator I'd suggest

StackOverflow question about encryption

Hi igniters, I can see a question on SO http://apache-ignite-developers.2346864.n4.nabble.com. The question is related to encryption. Nikolay Izhikov, as far as know you're the author of the feature and unfortunately I don't know anyone else who is familiar with it. Could you please answer? Thanks