Knowing Lucene and its index structure for years, I wouldn't advise to use a Lucene database as primary storage. Always keep the original data at least in a log-queue or in a separate database - so that you can rebuild the Lucene database.
Obviously incidents like such have made us cautious and we will be working on fixing these architectural issues quickly.
Just wanted to tip you off to what I assume is a typo:
But lack of automated regression testing would have caught this issue.
To explain myself, I meant that tests that were succeeding previously would have failed due to this issue if we had tests written for it. Does my statement not convey this?
> But lack of automated regression testing would have caught this issue.
> To explain myself, I meant that tests that were succeeding previously would have failed due to this issue if we had tests written for it. Does my statement not convey this?
No. The sentence says that the lack (i.e. not having) tests would have caught the issue. If you remove 'But lack of', the sentence makes sense ;)
Wish we had it back then. We are currently on 1.4.
When the patient was brought in, he was barely breathing. Due to the spots on his face, we assumed it was X. Then we made an incision in his pelvis to fix Y. Suddenly, he died. Gosh, we really should have kept an eye on the meter in the corner!
I understand things like litigation, but it makes me wonder to what extent we are being limited in medical achievements. From my outsider point of view, it seems that post mortems (ha!) are not used as much in the medical field other than for insurance / legal reasons.
(add more details here)
Probably a stupid question but why can't ElasticSearch translate both mappings into something like, "products_price", and "promotions_price" before adding to the 'list'?
Fields with the same name, in the same index, in different types,
must have the same mapping
 -- https://www.elastic.co/guide/en/elasticsearch/reference/curr...