Hello,
The activity table is 121823 records and the activityuseraccountrole 1027839
records.
First one runs under a second and produces:
/SELECT DISTINCT
ACTIVITY0._KEY,
ACTIVITY0._VAL,
ACTIVITY0.ACTIVITY_ID,
ACTIVITY0.TIMESTAMP,
ACTIVITY0.CONTAINER_ID,
ACTIVITY0.ACTIVITYTYPE_ID,
ACTIVITY0.REALIZATION_ID,
ACTIVITY0.KERNEL_ID,
ACTIVITY0.PREDECESSORTYPE_ENUMID,
ACTIVITY0.SUCCESSORTYPE_ENUMID,
ACTIVITY0.DURATIONUNIT_ENUMID,
ACTIVITY0.NAME,
ACTIVITY0.NAME_MLID,
ACTIVITY0.DESCRIPTION,
ACTIVITY0.DESCRIPTION_MLID,
ACTIVITY0.DURATION,
ACTIVITY0.REQUIRED,
ACTIVITY0.ESTIMSTARTDATE,
ACTIVITY0.ESTIMSTARTHOUR,
ACTIVITY0.ESTIMENDHOUR,
ACTIVITY0.ESTIMENDDATE,
ACTIVITY0.REMOVEFROMWORKLIST,
ACTIVITY0.SEQUENCENR,
ACTIVITY0.SESSION_ID,
ACTIVITY0.LASTACTIVITY_ID,
ACTIVITY0.SYSREPOPERATION_ID,
ACTIVITY0.LIFECYCLEREPORTING,
ACTIVITY0.DUEDATE,
ACTIVITY0.PRIORITY_ENUMID,
ACTIVITY0.NOTIFY
FROM "Activity".ACTIVITY ACTIVITY0
/* "Activity".ACTIVITY.__SCAN_ */
/* scanCount: 121824 *//
The seconds one also very fast and produces:
/SELECT DISTINCT
ACTIVITYUSERACCOUNTROLE0._KEY,
ACTIVITYUSERACCOUNTROLE0._VAL,
ACTIVITYUSERACCOUNTROLE0.ACTIVITY_ID,
ACTIVITYUSERACCOUNTROLE0.USERACCOUNTROLE_ID
FROM "Activity".ACTIVITYUSERACCOUNTROLE ACTIVITYUSERACCOUNTROLE0
/* "Activity".ACTIVITYUSERACCOUNTROLE.__SCAN_ */
/* scanCount: 1027840 */
WHERE ACTIVITYUSERACCOUNTROLE0.USERACCOUNTROLE_ID IN(1, 3)/
So basically, the join seems to kill it?
br
jan
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Unexpected-performance-issue-with-SQL-query-followed-by-error-tp4726p5239.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
