search

edgedb / rfcs

RFCs for major changes to EdgeDB
Apache License 2.0
35 stars 5 forks source link

RFC 1017: Abstract index #66

Closed vpetrovykh closed 1 year ago

vpetrovykh commented 1 year ago

Add a way to define different indexes in extensions and built-in modules. Also provide a way for users to define custom indexes extending existing ones with some of the parameters set to specific values.

msullivan commented 1 year ago

Could you update with an example of the parameter overriding mechanism in use? I'm having a little trouble fully visualizing it

tailhook commented 1 year ago

Yes, this definitely needs some examples.

Also my primary concern is what will be defined here. Because there was some discussion in slack about making address of the full-text search index server a part of the (abstract) index definition. Which is not something that would work well (server address must be a part of the configuration and differs on production and staging servers).

vpetrovykh commented 1 year ago

I've split the huge index RFC into several parts since they tackle fairly different aspects of indexes.

This portion is now trimmed and mostly concerns itself with simple abstract indexes exposing built-in Postgres index types. There's a question of how we define which types are indexable as well as where and how the SQL that is needed to define an index should be specified.