Re: Ignite OpenSSL Vulnerability

Hello! For the most part, we to not supply compiled versions of our C++ code, and our Java code does not use OpenSSL. So you should check if you can build ODBC driver against non-affected OpenSSL version. Regards, -- Ilya Kasnacheev чт, 3 нояб. 2022 г. в 15:45, Entwicklung : > Hello, > > i h

Re: ignite-spark3.2-ext release

Folks, I can help with releasing this module (and actually it's pretty easy to do a release using GA), but I have some notes according to contribution: 1. We should merge spark3.2-ext and spark-ext and separate development streams of different versions using branches with appropriate spark versio

[DISCUSSION] Enable Doclint for Ignite 3

Hi Igniters, I'm working on the javadoc generation in gradle and I mentioned that now standard Doclint [1] is disabled in the maven javadoc generation. I wonder to know why it is disabled. I would suggest enabling Doclint by default because it is a recommended and standard approach to dealing

Re: IgniteLogger improvement

Hello Ilya, I think that you might satisfy your requirements using MDC. It is refereed as Managed/Mapped Diagnostic Context [1], some logging libraries call it also Nested Diagnostic Context. Using it you can mark log entries with context specific information which is provided elsewhere. Stand

Re: Ignite OpenSSL Vulnerability

Hi, we don't link our odbc driver with openssl libraries. We load them dynamically. So don't worry, our odbc driver is not affected at all. Moreover, it supports multiple versions of openssl, up to 3.0.x пн, 7 нояб. 2022 г. в 12:17, Ilya Kasnacheev : > Hello! > > For the most part, we to not supp

Re: Ignite OpenSSL Vulnerability

So you should just download the latest openssl binaries, add them to PATH and that's it. The ignite odbc driver will load them automatically. You could also set OPENSSL_HOME env variable to the specific folder with the valid openssl binaries.

[ANNOUNCE] Release pyignite-0.6.0

Hi, Igniters! I suppose it is time to release pyignite 0.6.0, since we have released our previous release more than a year ago. Firstly, python 3.6 reached its EOL, the brand new python, 3.11, was just released. So it is a good idea to build new wheels targeting the new versions. Also, there are

RE: [DISCUSSION] Enable Doclint for Ignite 3

Here is my PR with enabling DocLint https://github.com/apache/ignite-3/pull/1320 I wonder if someone can take a look. -- Best regards, Aleksandr On 2022/11/07 11:45:48 Aleksandr Pakhomov wrote: > Hi Igniters, > > I'm working on the javadoc gene

Re: [ANNOUNCE] SCOPE FREEZE for Apache Ignite 3.0.0 beta 1 RELEASE

I also added https://issues.apache.org/jira/browse/IGNITE-17989 and https://issues.apache.org/jira/browse/IGNITE-17357 to the scope. Stan > On 4 Nov 2022, at 18:26, Игорь Гусев wrote: > > > Hi Igniters, > > I’d like to include some doc into beta1 if its not too late > https://issues.apache.o