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 rela
Any thoughts on this?
On Mon., Jul. 25, 2022, 11:29 a.m. John Smith,
wrote:
> Hi I have the following code and I get the below exception. The cache runs
> on 3 remote nodes and it is accessed by thick client (client = true)
>
> String sql = "select car_id from car_code where provider_id = ? and
Hi Taras,
OK, I’ll try to get this later today.
Thanks
Thomas.
On 29.07.22 at 12:49, Taras Ledkov wrote:
> Hi,
>
> Could you provide the original exception from the map node?
> It must be available at the log files of the map node.
>
Hi,
Could you provide the original exception from the map node?
It must be available at the log files of the map node.
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?
Thanks
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: javax.cache.CacheExcept
