Thanks for your quick response, Zhenya.
I now can deploy the Ignite upgrade to prod with more confidences
Thanks.
On Tue, May 17, 2022 at 6:50 PM Zhenya Stanilovsky
wrote:
> Hello, Noah. Yep seems this behavior is mistaken, just filter out this log
> somehow.
> I fill the issue [1]
>
> [1] htt
Hi Igniters! On June 14th speakers from industry-leading companies,
including Finance, Travel, Software Development and IoT will share their
experience and vision:
The future of Apache Ignite: Bridging from Complexity to Simplicity, Scale,
and Community - Nikita Ivanov, GridGain, Founder & CTO
L
Hello, Courtney.
I did some investigation.
It seems, current behavior is correct, in general.
Looks like passing list of values as a parameter is common issue for JDBC SQL
queries [1] [2] [3].
Tried to find formal requirements in JDBC spec but didn’t find clear
description :)
Anyway, If you a
Hey,
I just checked and it doesn't seem as if any of the test cases use arrays
with more than 1 element in them.
It also gives the wrong results if I use an array with multiple values.
On Tue, 17 May 2022 at 09:56, Николай Ижиков wrote:
> Hello, Courtney.
>
> I’m able to reproduce your issue [1
Hello, Courtney.
I’m able to reproduce your issue [1]
Can you, please, confirm - Do you have use-case when memberIds contains more
then one element?
Is it return correct results?
Before 2.11 SQL query with IN clause and array argument executed and return
some results.
But, in my reproducer res
