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

Crash on select using multiple indexes, group by and ranker = none #322

Closed
ergnuor opened this issue Mar 31, 2020 · 2 comments
Closed

Crash on select using multiple indexes, group by and ranker = none #322

ergnuor opened this issue Mar 31, 2020 · 2 comments
Assignees
Labels

Comments

@ergnuor
Copy link

ergnuor commented Mar 31, 2020

Describe the environment

Manticore Search version (top line in output of bin/searchd -v or bin/indexer -v):
Manticore 3.3.0 01fc8ad@200204 release

OS version (uname -a if on a Unix-like system):
Linux debian 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) x86_64 GNU/Linux

Build version:
manticore_3.3.0-200204-01fc8ad1-release.buster_amd64-bin.deb

Describe the problem:
searchd crashes under the following conditions:

  1. the search is performed using multiple indexes or a distributed index
  2. GROUP BY is used
  3. OPTION ranker = none is used

Steps to reproduce:

Query examples:

SELECT type_id FROM src_dist GROUP BY type_id OPTION ranker = none;    
SELECT type_id FROM src_1, src_2 GROUP BY type_id OPTION ranker = none;    

The configuration file, test data, crash dump, and other necessary data are provided in the attachment
necessary_data.zip

@ergnuor
Copy link
Author

ergnuor commented Apr 1, 2020

I also noticed that the ranker option appears twice in the query log. Maybe this is related to the bug somehow.

@tomatolog
Copy link
Contributor

I've just fixed daemon crash on ranker none without id at select list at
commit 632bdfd

@tomatolog tomatolog self-assigned this Apr 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants