Re: Re[2]: IGNITE-6499 Compact NULL fields

Ok gotcha, so it is not going to make it. Just to note that we are dragging this since before v2.0 and just a reminder that someone else tried a similar thing before v2 and it got blocked because it was too much of a change for v2. Typically the type of things that we can never change because it

Re: Request for contributors permissions

Hi Ivan, let me first apologize for the question, sure they are stupid and I am missing something obvious but I do not get what. I forked ignite there https://github.com/hostettler/ignite Then I comitted everything in my fork and then I create a pull request at https://github.com/apache/ignite/pu

Re: Request for contributors permissions

Hello, can I have the rights to create a branch on the github mirror. Thanks -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: IGNITE-6499 Compact NULL fields

Hello, Look at the ticket and the only comment I can see is creating a branch on git in the main repo and not in my fork. I do not have the right to create a branch in the main repository. Am i missing something? Sorry I probably misread the document but I though that I should fork the repo and

Re: Re[4]: IGNITE-6499 Compact NULL fields

Hello, Stanilovsky Evgeny : would you mind having a look at the pull request. Thanks in advance -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Ignite and Java 9+

Indeed, I misread the code and it already saves "str4e" on 5 bytes and "str4€" on 7 bytes. Sorry for the waste of time. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Ignite and Java 9+

Hello, The method doWriteString(@Nullable String val) writes everything in UTF-8. This is a bit a waste because with Java 9+ , strings are optimised and if all chars are ISO-LATIN-1 all char are represented with 1 byte instead of two. I would consider creating

Re: Re[4]: IGNITE-6499 Compact NULL fields

Hello, still fighting to get my unit tests green. Something I do not really understand is the mechanism of object replacement. For instance, marshalling a LocalDateTime, gets replace by java.time.Ser, I assume that's because it has a method writeReplace. But that takes precedence over a custom ser

Re: Re[4]: IGNITE-6499 Compact NULL fields

Ok, anyway I will finish my patch 2 unit tests still not working. I assume anyway that if we would want to apply zstd compression we would reuse the existing page compression algorithm in memory and not only for persistence. That would probably be anyway simpler and more straightforward. Will try

Re: Re[2]: IGNITE-6499 Compact NULL fields

Sorry I do not actual get what are you opposing? the compress of the binary or the null compaction or both? And can you ellaborate on why you are opposing it? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Request for contributors permissions

Thanks a lot -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Request for contributors permissions

Hello, as discussed in this thread I would like to contribute to IGNITE-6499. Would you mind giving me the right to contribute. Thanks in advance -- Sent from: http://apache-ignite-develop

IGNITE-6499 Compact NULL fields

Hello igniters, while I would like to help on the calcite because H2 optimiser (or the lack thereof) is really killing us, I think that it would be wiser to start by contributing on something easier. Therefore I will tackle another problem that we have which is the memory consumption. I stumbled

Re: Adding experimental support for Intel Optane DC Persistent Memory

Dear all, while I probably cannot help a lot with the implementation, I have access to a machine with Optane memory. So if I can help in running benchmarks, let me know. Steve -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

RE: New SQL execution engine

Actually I am now wondering whether this is not just a bug and that I should record it as such. As the behavior is different with and without the parallelism and there is no warning during execution or in the api. Any thought? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: New SQL execution engine

Dear all, would it be possible to also have then // execution of sql queries on single node with that approach? My understanding is that, for the moment, the SQL queries a re single-threaded for a given node if there is no affinity. Best Regards -- Sent from: http://apache-ignite-developers.23

Re: Embedded Version of H2

Hello, Actually I found the answer with the following ticket : https://issues.apache.org/jira/browse/IGNITE-10801 Seems to be planned for 2.8.0 -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Embedded Version of H2

Hello, we would like to use new H2 features (especially the OVER keyword) introduced in 1.4.198. Currently, 2.8.0-SNAPSHOT is relying on 1.4.197. Is there any plan to upgrade and if not, why? Do you expect any major issue with that upgrade or the use of the OVER keyword? Steve -- Sent from: ht

Re: H2 license and vulnerabilities

Hello Vladimir, thanks a lot for the quick turnaround. That answers my question and clears the vulnerability part. Best Regards -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

H2 license and vulnerabilities

Hello, I am using Apache Ignite in an financial setting and it gets reported as a high risk because of one of its dependencies : H2 The blackduck report warns the following: 1) The H2 license being weak reciprocal it is not the prefered type of OSS licenses (e.g., Apache, MIT) 2) There are known v

Re: Questions about getAllInternal(...)

Hello Alexey, Thanks for the answer. It does help but I can't help thinking that the sort of one size fits all approach would have important performance consequences on simple use cases (read only local or replicated caches). Wouldn't be useful to have the option for a on heap non serialized cach

Questions about getAllInternal(...)

Hello, in the case of local caches without eviction policy. I have the following questions: 1) I would to understand why, in the method, getAllInternal the method entryEx(cacheKey); uses the topology in the case of a local cache. Furthermore, it calls the method map.putEntryIfObsoleteOrAbsent.

Documentation about GatewayProtectedCacheProxy and more generally the gate semantics

Hello all, I am trying to understand how the system of gate and delegate works in GatewayProtectedCacheProxy. Is there some documentation you could point me to. Relying on reading the code and debug mode is not that optimal :) In particular, there is apparently part of the configuration that is