Confirmed users
513
edits
BMO/ElasticSearch: Difference between revisions
Jump to navigation
Jump to search
→Update (January 9th, 2014)
Klahnakoski (talk | contribs) |
Klahnakoski (talk | contribs) |
||
| Line 118: | Line 118: | ||
* ElasticSearch was not meant for direct public access, proxy added (https://bugzilla.mozilla.org/show_bug.cgi?id=879833) | * ElasticSearch was not meant for direct public access, proxy added (https://bugzilla.mozilla.org/show_bug.cgi?id=879833) | ||
= Update (January 9th, 2014) = | == Update (January 9th, 2014) == | ||
Over this past couple of months security reviews have been completed, and the suggested enhancements have been implemented. | Over this past couple of months security reviews have been completed, and the suggested enhancements have been implemented. | ||
== ETL Highlights == | === ETL Highlights === | ||
=== Alias Analysis === | ==== Alias Analysis ==== | ||
All bugs have a carbon copy (CC) list of users that are mailed when the bug changes. The historical record of this list is kept as a list of added and removed email addresses, with timestamps of course. An issue arises when the user changes their email address: The next change in the historical record will refer to the new email address, and not the old, looking something like this: | All bugs have a carbon copy (CC) list of users that are mailed when the bug changes. The historical record of this list is kept as a list of added and removed email addresses, with timestamps of course. An issue arises when the user changes their email address: The next change in the historical record will refer to the new email address, and not the old, looking something like this: | ||
| Line 154: | Line 154: | ||
[https://github.com/klahnakoski/Bugzilla-ETL/blob/711810f08951a731dc543c10a0973fc34ed17c6b/bzETL/alias_analysis.py Alias Analysis Code] | [https://github.com/klahnakoski/Bugzilla-ETL/blob/711810f08951a731dc543c10a0973fc34ed17c6b/bzETL/alias_analysis.py Alias Analysis Code] | ||
=== Proving Correctness === | ==== Proving Correctness ==== | ||
Bugzilla contains some bugs that should not be made public. These include bugs with specific security concerns, but also infrastructure specific details and other sensitive items. It is important that these do not leak. Making unit and functional tests is not enough because they can only test the known unknowns. The unknown unknowns are inevitable in any code with reasonable complexity and you can not test for those explicitly. Instead I want to perform the easier task of testing against invariants: | Bugzilla contains some bugs that should not be made public. These include bugs with specific security concerns, but also infrastructure specific details and other sensitive items. It is important that these do not leak. Making unit and functional tests is not enough because they can only test the known unknowns. The unknown unknowns are inevitable in any code with reasonable complexity and you can not test for those explicitly. Instead I want to perform the easier task of testing against invariants: | ||