Closed Bug 733193 Opened 13 years ago Closed 13 years ago

Create and store ElasticSearch's schema in Socorro

Categories

(Socorro :: Database, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: adrian, Assigned: aphadke)

References

Details

(Whiteboard: [qa-])

Attachments

(1 file, 1 obsolete file)

Attached file crash_reports mapping (obsolete) —
Before we start using ElasticSearch in production, we want to make sure the schema we will use for crash reports is correct and robust. Updating it will most likely be a pain, so we want to avoid it as much as possible. Attached is the most recent schema I have.
Blocks: 651279
Assignee: nobody → aphadke
This schema seems to be missing a LOT of fields. Am I not understanding it correctly?
(In reply to [:jberkus] Josh Berkus from comment #1) > This schema seems to be missing a LOT of fields. Am I not understanding it > correctly? ElasticSearch automatically updates the schema when we index a document containing a new field. I don't think we want to have all fields here, but only specific fields where we want a special mapping (or a mapping different from what ES would guess from the value of that field).
Target Milestone: 2.5.2 → 2.5.3
As we updated Socorro to support timezones, and moved to ISO 8601 datetimes, we need to update ES schema. The one attached has a date_format of "yyyy-MM-dd'T'HH:mm:ss.SSSSSSZZ". I also removed all the duplicate date_formats to keep only the default one.
Attachment #603086 - Attachment is obsolete: true
Target Milestone: 3 → 4
Target Milestone: 4 → 5
Ping?
Whiteboard: [qa-]
Target Milestone: 5 → 6
Target Milestone: 6 → 7
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: