Migration code does not respect SEARCH_INDEX #661

New issue

Closed

opened 2019-08-28 05:13:16 +00:00 by RAOF · 1 comment

RAOF commented

2019-08-28 05:13:16 +00:00

(Migrated from github.com)

Run plm migration run in a read-only directory, with the SEARCH_INDEX environment variable pointing at a writable directory.
plm migration run will error out with:

Running migration 20190428201506
thread 'main' panicked at 'Failed to run migrations: Search(IndexCreationError)', src/libcore/result.rs:997:5

As far as I can tell this is because up.sql doesn't check the SEARCH_INDEX variable, although it's not entirely obvious what the contents of path passed in there is.

Run `plm migration run` in a read-only directory, with the `SEARCH_INDEX` environment variable pointing at a writable directory. `plm migration run` will error out with: ``` Running migration 20190428201506 thread 'main' panicked at 'Failed to run migrations: Search(IndexCreationError)', src/libcore/result.rs:997:5 ``` As far as I can tell this is because `up.sql` doesn't check the `SEARCH_INDEX` variable, although it's not entirely obvious what the contents of `path` passed in there is.

RAOF commented

2019-08-28 23:45:59 +00:00

(Migrated from github.com)

For those playing at home, this can be mostly worked around by passing --path to plm, pointing to the parent directory of search_index. This does require that your search index directory is called search_index, but if your search index is /path/to/search_index then
plm migration run --path /path/to/ will correctly perform the migrations.

For those playing at home, this can be mostly worked around by passing `--path` to `plm`, pointing to the parent directory of `search_index`. This does require that your search index directory is *called* `search_index`, but if your search index is `/path/to/search_index` then `plm migration run --path /path/to/` will correctly perform the migrations.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#661

No description provided.

Rows
Columns