[MDEV-10698] Extend Storage Engine API to include estimate of full-text search Created: 2016-08-29 Updated: 2016-10-09 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major |
| Reporter: | Rasmus Johansson (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
When the optimizer looks for a best execution plan, it needs to know how many rows a particular condition can match. For historical reasons a full-text search query that uses a full-text index is always assumed to return 1 row. While it is kind of correct for a NL full-text search, it is definitely wrong for a boolean full-text search. For storage engines like Mroonga to be able to provide the optimizer with an estimate of the row count of a full-text search the Storage Engine API need to be updated with functions for the storage engines to provide the estimate. |
| Comments |
| Comment by Rasmus Johansson (Inactive) [ 2016-08-29 ] |
|
serg can you verify the description and maybe specify a bit more in detail what needs to be done. |
| Comment by Justin Swanhart (Inactive) [ 2016-08-29 ] |
|
Perhaps an extensible index should be supported like pgsql has. Basically you can plug any kind of index you want into postgresql. I would like to be able to add bitmap and range indexes for example. |