Re: Apache Ingite Join returns wrong records
Hello! I don't think so. But you can set it on JDBC connection level. Regards, -- Ilya Kasnacheev пн, 1 окт. 2018 г. в 16:14, Skollur : > Is there setDistributedJoins at cache level? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Re: Apache Ingite Join returns wrong records
Is there setDistributedJoins at cache level? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Apache Ingite Join returns wrong records
Hello! Of course, if Account_Type is reasonably well distributed you could just make it the affinity key. Regards, -- Ilya Kasnacheev сб, 29 сент. 2018 г. в 3:48, Andrey Mashenkov : > Hi, > > Try to use qry.setDistributedJoins(true). This should always return > correct result. > > However, it has poor performance as due to intensive data exchange between > nodes. > > By default, Ignite join only the data available locally on each node. Try > to collocate your data to get better performance with non distributed joins. > > сб, 29 сент. 2018 г., 3:39 Skollur : > >> I am using Apache Ignite 2.6 version. I have two tables as below i.e >> SUMMARY >> and SEQUENCE >> >> SUMMARY-> DW_Id bigint (Primary key) , Sumamry_Number varchar, >> Account_Type >> varchar >> SEQUENCE-> DW_Id bigint (Primary key) , Account_Type varchar >> >> Database and cache has same number of records in both tables. Database >> JOIN >> query returns 1500 counts/records and However IGNITE JOIN returns only 4 >> counts and 4 records. Ignite cache is build based on auto generated web >> console. Query used is as below. There is no key involved while joining >> two >> cache tables here from two cache.tables. This is simple join based on >> value(i.e account type - string). How to get correct value for JOIN in >> Ignite? >> >> SELECT COUNT(*) FROM SUMMARY LIQ >> INNER JOIN SEQUENCE CPS ON >> LIQ.Account_Type = CPS.Account_Type >> >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >
Re: Apache Ingite Join returns wrong records
Hi, Try to use qry.setDistributedJoins(true). This should always return correct result. However, it has poor performance as due to intensive data exchange between nodes. By default, Ignite join only the data available locally on each node. Try to collocate your data to get better performance with non distributed joins. сб, 29 сент. 2018 г., 3:39 Skollur : > I am using Apache Ignite 2.6 version. I have two tables as below i.e > SUMMARY > and SEQUENCE > > SUMMARY-> DW_Id bigint (Primary key) , Sumamry_Number varchar, Account_Type > varchar > SEQUENCE-> DW_Id bigint (Primary key) , Account_Type varchar > > Database and cache has same number of records in both tables. Database JOIN > query returns 1500 counts/records and However IGNITE JOIN returns only 4 > counts and 4 records. Ignite cache is build based on auto generated web > console. Query used is as below. There is no key involved while joining two > cache tables here from two cache.tables. This is simple join based on > value(i.e account type - string). How to get correct value for JOIN in > Ignite? > > SELECT COUNT(*) FROM SUMMARY LIQ > INNER JOIN SEQUENCE CPS ON > LIQ.Account_Type = CPS.Account_Type > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
Apache Ingite Join returns wrong records
I am using Apache Ignite 2.6 version. I have two tables as below i.e SUMMARY and SEQUENCE SUMMARY-> DW_Id bigint (Primary key) , Sumamry_Number varchar, Account_Type varchar SEQUENCE-> DW_Id bigint (Primary key) , Account_Type varchar Database and cache has same number of records in both tables. Database JOIN query returns 1500 counts/records and However IGNITE JOIN returns only 4 counts and 4 records. Ignite cache is build based on auto generated web console. Query used is as below. There is no key involved while joining two cache tables here from two cache.tables. This is simple join based on value(i.e account type - string). How to get correct value for JOIN in Ignite? SELECT COUNT(*) FROM SUMMARY LIQ INNER JOIN SEQUENCE CPS ON LIQ.Account_Type = CPS.Account_Type -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/