Filter by reset
- Everywhere
16956 - Issues
2152 - Pull Requests
1063 - Comments
13741
Added CLT integration test for Kafka partition-based data ingestion
Type of Change: New feature - Added CLT integration test for Kafka partition-based data ingestion Description of the Change: Added comprehensive CLT test to verify partition-based Kafka ingestion functionality in Manticore Search Buddy. Creates separate β¦
done
ci: fixed a bug in dist/test_kit_docker_build.sh which resulted in missing buddy commit
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)
Fulltext search efficiency improvement
Consider the request: SELECT ut FROM listing WHERE match('T14180 "2004 ΡΠ°ΡΠ½Π° ΠΊΠΈΡΠ°ΠΉΡΠΊΠΈΠΉ Π³ΠΎΡΠΎΡΠΊΠΎΠΏ 5 ΠΌ"/0.5') LIMIT 0,100 OPTION max_predicted_time=100, max_matches=100; Meta: +---------------------+---------------------+ | Variable_name | Value | β¦
est::NO_ESTIMATE
join search crashed when using string not int
bug
Created test-support-logstash-versions.rec
Type of Change (select one): New feature Description of the Change: Related Issue (provide the link):
Wrong error "Undefined array key "Field"
bugbuddy_candidate
Migration support using tools like sqlx migate or flyway
Proposal: I want to be able to manage a manticore db schema using migration files so that I have a repeatable flow for different environment. e.g a migrations directory with the SQL code to create / update tables like migrations/1_init_tables.sql , β¦
waiting
π Update backup version from 1.9.1 to 1.9.5
API response /search return a doc id as uint64 instead of int64
Bug Description: The API documentation specifies that the response doc _id should be a signed int64 int64 , but in practice, it returns an unsigned ( uint64 ). Although this discrepancy does not affect my use case, it deviates from the intended design. β¦
bug
API response /search return a doc id as uint64 instead of int64
bug
How to solove table left join query slowly?
chat_log1 left join chat_log2 cost time 14 seconds, chat_log1 has 2.5w datas, chat_log2 has 2.6w datas, SQL: select * from chat_log1 left join chat_log2 on chat_log1 .app_id = chat_log2 .app_id; Create table: ` CREATE TABLE chat_log1 ( id bigint, response β¦
waiting
Test coverage for bidirectional log level synchronization between Manticore and Buddy
test(clt): add regression test for offset out of bounds error
integration of Manticore with Filebeat
est::size_M
CLT: update tests to latest updates and fixes in buddy to autosharding
Consider using CDN to accelerate downloads for repo.manticoresearch.com
Is your feature request related to a problem? Please describe. It takes many minutes to install manticore search in asia. repo.manticoresearch.com seems randomly very slow. Describe the solution you'd like Consider using CDN to accelerate downloads for β¦
π Update buddy version from 3.29.7 to 3.30.0
Describe the bug When systemd is updated on RHEL 8 with manticore search installed the following errors occur: [/usr/lib/tmpfiles.d/searchd.conf:1] Line references path below legacy directory /var/run/, updating /var/run/manticore β /run/manticore; please β¦
System Variables and Query Parsing Inconsistencies in Manticore Search
Manticoresearch repo is not available in Debian extrepo
Bug Description: Many famous 3rd party software repo is available in extrepo in Debian. Can you please add your Debian repo into extrepo ? Because that will allow user to just execute extrepo enable manticoresearch and setup manticoresearch's Debian repo β¦
bug
How to solove table left join query slowly?
waiting
π Update buddy version from 3.30.0 to 3.30.2
Update buddy version from 3.30.0 to 3.30.2 which includes: c16d9c2 fix(network): improve error debug and conditional logging
error: cannot use 'typeid' with '-fno-rtti' when building on Debian 11
Facet search by float RANGE() not working
Bug Description: DROP TABLE IF EXISTS test_interval_and_range; CREATE TABLE test_interval_and_range(volume float); DESC test_interval_and_range; +--------+--------+------------+ | Field | Type | Properties | +--------+--------+------------+ | id | bigint β¦
bug
π Update mcl version from 4.2.2 to 5.0.1
Escaping does not work with reserved keywords
Describe the bug Escaping does not work with reserved keywords in the query. To Reproduce Steps to reproduce the behavior: mysql> create table t(`year` int); mysql> create table t(`facet` int); mysql> create table t(`order` int); Expected behavior The β¦
est::size_Srel::upcoming
Added CLT integration test for Kafka partition-based data ingestion
done
fix(kafka): add debug logging to nightly test startup
Secondary indexes for json attributes don't work with in() expressions
bugrel::7.0.0
joining by json_attr.string doesn't work
Bug Description: MRE: snikolaev@dev2:~$ mysql -P9306 -h0 -e "drop table if exists t; drop table if exists t2; create table t(f text, s string, j json); create table t2(f text, s string, j json); insert into t values(1, 'abc', 'string', '{\"i\": 1, \"b\": β¦
bugest::size_Srel::upcomingfeature::join
Proposal: Currently we have almost the same modes that daemon has in buddy --debug --debugv --debugvv The idea is to map our log_level from config and also those that change in Runtime to Buddy starting command and append proper debug level in case set, β¦
enhancementest::size_M
move lemmatize_uk.so to /usr/share/manticore/modules/
JOIN query on json attribute returns null
Bug Description: mysql -P9306 -h0 -e 'create table t1(f1 json)' mysql -P9306 -h0 -e 'create table t2(f2 json)' mysql -P9306 -h0 -e "insert into t1(f1) values('{\"f\":\"a\"}')" mysql -P9306 -h0 -e "insert into t2(f2) values('{\"g\":\"a\"}')" mysql -P9306 - β¦
bug
π Update mcl version from 4.2.2 to 5.0.1
If data is being written, execute group by to obtain duplicate data
Bug Description: οΌ1οΌcolumnar table: mysql> desc test_table; +-----------+-----------+---------------------+ | Field | Type | Properties | +-----------+-----------+---------------------+ | id | bigint | columnar fast_fetch | | biz_code | string | columnar β¦
bug
Added CLT integration test for Kafka partition-based data ingestion
done
Proposal: Auto create column/s inside existing schema when new field is observed in incoming data! Reference: https://www.elastic.co/guide/en/elasticsearch/reference/current/dynamic-mapping.html https://www.elastic.co/guide/en/elasticsearch/reference/ β¦
est::NO_ESTIMATE
Auto UUID creation seems improper? Existing docs getting overwritten even with insert operation
bugwaiting