Hi Doug,
_key is implicitly indexed, no need to configure additional index for it.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/odd-query-plan-with-joins-tp13680p14279.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
quot; as an indexed field within the the table? Or is it considered
"proper" to do a join using using "_key"?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/odd-query-plan-with-joins-tp13680p13728.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
CM__Z0.PERIOD, P__Z1.ROOM_TYPE, P__Z1.BEDROOMS, P__Z1.PROPERTY_ID
>
> SELECT
> __C0_0 AS PROPERTY_ID,
> (CAST(SUM(__C0_1) AS REAL) / (SUM(__C0_5) + SUM(__C0_6))) AS OCC_RATE,
> __C0_2 AS BEDROOMS,
> __C0_3 AS PERIOD,
> __C0_4 AS ROOM_TYPE
> FROM PUBLIC.__T0
> /* CalendarMetricCache.merge_scan */
> GROUP BY __C0_3, __C0_4, __C0_2, __C0_0
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/odd-query-plan-with-joins-tp13680.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
OOM_TYPE
FROM PUBLIC.__T0
/* CalendarMetricCache.merge_scan */
GROUP BY __C0_3, __C0_4, __C0_2, __C0_0
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/odd-query-plan-with-joins-tp13680.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
