The only other thing I can think of is that I did an upgrade to 2.12.0
On Thu, Aug 4, 2022 at 12:52 PM John Smith wrote:
> Personally I think there is some sort of index corruption. I dropped the
> table and recreated it and my problem went away.
> I never restarted the application and it
Personally I think there is some sort of index corruption. I dropped the
table and recreated it and my problem went away.
I never restarted the application and it started to work again.
Maybe you can make a copy of your table, insert the data fresh and point
your app to the copied table. And see
Hi Taras,
attached the extract from the local node log (which is a Ignite client)
and the remote node log (which is a Ignite server with persistance enabled).
What's really strange is that previous value "IDX_STAGE_308" seems to be
the root cause? This is a value in column UCID but it's not
One additional log I noticed on the server node for these SQL queries;
WARNÂ QueryParser For join two partitioned tables join condition
should contain the equality operation of affinity keys. Left side:
JOBQUEUE; right side: JOBS
Is this a warning or can it cause the below exception?
Hi,
I'm getting (unreliable until now) Exception when executing SQL query in
Ignite 2.13.
It seems to be connected to the parameter for column UCID. When
searching for "6bf1dfc9-311b-432f-9342-257400dcc59e" the below exception
happens on our production server:
Caused by:
