lokeshj1703 opened a new pull request, #12349:
URL: https://github.com/apache/hudi/pull/12349
### Change Logs
We have to ensure users intuitively understand what we are shipping. Let's
align with existing terminology of a popular database than inventing our own
"names".
Postgres uses "Expression indexes" . and we can change our terminology to be
the same.
- References to "Functional Index" in docs/code/RFC changes to "Expression
Index"
- "func" becomes "expr" (no need to change syntax with an "expression"
clause like pg yet.
- Change anything in storage like prefix "func_index_" or the
hoodiemetadata.avsc fields or the index defs files. (need to be really really
thorough)
Here's how we need the experience to be.
```
CREATE INDEX name ON table (primaryKeyColumn); -- should create RLI
effectively, alternatively `WHERE primaryKeyColumn = | IN ` has to work with
RLI is enabled via Streamer/Datasource config. Need to test/confirm this.
CREATE INDEX name ON table (someOtherColumn); -- should create
secondary_index backed by RLI, remove secondary_index as an option in using
clause, if no index type is specified SI is the default.
CREATE INDEX name ON table USING BLOOM_FILTERS(column)
options(expr='lower'); -- build a bloom filter from lower case version of column
CREATE INDEX name ON table USING COL_STATS(column)
options(expr='from_unixtime', format='yyyy-MM-dd'); -- build date based
indexing of ts column
CREATE INDEX name ON table USING COL_STATS(column); -- should just add to
the column stats? (or) should we disallow this for now?
```
### Impact
_Describe any public API or user-facing feature change or any performance
impact._
### Risk level (write none, low medium or high below)
_If medium or high, explain what verification was done to mitigate the
risks._
### Documentation Update
_Describe any necessary documentation update if there is any new feature,
config, or user-facing change. If not, put "none"._
- _The config description must be updated if new configs are added or the
default value of the configs are changed_
- _Any new feature or user-facing change requires updating the Hudi website.
Please create a Jira ticket, attach the
ticket number here and follow the
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to
make
changes to the website._
### Contributor's checklist
- [ ] Read through [contributor's
guide](https://hudi.apache.org/contribute/how-to-contribute)
- [ ] Change Logs and Impact were stated clearly
- [ ] Adequate tests were added if applicable
- [ ] CI passed
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
