Tested SqlQueriesExample.java of ignite 2.13.0 - the inside sqlQueryWithJoin
method, it still prints out below warning message when executing the join sql
on COLLOCATED_PERSON_CACHE. So that's a false positive ?
[ WARN] - For join two partitioned tables join condition should contain the
equality
6733...@qq.com>
Sent: Tuesday, June 13, 2023 1:24:48 AM
To: user
Subject: Re: Ignite Affinity - sql join Question
No luck. With the change its throwing exception BinaryObjectImpl cannot be
cast to java.lang.String when it tried to put a new entey into "companies"
cache.
B
No luck. With the change its throwing exception BinaryObjectImpl cannot
be cast to java.lang.String when it tried to put a new entey into
"companies" cache.
Beside, there is already the @AffinityKeyMapped annotation on companyId field
of PersioKey class. AffinityKey needs to be marked on sq
y, June 12, 2023 10:46:23 PM
To: Chandranana Naik via user
Subject: Ignite Affinity - sql join Question
hi Igniters,
Can you pls advise below ?
It always prints out below WARN message in server side when I am trying to use
the sql join . Anything wrong with my configuration or testing code ? Is
hi Igniters,
Can you pls advise below ?
It always prints out below WARN message in server side when I am trying to use
the sql join . Anything wrong with my configuration or testing code ? Is
it possible to eliminate that WARN message ?
[ WARN] org.apache.ignite.internal.processors.qu
Hello!
Can you please share a runnable reproducer project exposing this issue?
Regards,
--
Ilya Kasnacheev
пт, 22 мая 2020 г. в 19:54, narges saleh :
> Sorry for the late reply.
> I have defined the affinity via cacheKeyConfiguration in ignite config
> file and it is working fine, if I use JD
Sorry for the late reply.
I have defined the affinity via cacheKeyConfiguration in ignite config file
and it is working fine, if I use JDBC connection.
But it does seem the issue is with the affinity key population, not
definition, in case of binary objects. I must be doing something wrong. I
am tr
Hello!
It is possible that Data Streamer is not actually aware of affinity column
of your table. Can you try marking it with @AffinityKeyMapped?
Regards,
--
Ilya Kasnacheev
вт, 19 мая 2020 г. в 01:48, narges saleh :
> It seems the issue exist only if one uses data streamer with binaryobject
>
It seems the issue exist only if one uses data streamer with binaryobject
builder. If I use straight JDBC to insert data, the issue goes away. Any
idea what one needs to do to get this working with binary objects?
Everything else is the same between the two scenarios.
On Mon, May 18, 2020 at 4:39
It turned out that I'd get partial results in some cases, when joining
partitioned caches. But I still don't understand why I am not getting all
the rows that the joined query should return.
My assumption is that if you have caches with primary keys, containing the
affinity key, then the related en
No error. Just no records is returned, as opposed to the join between the
replicated and partitioned cache which returns ass applicable rows. Sorry,
for not being clear.
On Mon, May 18, 2020 at 9:00 AM Ilya Kasnacheev
wrote:
> Hello!
>
> Fails how? Is the result set incorrect? Any specific error
Hello!
Fails how? Is the result set incorrect? Any specific error message? Please
share details.
Regards,
--
Ilya Kasnacheev
пн, 18 мая 2020 г. в 16:49, narges saleh :
> Hi All,
> I have encountered a puzzling join case.
> I have 3 tables on a cluster of two ignite server nodes:
> table-A (id
Hi All,
I have encountered a puzzling join case.
I have 3 tables on a cluster of two ignite server nodes:
table-A (id + org = primary), replicated
id
org. <-- affinity
other fields
table-B (id, org, add-id=primary key), partitioned
id
org <- affinity
addr-id
other fields
table-C (id, org, comp-id
13 matches
Mail list logo
