Bug #24444 | Please add FEDERATED query feature | ||
---|---|---|---|
Submitted: | 20 Nov 2006 18:36 | Modified: | 5 Nov 2009 12:51 |
Reporter: | Roland Bouman | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Federated storage engine | Severity: | S4 (Feature request) |
Version: | NA | OS: | Any (NA) |
Assigned to: | CPU Architecture: | Any | |
Tags: | federated, query, VIEW |
[20 Nov 2006 18:36]
Roland Bouman
[20 Nov 2006 23:22]
Sergey Petrunya
Timour had an idea of achieving a similar effect by doing "the opposite": let the optimizer at frontend detect a case when we have a join of several remote tables from the same backend, and push the join operation down to that backend. This "opposite" way seems to be more generic/powerful, but on the other hand it may be harder to implement. There are no specs for either variant yet, so it's hard to tell whether implementation of Timour's idea will provide everything that Roland requests (or vice versa). In any case, whoever picks up this bug should check with Timour.
[21 Nov 2006 7:07]
Roland Bouman
Thanks sergey! I think the pushdown according to Timour's plan is wonderful too. In some ways it might be more flexible. However, my proposal is different, and also flexible but in other wasys. My initial requirement is actually very simple and straight forward, and you will probably notice immeditately why you cannot solve it using the proposed approach by Timour: create table mysql_remote_version( version varchar(12) not null ) engine=federated connection='mysql://user@host//select version()' or even create table mysql_remote_proc( id int ) engine=federated connection='mysql://user@host//call procname()' (this second one is just an idea)