Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

boundary_step!=0 on ATTACH INDEX error #172

drewblin opened this issue Mar 6, 2019 · 1 comment

boundary_step!=0 on ATTACH INDEX error #172

drewblin opened this issue Mar 6, 2019 · 1 comment


Copy link

@drewblin drewblin commented Mar 6, 2019

Describe the environment

Manticore Search version: 2.7.5

OS version: FreeBSD 11.2-RELEASE-p4

Describe the problem

Description of the issue:

I have plain index with phrase_boundary_step = 1000
And i have similar RT index also with phrase_boundary_step = 1000

And when i call
attach index prod_v2_plain to rtindex prod_v2 with truncate
i get error
ERROR 1064 (42000): ATTACH currently requires boundary_step=0 in disk index (RT-side support not implemented yet)

But RT index works as expected with phrase_boundary_step if i fill it via SQL. So, it is implemented on RT-side.
I’m not sure, buy may be it is already possible to attach such indexes?

Changelog: fixed phrase_boundary setting at RT index and on attaching plain index to RT

Copy link

@tomatolog tomatolog commented Mar 6, 2019

I've just fixed this issue at 6a217f6
However to make it work it might be better to stop daemon remove index files for RT index with phrase_boundary settings used then reindex data there from scratch via regular insert or plain attach.

As prior to fix RT index save disk chunk with that option disabled, phrase_boundary_step set to 0 that is why I was sure disk chunks of RT index get wrong matches.
I'd also suggest to reindex from scratch as old disk chunks with that option might screw new disk chunk (got from plain index) on optimize.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants