Hi,
I am Richa Sehgal currently pursuing Master’s at University of Illinois Urbana Champaign, USA. I did my undergraduate from Indian Institute of Technology Delhi (IIT-Delhi). I would like to take this up as my GSoC project.
Materialization gives us two things:
1. A name to the column which we can use in queries
2. A formal "regular" column which is stored and indexed in the regular fashion - Disadvantage: Extra memory requirements for the materialized column.
My initial thoughts on this project are the following:
We do need the name of the column which can be used to query. So maybe we can expose a command such as:
create virtual_index <name> on <column_name> <expression>
What this would do would run a regular query which evaluates expressions (like in WHERE clause) and the feed the result into the indexer. This index can then be stored in the regular fashion.
Am I approaching this in the right direction? Can you please point me to the next steps?
Thanks
Richa
MDEV-6017 Add support for Indexes on Expressions
Hi,
I am Richa Sehgal currently pursuing Master’s at University of Illinois Urbana Champaign, USA. I did my undergraduate from Indian Institute of Technology Delhi (IIT-Delhi). I would like to take this up as my GSoC project.
Materialization gives us two things:
1. A name to the column which we can use in queries
2. A formal "regular" column which is stored and indexed in the regular fashion - Disadvantage: Extra memory requirements for the materialized column.
My initial thoughts on this project are the following:
We do need the name of the column which can be used to query. So maybe we can expose a command such as:
create virtual_index <name> on <column_name> <expression>
What this would do would run a regular query which evaluates expressions (like in WHERE clause) and the feed the result into the indexer. This index can then be stored in the regular fashion.
Am I approaching this in the right direction? Can you please point me to the next steps?
Thanks
Richa