Closed Bug 1111536 Opened 11 years ago Closed 11 years ago

[Super Search Fields] Storage mapping is not used for fields in a sub-namespace

Categories

(Socorro Graveyard :: Middleware, defect, P1)

Product:
Socorro Graveyard
Component:
Middleware
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: adrian, Assigned: adrian)

Details

I am seeing that the field 'processed_crash.json_dump.write_combine_size' has been set a storage mapping, but it is not being reflected in the Elasticsearch mapping. Other fields without a dot in the namespace work as expected.
Status: NEW → ASSIGNED
Priority: -- → P1
I can't reproduce this problem anymore. No idea what happened.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
Commits pushed to master at https://github.com/mozilla/socorro https://github.com/mozilla/socorro/commit/bc58e44187c298d3e448c5071a7c76081b446d53 Bug 1111536 - Improved get_mapping unit tests. https://github.com/mozilla/socorro/commit/1a05d08082e7d685e195bb12fd5b44a076eed23f Merge pull request #2548 from AdrianGaudebert/1111536-super-search-fields-sub-namespace-mapping Bug 1111536 - Improved get_mapping unit tests.
Product: Socorro → Socorro Graveyard
You need to log in before you can comment on or make changes to this bug.