Hi Siva,
Not sure if this guess is correct, but it's likely that the LEFT OUTER JOIN
produces some rows that has the fields from the second table as null
values, and in that case the WHERE condition matters. Since the WHERE
clause is always true for the second table, the first query should be
equi
Hi Maryann,
Thanks for your response.
Here is the count of records in second table with and without filter. In
this case, whether the filter is in where clause (or) on clause should get
the same number of records. Initially, I tried to debug the data, but could
not find any issue with data.
0: j
Hi Siva,
This is an expected behavior and therefore is not a bug.
For outer joins, condition specified in the ON clause would have different
effects than specified in the WHERE clause. If specified in the WHERE
clause, the join operation happens first and the condition is applied on
the join resu
Hi Everyone,
Are there any known bugs on Left joins in Phoenix
Here are the two queries with same conditions resulting different set of
records.
0: jdbc:phoenix:172.31.45.176:2181:/hbase> select count(*) from
. . . . . . . . . . . . . . . . . . . . .> (select rowkey, "typeid" as
typeid, to_numb
