manticoresoftware / manticoresoftware/columnar
Crash!!! Handling signal 11 on import to table with multi64 field
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 110
- Forks
- 23
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 8
Description
Doing an import to a table which uses columnar Manticore crashes with message `Crash!!! Handling signal 11`. (SIGSEGV) No further details in query log and it is not related to a specific document. The import always crashes after a few seconds however. I have imported much larger tables with success.
The issue seems to be related to a `multi64` field (which i did not use with the successful tables). When i set `engine='rowwise'` on this field, the issue goes away and i can import the full table.
Global config options on the table are: `engine='columnar' dict='keywords' expand_keywords='1' index_exact_words='1' min_infix_len='3'`
Im on the latest Manticore release 6.0.4 and it's in docker.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the import against a columnar table containing a multi64 field in the reported Docker setup, then compare it with the rowwise workaround. Investigate the import path and existing tests for multi64 and columnar storage; done means the import completes without SIGSEGV while retaining columnar storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, docker
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100