dutchcoders / dutchcoders/marija
[query_string] query does not support [all_fields] and cannot use [all_fields] parameter in conjunction with [default_field] or [fields]
- Dominant language
- Go
- Stars
- 234
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
I want to use marija with docker. I have 2 docker containers. one with marija and one with elasticsearch.
I seeded some fake data, the index looks like this:
GET es:9200/test_persons
```
{
"test_persons": {
"aliases": {},
"mappings": {
"person": {
"properties": {
"city": {
"type": "string"
},
"company": {
"type": "string"
},
"country": {
"type": "string"
},
"email": {
"type": "string"
},
"name": {
"type": "string"
}
}
}
},
"settings": {
"index": {
"creation_date": "1551956277080",
"number_of_shards": "5",
"number_of_replicas": "1",
"uuid": "xxxxxx",
"version": {
"created": "2040699"
}
}
},
"warmers": {}
}
}
```
I tried a whole lot of different elasticsearch versions in docker
My config of marija looks like this:
config-docker.toml
```
[datasource]
[datasource.test_persons]
type="elasticsearch"
url="http://es:9200/test_persons"
[[loggings]]
output = "stdout"
level = "debug"
```
I am not so experienced with elasticsearch, I hope it is just a stupid mistake. Can someone help me?
Contributor guide
Research direction
Start by reproducing the query_string behavior with the Elasticsearch datasource configured in config-docker.toml. Trace how Marija builds query_string requests and compare handling of all_fields, default_field, and fields. Done means all_fields is supported and its parameter combinations behave as described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, elasticsearch, go
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100