Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Tommaso Teofili
2014-06-04 9:36 GMT+02:00 Thomas Mueller muel...@adobe.com: Hi, QueryIndex.getCost: this is actually quite well documented (see the Javadocs). But the implementations might not fully follow the contract :-) this is probably just my opinion but the contract is not much clear; to me finding

Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Davide Giannella
On 18/06/2014 10:26, Tommaso Teofili wrote: it would be ok for me to either deprecate it or improve the semantics of the cost calculation (e.g. explicitly introduce other metrics to be taken into account in the cost calculation: local / remote index, With the IndexPlan.isDelayed() we instruct

Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Thomas Mueller
Hi, QueryIndex.getCost my doubt is what this heuristic function to estimate the traversed entries should look like in general Relational databases typically know the number of entries in the index (total indexed entries), plus the selectivity of a column. See also

Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Jukka Zitting
Hi, On Wed, Jun 18, 2014 at 4:26 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: should we just return the number of estimated entries for the cost? Yes, that's what I think the contract should be. My other concern on this point is that it's not granted, in my opinion, that the index

Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Jukka Zitting
Hi, On Wed, Jun 18, 2014 at 7:44 AM, Thomas Mueller muel...@adobe.com wrote: My other concern on this point is that it's not granted, in my opinion, that the index returning less entries would be the faster. Yes, it's not that much about less entries or more entries, it's about lower or higher

Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Tommaso Teofili
ok, thanks Davide for the pointers. Regards, Tommaso 2014-06-18 13:36 GMT+02:00 Davide Giannella giannella.dav...@gmail.com: On 18/06/2014 10:26, Tommaso Teofili wrote: it would be ok for me to either deprecate it or improve the semantics of the cost calculation (e.g. explicitly introduce

Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Tommaso Teofili
Hi, 2014-06-18 13:44 GMT+02:00 Thomas Mueller muel...@adobe.com: Hi, QueryIndex.getCost my doubt is what this heuristic function to estimate the traversed entries should look like in general Relational databases typically know the number of entries in the index (total indexed entries),

Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Tommaso Teofili
Hi, 2014-06-18 16:02 GMT+02:00 Jukka Zitting jukka.zitt...@gmail.com: Hi, On Wed, Jun 18, 2014 at 4:26 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: should we just return the number of estimated entries for the cost? Yes, that's what I think the contract should be. ok, that's

Re: [DISCUSS] - QueryIndex selection

2014-06-18 Thread Jukka Zitting
Hi, On Wed, Jun 18, 2014 at 11:31 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: 2014-06-18 16:02 GMT+02:00 Jukka Zitting jukka.zitt...@gmail.com: On Wed, Jun 18, 2014 at 4:26 AM, Tommaso Teofili tommaso.teof...@gmail.com wrote: should we just return the number of estimated entries for