-
Notifications
You must be signed in to change notification settings - Fork 36
Schema toml format doesn't describe how to specify indexes #71
Comments
Still Example react-chat-app $ rethinkdb $ hz get-schema
$ hz serve --permissions no Browse localhost:8181 RethinkDB Administration Console
schema.toml file
config.toml file
|
@SenerDemiral This is an issue about documentation. There is a different tracker for issues with Horizon itself. I moved your comment over to there: rethinkdb/horizon#533 |
The current format is each field in the index, concatenated in order, delimited by underscores. Undescores and backslashes in field names are escaped with backslashes. Examples:
There is an open issue to replace the naming scheme with JSON names, which will be a bit more readable and allows nested fields to be indexed: rethinkdb/horizon#444 |
If you create a horizon app using
--auto-create-collection
and--auto-create-indexes
, and then dohz get-schema
on it, you will get stuff that looks like:These index names have a particular format that tells horizon how to create the index when it's passed back to
set-schema
, but this isn't documented anywhere. We should document it so people are able to specify their indexes without needing to have horizon autogenerate them first.@Tryneus can probably give us exact details on how the mapping works
The text was updated successfully, but these errors were encountered: